Aller au contenu principal
AI Skills

Your trafficking rules, executed by AI.

8 ready-made business contexts — AI knows how to use the tools, Skills give it your specific context so it doesn't have to figure things out.

The concept

Tools + Context = Immediate results

Tools (MCP / CLI) provide capabilities. Skills provide operational context: the right order of operations, required checks, business rules to follow.

Without this context, AI can do everything — but has to figure out how. With Skills, it's immediately operational.

An LLM without Skills is an expert without a procedure.

It knows the tools. It doesn't know in which order to use them in your context, when to stop, or what to verify before pushing to production.

01

Step order isn't in the API

Creating a GAM campaign requires 12 steps in a precise order. Without Skills, the LLM improvises — it may create Line Items before the Order, or activate without checking the creative.

02

Your business rules don't exist anywhere else

Naming conventions, validation thresholds, per-network targeting rules — none of this is in the GAM API. Skills are the only place you encode them once and for all.

03

Automatic rollback doesn't improvise itself

Without explicit instructions, an LLM doesn't know that a failure at step 6 should trigger a clean rollback of steps 1–5. The cli-qa Skill enforces it.

In practice
AI searches for steps
Asks for clarification
Hesitates on order
45 min per campaign
Context is provided
Executes directly
Checks at every stage
3 min per campaign

Three layers, one result

Tools
MCP / CLI
173 GAM tools
Skills
8 business contexts
Order, checks, rules
Result
Campaign live in 3 min
No manual intervention

9 Skills, 9 operational contexts

Each Skill covers a complete area of GAM trafficking.

Bootstrap & Network

Connect your tenant and verify GAM access.

5 steps

Inventory & Ad Units

Explore and qualify your ad units.

5 steps

Availability Forecast

Check availability before creating.

5 steps

Advertisers, Orders & Line Items

Create advertisers, orders and line items.

5 steps

Placements & Targeting

Align placements and targeting for trafficking.

5 steps

Native Image Creative

Convert your assets into controlled native creatives.

5 steps

QA & Preview

Quality check and validation before going live.

5 steps

Deploy & Activate

Deploy campaigns and activate line items atomically.

5 steps

Reporting & Analytics

Run reports, analyze performance and export data from GAM.

5 steps
Open Source · GitHub

Install Skills in 2 minutes

Skills are lightweight Markdown files freely available on GitHub. They don't execute — they're loaded as context by your LLM.

Via the GitHub repository
Clone the repo and run the script:
$ git clone https://github.com/OrbiAds/Orbiads-GAM-MCP.git
$ cd Orbiads-GAM-MCP
$ ./install.sh skills
Permanent install (all sessions):
$ ./install.sh skills --copy
Inside Claude Code, without cloning
Directly from a Claude Code session:
claude> /install-github OrbiAds/Orbiads-GAM-MCP
— ou installer tout en une fois :
$ ./install.sh all
# CLI + MCP + Skills
Slash commands available after install
/orbiads:bootstrap
/orbiads:inventory-ad-units
/orbiads:availability-forecast
/orbiads:advertiser-order-line-items
/orbiads:placements-targeting
/orbiads:native-image
/orbiads:qa-preview
/orbiads:deploy-reporting
Advanced users

Adapt Skills to your internal rules

Skills are plain Markdown files. Fork the repo, edit the rules, deploy your version. No recompilation, no custom API.

Naming conventions

Enforce the format "CLIENT-YYYYMM-CampaignName" on every Order. The LLM applies it every time without being reminded.

Network-specific validations

Require a mandatory dry-run if the GAM network exceeds 50,000 active impressions. Zero risk of premature deployment.

Custom abort conditions

Define which errors trigger a full rollback vs. a simple Slack alert. Your risk policy, embedded in the Skill.

Example — adding a custom rule to SKILL.md
orbiads/skills/cli-deploy/SKILL.md
# Étapes existantes (inchangées)
1. [start] Run `orbiads --version`...
2. [depends: step 1] Run `orbiads auth status --json`...
...
# ✏️ Vos règles custom ajoutées ici
## Custom Rules
- Always prefix Order names with CLIENT-YYYYMM-
- Require dry-run on networks with > 50,000 impressions
- Alert on Slack after successful deploy (webhook: $SLACK_URL)
How to do it
1
Fork OrbiAds/Orbiads-GAM-MCP on GitHub
2
Edit the SKILL.md file for the target workflow
3
Install your fork: ./install.sh skills --copy
Fork the repository

The SKILL.md syntax is documented in the repo. Each file follows the same format: description, available commands, ordered steps, abort conditions, expected output.

Same context, two transports

The MCP vs CLI choice is about context weight, not functionality.

MCP

Tools have built-in descriptions — AI discovers them automatically. Ideal for rich conversations.

CLI

Skills provide context directly — lighter on memory. Ideal for scripting and focused tasks.

The result is identical.

Before / After Skills

Deploying a native campaign (12 manual steps).

Without Skills

  • AI searches for steps
  • Asks for clarification
  • Hesitates on order
  • 45 min per campaign

With Skills

  • Context is provided
  • Executes directly
  • Checks at every stage
  • 3 min per campaign

Ready to accelerate your trafficking?

5 free credits. No card required.