How to use the IMA DAI SDK agent skill (ima-dai-sdk)

What an agent skill is and what this one does

An agent skill is a folder of instructions and reference files that an AI agent such as Claude can load when a task matches the skill's description. This one contains a main SKILL.md file and five platform reference guides.

The skill tells the agent to use the IMA DAI SDK to load HLS or DASH streams for livestream events configured in Google Ad Manager, and video on demand content ingested into Google Ad Manager. The agent then follows the guide for your platform: StreamManager for web, Cast and Roku, the ExoPlayer IMA extension's ImaServerSideAdInsertionMediaSource for Android, and IMAStreamRequest for iOS and tvOS with AVPlayer.

• Web, HTML5, React, Node.js and Angular: loading a stream URL from Google full-service DAI into a video element
• Cast: integrating the SDK into a Cast Web Receiver using the Cast Application Framework
• Android: the Media3 ExoPlayer IMA extension
• iOS and tvOS: playing streams with AVPlayer
• Roku: implementing DAI on Roku SceneGraph

What the skill will not do

The skill does not play VAST or VMAP ad URLs. Its description says not to use it for that, so if your project uses ad tag URLs, this skill is the wrong tool.

It is also code integration work, not an ad tool. It does not set up ads in Google Ad Manager for you.

Install the skill

Download the ZIP for this skill from this page and unzip it. Then put the resulting skill folder in one of two places: your personal skills folder at ~/.claude/skills/, or a project's .claude/skills/ folder if you want it available only for that project.

Alternatively, upload the skill in the Claude apps under Settings → Capabilities → Skills.

• Personal: ~/.claude/skills/
• Single project: the .claude/skills/ folder inside the project
• Claude apps: Settings → Capabilities → Skills, then upload

Get the prerequisites in place

The skill only helps if your Google side is set up. The SDK needs a Google Ad Manager account with either a DAI livestream asset key, or a VOD content source CMS ID and video ID. Without these, there is nothing for the SDK to load.

You also need the IMA DAI SDK for your target platform and the platform toolchain, such as Android Studio, Xcode, or the Cast or Roku development environments. The skill does not install these for you.

• Google Ad Manager account with a DAI livestream asset key, or a VOD CMS ID and video ID
• IMA DAI SDK for your platform: web, Android Media3, iOS AVPlayer, Cast or Roku SceneGraph
• Platform toolchain such as Android Studio, Xcode, or Cast or Roku development environments

Trigger the skill with natural requests

You do not need a special command. Describe the integration you want in plain language and name your platform, and the agent should pick up the skill when your request matches its description. Mention the stream type too, since livestream and VOD use different request classes.

Good requests name the platform, the stream type and what you already have. The agent then follows the matching guide and the general setup workflow.

• "Add IMA DAI livestream playback to my React web app using my asset key."
• "Help me request a VOD stream with the IMA DAI SDK in an iOS AVPlayer app."
• "I have a Roku channel. Show me how to set up StreamManager for DAI."
• "Add DAI to my Android app with Media3 ExoPlayer and the IMA extension."

Follow the general setup workflow

Whatever the platform, the skill asks the agent to follow the same six-stage workflow. Knowing these stages helps you check the agent's output.

Stages: import the SDK, initialize it, add stream event listeners, set up timed metadata forwarding, make a stream request, then clean up SDK resources when the stream fails or the user leaves.

• Import the SDK
• Initialize the SDK
• Add stream event listeners
• Set up timed metadata forwarding
• Make a stream request
• Clean up SDK resources when the stream fails or the user leaves

Safety notes: scripts and network

According to the skill's listing, this skill runs no scripts and makes no network calls. It is a set of reference documents the agent reads. Any code the agent writes is for you to review, build and run in your own project.

Check generated code against the official guides in the references folder before shipping, and keep your Ad Manager keys out of public repositories.

Tips for better results

Give the agent your exact platform and framework version, and say whether you need livestream or VOD. Paste your existing player setup so the agent can add to it rather than replace it.

If the agent suggests VAST or VMAP tags, point out that this skill does not cover them and ask for the DAI approach instead.

• State the platform precisely, for example Android with Media3 rather than just Android
• Say livestream or VOD up front
• Share your existing player code
• Keep your asset key or CMS ID and video ID ready to paste into your own config