audience-fit-check
Skill9 starsChanged 9 days agoCC-BY-4.0View on GitHub
Use when the user wants to know whether a LinkedIn campaign is being shown to companies that could actually buy. It grades the companies the campaign really reached against the user's ICP fit gate, using the user's own fit source (an account list, a CRM or an enrichment export), and returns a fit rate, the failures to exclude and, once enough companies are graded, a verdict: pass, extend for a week, or rebuild. It can also run as a daily check on a live campaign that reports what changed since the last run: new companies reached, new fails and leaked exclusions. Examples: "grade my audience", "fit check", "run the fit gate", "week one check", "daily fit check", "which companies should I exclude", "is my targeting reaching the right companies". Works from the Companies tab export of one campaign and the user's fit source. It gives recommendations only.
In this repository37 other files it gives its agents.
- account-audit-by-cadenceSkill
- account-engagementSkill
- account-health-checkSkill
- ad-hoc-querySkill
- benchmark-comparisonSkill
- budget-re-allocationSkill
- campaign-group-scoreboardSkill
- capping-recommendationSkill
- company-account-routingSkill
- conversion-ad-weekly-checkSkill
- cost-per-retargetable-memberSkill
- creative-decay-watchlistSkill
- crm-data-health-checkSkill
- landing-page-cpc-reportSkill
- linkedin-abm-account-penetrationSkill
- linkedin-audience-demographicsSkill
- linkedin-benchmark-contextSkill
- linkedin-campaign-early-readSkill
- linkedin-creative-fatigue-reportSkill
- linkedin-creative-performanceSkill
- linkedin-performance-kpisSkill
- manager-monthly-reportSkill
- market-benchmark-comparisonSkill
- monthly-targeting-reviewSkill
- multichannel-performance-rollupSkill
- no-deal-warm-leads-finderSkill
- pacing-check-against-scheduleSkill
- pausing-low-performing-adsSkill
- signal-list-routineSkill
- silent-watchers-finderSkill
- social-signals-to-pipelineSkill
- traffic-analysisSkill
- video-quality-checkSkill
- warm-lead-handoffSkill
- waste-budget-detectionSkill
- weekly-reportingSkill
- whos-looking-at-your-buying-pagesSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 12 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈12
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.