monthly-targeting-review
Skill9 starsChanged 10 days agoCC-BY-4.0View on GitHub
Use when the user wants a monthly review of who each LinkedIn campaign actually paid to reach against who it meant to reach, and whether those audiences turn into pipeline. It audits job titles per campaign against that campaign's own targeting, reads the CRM deals by the same audience profiles, compares each profile's share of exposure with its share of pipeline, and recommends targeting, exclusion and budget changes per campaign. Also runs as a short weekly check on top of the last review. Examples: "job title audit", "are we paying for the wrong titles", "monthly targeting review", "which job titles create pipeline", "exclusion list for job titles", "weekly targeting check", "is our targeting leaking". Works from per-campaign Demographics reports, each campaign's targeting and a CRM deal export with contact job titles. 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
- audience-fit-checkSkill
- 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
- 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
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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.