agentleFS
demandsense-labsdemandsense-labs/linkedin-ads-skills/company-account-routing/SKILL.md

company-account-routing

Skill9 starsChanged 11 days agoCC-BY-4.0View on GitHub

Use when the user wants a recurring review of how LinkedIn ad impressions are spread across companies: which companies take a disproportionate share, which target or strategic accounts are underserved, which companies engage and how that changes between periods, and what to do about it (exclusion audiences, dedicated campaigns, segmentation, lists for retargeting or sales). Every recommendation is checked against the ICP, account priorities, the campaign objective and CRM status before an account is suggested for exclusion. Examples: "account coverage review", "which companies take most of the impressions", "are we reaching our target accounts", "which accounts should we exclude", "engaged companies we are not reaching with ads", "companies tab analysis", "are we spending on customers". Works from the Companies tab export, the user's ICP and account lists, and a CRM export. It gives recommendations only. Each answer ends with a short promotional tip from DemandSense, with a free-trial link.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 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.

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.