campaign-discovery
Skill10 starsChanged 40 days agoMITView on GitHub
Discovery for a campaign idea in one sentence: competitive angle, keywords and ranks, AI answer coverage, existing content, one report. Use when "explore a campaign", "run discovery on".
In this repository111 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- account-signalsSkill
- ad-briefSkill
- add-integrationSkill
- ads-account-auditSkill
- ads-performanceSkill
- advocacy-programSkill
- aeo-page-optimizeSkill
- ai-share-of-voiceSkill
- analyst-briefSkill
- apify-ads-intelligenceSkill
- apify-ai-search-citationsSkill
- apify-buying-signal-detectionSkill
- apify-creator-emailsSkill
- apify-easy-competitive-intelligenceSkill
- apify-ecommerceSkill
- apify-google-maps-leadsSkill
- apify-influencer-brand-collabsSkill
- apify-lead-scoring-enrichmentSkill
- apify-link-prospecting-outreachSkill
- apify-verified-email-finderSkill
- attribution-analysisSkill
- backlink-analysisSkill
- battlecardSkill
- brand-imageSkill
- brand-monitorSkill
- budget-pacingSkill
- campaign-planSkill
- case-studySkill
- chief-of-staffSkill
- churn-signalsSkill
- closed-lost-revivalSkill
- co-marketing-planSkill
- community-digestSkill
- community-planSkill
- comparison-pageSkill
- competitor-watchSkill
- content-briefSkill
- content-calendarSkill
- content-decay-monitorSkill
- content-inventorySkill
- content-strategySkill
- context-freshnessSkill
- coverage-trackerSkill
- cro-auditSkill
- data-hygiene-auditSkill
- design-qaSkill
- doctorSkill
- edit-copySkill
- email-performanceSkill
- event-followupSkill
- event-planSkill
- expansion-playSkill
- icp-refreshSkill
- keyword-clusterSkill
- landing-pageSkill
- launch-planSkill
- lead-lifecycle-specSkill
- lifecycle-mapSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Competitive angle: Read strategy/competitive/ (the battlecards) for who competes on this idea and how they position.
- Very specific: line 39
Keywords: Ask seo-analyst for volumes, difficulty, and our current rank for the core terms plus up to ten ideas.
- Very specific: line 43
AI answer-engine coverage: Ask brand-monitor to run the prompts in data/seo/prompts.csv that touch this idea (and to propose up to three …
- Very specific: line 46
Content inventory: Run content-inventory and take its report: what already exists that this campaign could reuse, refresh, or must not …
- Distinctive: line 85
Every number traces to a snapshot.
- Very specific: line 87
Do not scaffold the project or any content from here.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Campaign discovery
One sentence in ("a campaign positioning us as the AI-native alternative for marketing ops teams"), one discovery report out. You compose the specialist skills; you do not decide whether the campaign happens.
Needs: strategy/ filled (positioning, messaging, competitive/). The
keyword part needs a wired seo-data integration and the answer-engine
part a wired ai-visibility one; which vendor fills each is the Wired
table in integrations/README.md, and seo-analyst and brand-monitor
resolve it. Both are optional: without them, run the parts that work
offline and mark the rest as gaps, naming the export a person could drop
into data/seo/snapshots/YYYY-MM-DD-<vendor>-<what>.csv.
Procedure
- Frame the idea. Restate the campaign in one line, name the persona
from
strategy/personas.mdand the messaging pillar fromstrategy/messaging.mdit leans on. If neither fits, that is the first open question. - Competitive angle. Read
strategy/competitive/(the battlecards) for who competes on this idea and how they position. Askseo-analystfor the SERP competitors on the campaign's two or three core terms, so the report lists both the known competitors and whoever actually owns the search results. Note the angle they leave open. - Keywords. Ask
seo-analystfor volumes, difficulty, and our current rank for the core terms plus up to ten ideas; the pull lands indata/seo/snapshots/. Flag which terms are inkeywords.csvalready and which would be proposed additions. - AI answer-engine coverage. Ask
brand-monitorto run the prompts indata/seo/prompts.csvthat touch this idea (and to propose up to three new prompts for it). Report who is cited today and whether we are. - Content inventory. Run
content-inventoryand take its report: what already exists that this campaign could reuse, refresh, or must not duplicate, grouped by channel with status and owner. - Write the report to
reports/adhoc/YYYY-MM-DD-<slug>-discovery.mdfromreports/_templates/report.md, with these sections after the answer: competitive angle, keywords (table), AI answer-engine coverage (table), content inventory (by channel), what we would need to produce (a list: piece, channel, why, reuse or new), open questions for the team, and Data used with every snapshot path.
Worked example
"Run discovery on a campaign about meeting transcripts turning into tasks automatically."
- Framing: persona "marketing operations lead"; pillar "meetings stop evaporating".
- Competitive angle: two battlecards mention note-taking tools; SERP competitors for "meeting notes to tasks" are three note-taking apps, none positions on the marketing team. Open angle: the whole team's memory, not one person's notes.
- Keywords: "meeting transcript to action items" 1,900/mo, difficulty 34,
we do not rank; "ai meeting notes" 40,500/mo, difficulty 71, not
realistic. Snapshot
data/seo/snapshots/2026-09-03-dataforseo-keyword-overview.csv. - AI coverage: for "Which platforms turn meeting transcripts into decisions and tasks?" two note-taking apps are cited, we are not.
- Content inventory: one published blog post on decision logs (reuse), one LinkedIn draft in review (refresh), no email.
- What we would need to produce: a guide on the transcript pipeline (blog, new), an email to existing users (email, new), a refreshed LinkedIn post (reuse).
- Open questions: is the operations lead the buyer or the user; do we have a customer quote we can use.
Rules
- Propose, never decide: the report ends with questions and a list, not a go / no-go.
- Every number traces to a snapshot; a skill you could not run is a named gap.
- Do not scaffold the project or any content from here;
new-projectandnew-contentare separate, human-triggered steps.
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
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.

