Coupler.io Skills

Curated skill collection for business data analysis powered by the Coupler.io MCP server. Install as a Claude Code plugin to give Claude expert procedures for analytics, reporting, and marketing — backed by live data from your Coupler.io workspace.

Skills

Skills are organized by ICP (ideal customer profile) first — Finance, Sales, E-commerce, Marketing & Ads — then by shared Capability and general Utilities.

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.

Finance

Sales

E-commerce

Marketing & Ads

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.

Capability

Cross-ICP building blocks — compose these with a domain skill above.

Utilities

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.

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 ICP 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 32 and adds roughly 5.5k 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 <plugin>@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.