agentleFS
OneWave-AIOneWave-AI/claude-skills/champion-identifier/SKILL.md

champion-identifier

Skill378 starsChanged 52 days agoMITView on GitHub

Analyze LinkedIn profiles in target accounts to identify potential internal champions. Evaluates role, career path, mutual connections, interests, and suggests personalization approach. Use when you need to find who will champion your solution internally.

The file

Files
SKILL.md

Champion Identifier

Find the internal champion most likely to advocate for the solution at a target account, using structured LinkedIn and account analysis.

Contents

  • references/scoring-framework.md - champion profile, six scoring dimensions, total-score bands, warning signs
  • references/output-template.md - the full Markdown report structure to produce
  • references/outreach-templates.md - warm-intro, forwardable, direct, and opening-line messages
  • references/meeting-prep.md - discovery and qualification questions, red flags
  • references/multi-threading.md - sequence, coverage map, DMU table, org-chart format
  • references/champion-development-plan.md - five-phase plan with success metrics
  • references/playbook.md - tips, best practices, trigger phrases, worked example

Workflow

  1. Gather inputs: the company, the solution being sold, and any known contacts or mutual connections. Ask for whatever is missing.
  2. Research the company and the department the solution touches: stage, recent news, likely pain points, decision-making style, and hiring signals.
  3. Identify 5-10 candidate individuals on LinkedIn within the relevant department and leadership chain.
  4. Score each candidate across the six dimensions (0-10 each, 0-60 total) per references/scoring-framework.md, citing concrete evidence for every score.
  5. Rank candidates best to worst, and flag anyone who is a blocker or coach rather than a champion using the warning signs.
  6. For the top candidates, choose an outreach path (warm intro vs. direct) and draft the message from references/outreach-templates.md, plus personalization hooks and meeting prep from references/meeting-prep.md.
  7. Build the multi-threading plan and account map (DMU table, org chart) per references/multi-threading.md.
  8. Assemble the full report following references/output-template.md, filling every field with researched specifics and no placeholders.
  9. Recommend next steps using the phased plan in references/champion-development-plan.md.

Download now (ZIP)

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.