gtmos-routing-lead-ownership | ay-automate/gtmos-skills

What it does when it runs

Find the authoritative owner of a lead or account, audit whether high-intent leads got timely human follow-up ("no lead left behind"), and fix ownership gaps -- unowned records, owners who left, territory mismatches, bulk reassignments. With GTM OS connected it reads owners and territories, previews routing with territory.match, assigns with routing.assign (an auditable decision record per change), sweeps unowned or orphaned records with routing.reconcile, edits territories with territory.upsert (human only) and opens follow-up tasks; CRM-of-record owner changes are proposed through crm.update_record for approval. Use for "who owns this lead", "find the account owner", "unowned leads", "lead routing", "round robin", "territories", "reassign accounts", "rep left, move their book", "speed to lead audit", "leads nobody followed up". For triaging single new leads see gtmos-leads-inbound-triage.

Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply: None found.
Hosts it reaches: No third-party host appears in the skill or its bundled files.
Tool permissions it declares: No allowed-tools in the frontmatter. It does act, so it runs under whatever permissions your session already grants.
Actions present in the files: shellwrites files

Ask about gtmos-routing-lead-ownership

Opens your assistant with this page's recorded context. Check the linked sources before relying on it.

Is this safe to install?Claude ChatGPT

Adapt it to my stackClaude ChatGPT

What else do I need for it to workClaude ChatGPT

Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗

git clone --depth 1 --filter=blob:none --sparse https://github.com/ay-automate/gtmos-skills.git /tmp/gtmos-skills
git -C /tmp/gtmos-skills sparse-checkout set "skills/gtmos-routing-lead-ownership"
mkdir -p ~/.claude/skills/gtmos-routing-lead-ownership
cp -R "/tmp/gtmos-skills/skills/gtmos-routing-lead-ownership/." ~/.claude/skills/gtmos-routing-lead-ownership/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 107 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add ay-automate/gtmos-skills
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

The source carries a MIT AND APACHE-2.0 licence, which does not grant redistribution. Everything else on this page is our own reading of the file and is published here; the text of the skill is not, and stays where its author put it.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

no-lead-left-behind-lead-treatment-audit by zapier · 354
workflows-inbound-lead-routing by clay-run · 145
lead-routing by NEON-Rutger · 58
lead-routing-rule-analyzer by elijeangilles · 9
lead-routing by sidchaudhary · 6
lead-routing-design by noahatcheckpoint · 1
lead-magnets by coreyhaines31 · 57,918
lead-dossier by ericosiu · 3,766

Need help setting it up?

This page tells you what gtmos-routing-lead-ownership does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.