signal-list-routine
Skill9 starsChanged 9 days agoCC-BY-4.0View on GitHub
Use when the user runs LinkedIn ads only at a list of named target companies and wants the weekly routine that tells a person which companies to write to this week and why now. It sorts the list into A, B and C by dated public buying signals and sets aside a holdout (monthly), checks the account's clicks for placeholder employer pages such as "Stealth AI Startup", checks whether each list is still buying new people or has been used up and plans the budget a list can hold (Mondays), ranks the companies that engaged far above the ads for a human to approve as cards, and at quarter end reads which signals sat on won deals. Examples: "which companies should we write to this week", "is my list warm or only a fit list", "signal list check", "are my clicks from real companies", "can my list hold more budget", "warm accounts from my ABM list", "quarter-end signal retrain". Works from LinkedIn Companies exports and the user's own CSVs. It never sends or changes anything and 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
- monthly-targeting-reviewSkill
- multichannel-performance-rollupSkill
- no-deal-warm-leads-finderSkill
- pacing-check-against-scheduleSkill
- pausing-low-performing-adsSkill
- 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.