Coupler.io AI Agent Skills for Business Analytics

Ready-to-use AI agent skills for marketing, PPC, sales, finance, ecommerce, and business reporting. Coupler.io skills give AI assistants repeatable analytics workflows backed by live data from your Coupler.io workspace through the Coupler.io MCP server. Use them to analyze campaign performance, sales pipelines, financial metrics, ecommerce data, generate reports, investigate anomalies, and turn business data into actionable insights.

Contents

• What can you do
• Quick start
• Skills library
  • Marketing & PPC
  • SEO & GEO
  • Sales
  • Finance
  • Ecommerce
  • Capabilities
  • Utilities
• Example questions
• How Coupler.io skills work
• Installation
• Coupler.io MCP
• Skill frontmatter
• Contributing
• License

What can you do with Coupler.io skills?

Use AI agent skills to:

• Analyze marketing performance across Google Ads, Meta Ads, TikTok Ads, Microsoft Ads, LinkedIn Ads, Amazon Ads, and other channels
• Find wasted PPC spend and opportunities to scale campaigns
• Review sales pipelines, win rates, deal velocity, and rep performance
• Analyze P&L, MRR, ARR, cash runway, and financial performance
• Measure ecommerce conversion, AOV, retention, and repeat purchases
• Generate structured business reports with validated metrics
• Investigate anomalies and explain changes in business KPIs
• Create and configure Coupler.io dataflows through AI

Quick start

Add the Coupler.io skills marketplace:

/plugin marketplace add coupler-io/skills

Then install the skill set you need:

/plugin install coupler-marketing-ads@coupler-io-skills
/plugin install coupler-seo-and-geo@coupler-io-skills
/plugin install coupler-finance@coupler-io-skills
/plugin install coupler-sales@coupler-io-skills
/plugin install coupler-ecommerce@coupler-io-skills

Install only what you need. Every skill’s description stays in context for the whole session, so a plugin costs tokens in proportion to how many skills it carries. See Installation for the full plugin list, team setup, and manual install.

You also need a Coupler.io account with the MCP server connected, so the skills have live data to work against.

Skills library

Skills are organized by business function - Finance, Sales, Ecommerce, Marketing & Ads, and SEO & GEO - with additional shared capabilities and utilities.

Marketing & PPC

Google Ads deep dives

Eight Google-Ads-only skills in marketing-and-ads/google-ads/. Each one owns a single question and hands off to the others rather than duplicating them — ppc-analytics stays the cross-platform paid view. When a request needs a field no packaged report type carries, they route to capability/google-ads-custom-gaql.

TikTok Ads deep dives

Eleven TikTok-only skills in marketing-and-ads/tiktok-ads/. Same shape as the Google pack — each owns a single question and routes to its siblings rather than duplicating them, with ppc-analytics still the cross-platform paid view.

Meta / Facebook Ads deep dives

Eleven Meta-only skills in marketing-and-ads/facebook-ads/. Same shape as the Google pack — each owns a single question and routes to its siblings rather than duplicating them, with ppc-analytics still the cross-platform paid view.

Microsoft Ads deep dives

Eleven Microsoft Ads (Bing) skills in marketing-and-ads/microsoft-ads/. Same shape as the Google pack, with triggers anchored to Microsoft, Bing and UET so the two packs don’t collide. Adds what Microsoft carries and Google doesn’t: share of voice with click share, LinkedIn profile targeting (company, industry, job function), and the negative keyword conflict report.

LinkedIn Ads deep dives

Ten LinkedIn-only skills in marketing-and-ads/linkedin-ads/. Member demographics and country/region come from single-dimension ad analytics (one member dimension per source, not crossable with campaign), and there’s no hourly split, so there’s no separate audience or dayparting skill. Adds a native lead gen form skill instead.

Amazon Ads deep dives

Ten Amazon-only skills in marketing-and-ads/amazon-ads/, built on the standard Amazon Ads connector, with extra coverage from Amazon Ads (Unified) where that connector is enabled on the account. Every run declares one sales basis (ACOS or ROAS, one attribution window) and never totals marketplaces in different currencies.

Black Friday deep dives

Five sale-season skills in marketing-and-ads/black-friday/, one per stage of a Black Friday, Cyber Monday, Prime Day or store sale. They read Google Ads, Meta / Facebook Ads and TikTok Ads together with Shopify, and hand off to the per-platform and Shopify skills for anything outside the sale.

SEO & GEO

Thirteen organic- and AI-search skills in seo-and-geo/, installed as their own coupler-seo-and-geo plugin.

SEO

Twelve organic-search skills built on Google Search Console, with GA4 and Google Ads where a question needs them. Same shape as the ad packs — each owns a single question and routes to its siblings rather than duplicating them.

GEO

Generative engine optimization skills, also in seo-and-geo/, built on AI-visibility exports (Peec AI and similar) joined to GA4, Search Console and your business data.

Sales

Finance

Ecommerce

Shopify deep dives

Seven Shopify-only skills in ecommerce/shopify/. Same shape as the ads packs — each owns a single question and routes to its siblings rather than duplicating them, with ecom-analytics still the cross-platform store view. They share their definitions deliberately: store performance is the baseline the others read against, and sell-through, inventory value and dead-stock cash live in one skill only.

Klaviyo, Gorgias and Cin7 deep dives

Store-side skills for the tools around the shop, in ecommerce/klaviyo/, ecommerce/gorgias/ and ecommerce/cin7/. Same shape as the Shopify pack, and they route to it where the question is about store sales.

Capabilities

Shared building blocks. Compose these with any domain skill above.

Utilities

---

Example questions

Marketing & PPC

• Why did Google Ads ROAS decline last week?
• Which campaigns are wasting budget?
• Which Meta Ads creatives are showing signs of fatigue?
• Are we on track to spend our advertising budget this month?

Sales

• What is our current pipeline coverage?
• Which stage has the biggest conversion drop?
• Which reps have the shortest sales cycles?

Finance

• What changed in our P&L this month?
• How many months of cash runway do we have?
• Explain the movement in MRR versus last month.

Ecommerce

• Which products contributed most to revenue growth?
• How has repeat purchase rate changed?
• Which customer cohorts have the strongest retention?

How Coupler.io skills work

A skill is a reusable set of instructions that tells an AI agent how to perform a specific analytics task.

The skill uses Coupler.io MCP tools to discover datasets, inspect schemas, query live business data, and return a structured analysis.

Skills define how to analyze your data. Coupler.io MCP provides access to the data and tools needed to perform the analysis.

Skills work in all popular AI tools, such as Claude, ChatGPT, and Cursor. Any AI assistant connected to the Coupler.io MCP server can load them, even without installing the plugins.

---

Installation

From the marketplace — add this repo as a plugin marketplace, then install the per-cluster plugin(s) you want:

/plugin marketplace add coupler-io/skills
/plugin install coupler-finance@coupler-io-skills

Each business function is its own plugin, so you install only what you need. Available plugins:

Plugin skills are namespaced by their plugin, so they can be invoked explicitly as /coupler-finance:finance-analytics. Most of them are model-invoked too — Claude reaches for them when the request matches their description. If the install summary says Run /reload-plugins to activate., run that.

Install only the plugin you need. Every skill’s description stays in context for the whole session, so a plugin’s cost scales with how many skills it carries. coupler-marketing-ads bundles 68 and adds roughly 13k tokens to every session; the single-skill plugins add a few hundred. Check any plugin before installing it:

claude plugin details coupler-marketing-ads@coupler-io-skills

For a whole team — register the marketplace in the repository’s .claude/settings.json so collaborators get it once they trust the folder:

{
  "extraKnownMarketplaces": {
    "coupler-io-skills": {
      "source": {
        "source": "github",
        "repo": "coupler-io/skills"
      }
    }
  }
}

This adds the marketplace, not the plugins. Each person still runs /plugin install @coupler-io-skills to pick what they want. To pre-enable plugins as well, see enabledPlugins.

Manual — copy any skill folder (each contains a SKILL.md) into your project’s .claude/skills/ directory. Skills installed this way are not namespaced, and Claude activates them when the request matches their description.

---

Coupler.io MCP tools

These are the tools the Coupler.io MCP server exposes. Skills use them automatically — you only need to know them if you are writing a new skill or calling tools directly.

Skills

Discovery

Inspection

Configuration

Run & persist

Deprecated: list-dataflows — replaced by list-datasets.

---

Skill frontmatter

The Agent Skills spec allows only six top-level frontmatter keys — name, description, license, compatibility, metadata, allowed-tools — and a SKILL.md carrying anything else can be rejected outright. Claude Code’s own frontmatter reference accepts considerably more (when_to_use, model, effort, context, agent, argument-hint, disable-model-invocation, allowed-tools, disallowed-tools, and others), but those are Claude-only extensions that other runtimes ignore. We target the portable six, so everything of ours lives under metadata:

---
name: sales-analytics
description: Use this skill when the user wants to analyze sales pipeline, review win rates, … # for the agent: what it does and when to reach for it
metadata:
  short_description: Pipeline health, win rates, sales velocity and rep performance, straight from your CRM. # for humans: one line, shown in the UI
  category: sales
  sources:
    - Salesforce
---

description is the agent’s routing signal, so it is long and stuffed with trigger phrases — unreadable in a skill catalog. short_description is the human-facing counterpart: one sentence, no “use this skill when”, safe to render in a card or list. It is optional; consumers should fall back to a truncated description when it is absent.

python .github/scripts/generate_skill_index.py --check enforces the length limits:

Above 500 characters a description only earns a warning — it still passes. There is no consensus on the right length: obra/superpowers ships descriptions of 79–234 characters, while coreyhaines31/marketingskills runs 432–1014. The warning is a nudge to check the tail is still earning its context, not a rule — agents weigh the opening sentence most heavily.

Both descriptions land in skills-index.json, which is what the API and the MCP server read.

Contributing and development

The machine-readable catalog is skills-index.json. Do not edit it by hand — it is generated from SKILL.md frontmatter. Change the skill files, then run python .github/scripts/generate_skill_index.py, or let the GitHub Action regenerate it on merge to main.

License

Released under the MIT License.