> ## Documentation Index
> Fetch the complete documentation index at: https://docs.contentignite.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Skills

> Let an AI coding agent integrate the Content Ignite Mobile SDK for you

If you use an AI coding assistant, you can have it integrate the Content Ignite Mobile
SDK for you. We publish a set of **Agent Skills** — packaged instructions that teach a
coding agent exactly how to install, initialise and add ads with our SDK, following the
same guidance as these docs.

## What are Agent Skills?

Agent Skills are a lightweight, open format for giving AI agents new, task-specific
expertise. Each skill is a small bundle of instructions (and links to our reference
implementations) that an agent loads on demand when you ask it to do the related task —
for example, *"add a Content Ignite banner to my home screen."*

Because the format is an open standard, the same skills work across any
skills-compatible assistant, including **Claude Code, Cursor, OpenAI Codex, Gemini CLI,
GitHub Copilot** and others.

<Note>
  Agent Skills are optional and complement these docs — they don't replace them. This
  documentation remains the source of truth; the skills simply let an agent apply it for
  you. If you prefer to integrate by hand, follow the platform guides directly.
</Note>

## Install

The skills live in our public repository and install with the
[`skills`](https://github.com/vercel-labs/skills) CLI (via `npx`, so no global install
is needed):

```bash theme={null}
npx skills add https://gitlab.com/content-ignite/skills
```

Select the skills you want from the interactive list, or install one directly:

```bash theme={null}
npx skills add https://gitlab.com/content-ignite/skills --skill ci-mobile-ads-get-started
```

Then ask your agent in natural language — e.g. *"Get started with the Content Ignite
Mobile SDK"* or *"Add a Content Ignite interstitial"* — and it will load the relevant
skill and apply it to your project.

### Project vs global install

By default the skills install at **project scope** — into your app's `.claude/skills`
directory (or the equivalent for your assistant) — so run the command from your app's
root directory. This is what you want when integrating a specific app, and it keeps the
skills versioned alongside that project.

To make the skills available across all of your projects instead, add the `-g` (global)
flag:

```bash theme={null}
npx skills add https://gitlab.com/content-ignite/skills -g
```

<Note>
  You need Node.js installed (which provides `npx`). The skills work with **native
  Android and iOS** integrations today (Jetpack Compose, View-based, SwiftUI and UIKit);
  React Native is documented on this site and planned for a future skills release.
</Note>

## Available skills

<Columns cols={2}>
  <Card title="ci-mobile-ads-get-started" icon="rocket" href="https://gitlab.com/content-ignite/skills/-/tree/main/skills/ci-mobile-ads-get-started">
    Install, configure and initialise the SDK on Android or iOS. Start here.
  </Card>

  <Card title="ci-mobile-ads-banner" icon="rectangle-ad" href="https://gitlab.com/content-ignite/skills/-/tree/main/skills/ci-mobile-ads-banner">
    Add an inline banner ad (Compose/View-based, SwiftUI/UIKit).
  </Card>

  <Card title="ci-mobile-ads-interstitial" icon="window-maximize" href="https://gitlab.com/content-ignite/skills/-/tree/main/skills/ci-mobile-ads-interstitial">
    Add a full-screen interstitial ad shown at natural transitions.
  </Card>

  <Card title="ci-mobile-ads-app-open" icon="mobile-screen-button" href="https://gitlab.com/content-ignite/skills/-/tree/main/skills/ci-mobile-ads-app-open">
    Add App Open ads for cold start and resume-from-background.
  </Card>

  <Card title="ci-mobile-ads-migrate-from-google" icon="arrows-rotate" href="https://gitlab.com/content-ignite/skills/-/tree/main/skills/ci-mobile-ads-migrate-from-google">
    Migrate an app already using the Google Mobile Ads SDK onto Content Ignite.
  </Card>
</Columns>

## Already running Google Mobile Ads?

The Content Ignite Mobile SDK embeds and orchestrates the Google Mobile Ads SDK, so you
should not run a separate Google Mobile Ads integration alongside it. If your app
already uses the Google Mobile Ads SDK, the **`ci-mobile-ads-migrate-from-google`** skill
detects the existing integration, removes it, installs Content Ignite in its place, and
can wire your existing ad views into our `publisher` fallback for a gradual rollout.

## How the skills stay current

The skills never hard-code an SDK version — they resolve the latest release from our
repositories at integration time, and the iOS `SKAdNetworkItems` list is pulled from
Google's official quick-start when needed. Each skill also links to a complete, working
demo app so your agent can reference a full example in context.

## Need help?

If a skill produces something unexpected, or you'd like a skill for a scenario we don't
yet cover, reach out to your Content Ignite account manager, or follow the relevant
platform guide on this site:

<Columns cols={2}>
  <Card title="Android setup" icon="android" href="/app/android/android_intro" />

  <Card title="iOS (SwiftUI) setup" icon="apple" href="/app/ios_swiftui/ios_swiftui_intro" />

  <Card title="iOS (UIKit) setup" icon="apple" href="/app/ios_uikit/ios_uikit_intro" />

  <Card title="React Native setup" icon="react" href="/app/react_native/react_native_intro" />
</Columns>