agentleFS
adkitadkit/ads-mcp/skills/analyze/SKILL.md

analyze

Skill20 starsChanged 4 months agoMITView on GitHub

Pull ad campaign performance data from connected platforms. Use when the user asks about campaign results, ROAS, ad spend, CTR, conversions, search terms, negative keywords, ad fatigue, budget pacing, delivery issues, or wants to diagnose why ads aren't spending. Also use for Google search term reports and keyword performance analysis. Not for creating campaigns, browsing competitor ads, or generating creatives.

70 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use constitution, revise and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArvorCoSkill

    constitution

    Create or update the project constitution - personalized governance and coding principles. Use when starting a project or updating project standards. Triggers on: create constitution, update principles, set project rules.

    Also in 4 projects that use this

  • stormlightlabsSkill

    revise

    Address review comments on an open pull request and push the fixes. Use for /edit, /revise, or when asked to respond to review feedback on a PR number.

    Also in 3 projects that use this

  • DockerSkill

    write

    Write or edit reader-facing technical prose for immediate comprehension. Use for documentation, PR titles and descriptions, release notes, design documents, user-facing explanations, and substantive comments. Also use when asked to make writing clearer, more natural, less AI-generated, or easier to read. For documentation fixes, handles edits, formatting, self-review, and commits after research identifies what to change. Do not use for code-only tasks with no prose deliverable.

    Also in 6 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 5 projects that use this

  • H-mmerSkill

    submit

    Draft and submit a vulnerability report to the bug bounty platform. Reads scope.yaml for platform/program, uses brain + findings for content. Always drafts first for review.

    Also in 3 projects that use this

  • GoogleSkill

    quality

    Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.

    Also in 3 projects that use this

  • +1 more from ArvorCo

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 60 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use adkit_manage with entity: "results" and action: "list" on any connected platform:

    line 18
  2. Very specific:

    Use period for presets, or from + to for custom ranges.

    line 34
  3. Very specific:

    If the user has multiple ad accounts, pass accountId in params.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 60 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Analyze Performance

Requires a connected platform — run /ads:setup first if needed.

1. Fetch results

Use adkit_manage with entity: "results" and action: "list" on any connected platform:

adkit_manage platform: "<platform>" entity: "results" action: "list" params: { level: "campaigns", period: "30d" }

Common params (all platforms)

ParamDescription
levelcampaigns, adsets/ad-groups, ads (Meta also: no level = account; Google also: keywords)
periodtoday, yesterday, 7d, 14d, 30d, this_month, last_month, this_quarter, last_year, maximum
from / toYYYY-MM-DD custom date range (use instead of period)
sortcost, clicks, impressions, conversions
limitMax rows to return

Use period for presets, or from + to for custom ranges. Don't combine both.

Platform-specific features

Available breakdowns, metrics, and additional actions vary by platform. Call adkit_help path: "manage <platform> results" for the full list. Key differences:

  • Meta: breakdown (day, age, gender, country, device), attribution-window, actions filter
  • Google: breakdown (device, network), plus separate search-terms, placements, and keywords actions
  • TikTok: dimensions and metrics pass through to TikTok reporting API

Filtering by entity

Filter results to a specific campaign or ad group:

PlatformParam
Metacampaign: "<id>", adset: "<id>", ad: "<id>"
GooglecampaignId: "<id>", adGroupId: "<id>"
TikTokUses dimensions — check adkit_help

2. Google-specific entities

Google Ads has additional entities beyond standard results:

EntityActionUse case
resultssearch-termsActual queries that triggered ads
resultsplacementsWhere ads appeared (Display/YouTube)
keywordslistManaged keyword list for an ad group
keywordscreateAdd keywords (including negative match types)

search-terms and keywords are different: search terms are what users typed, keywords are what you're targeting/excluding.

3. Multi-account

If the user has multiple ad accounts, pass accountId in params. Call adkit_status to see available accounts — if omitted, the first account is used.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.