champion-move-outreach

End-to-end champion/buyer/user job change signal composite. Takes a set of known people (past buyers, champions, power users), detects when they move to a new company, researches the new company for ICP fit, and drafts personalized outreach leveraging the existing relationship. Tool-agnostic — works with any people source, detection method, and outreach platform.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/outreach/composites/champion-move-outreach/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and clearly sequenced with strong validation checkpoints, but it is a monolithic, somewhat verbose document that buries operational detail alongside motivational rationale and does not split any content into reference files.

Suggestions

Trim persuasive/rationale sections like 'Why this is the #1 signal' and the 'Key Differences from Other Signal Composites' table, or move them to a reference file, since Claude does not need to be sold on the approach to execute it.

Split the large inline material — Step 0 config tables and the full per-approach email template/example sequences — into reference files (e.g. CONFIG.md, OUTREACH-TEMPLATES.md) and link them one level deep to shorten the SKILL.md overview.

Dimension	Reasoning	Score
Conciseness	The body is actionable and domain-specific but runs ~600 lines with rationale/persuasion prose ('Why this is the #1 signal', the 'Key Differences' comparison table, motivational framing) that could be tightened — efficient enough to clear score 1 but padded relative to the lean score-3 anchor.	2 / 3
Actionability	Provides fully concrete guidance: typed input/output contracts, per-tool search-query strings (e.g. '"{full_name}" AND ("{last_known_company}" OR "joined" OR "new role")'), ICP qualification matrices, and complete copy-paste email template shapes with example sequences — meeting the fully executable/copy-paste-ready bar for an instruction skill.	3 / 3
Workflow Clarity	A clearly sequenced 5-step pipeline with typed contracts linking each step, explicit human checkpoints after almost every step ('Approve before we draft outreach?', 'Ready to launch?'), and addressed error branches (unable_to_verify, email_not_found, disqualified), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well-organized with headers, but no bundle files exist and all detail — config tables, full email example sequences, the comparison table — is inline in one ~600-line SKILL.md with no one-level-deep references to separate files, fitting the score-2 anchor of content that should be separate being inline.	2 / 3
	Total	10 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-differentiated with a clear what-it-does summary, but it omits any explicit 'Use when' trigger guidance and leans on jargon over natural user phrasings, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit 'Use when...' clause with natural triggers users would say, e.g. 'Use when a user asks to track their champions, check for job changes among past buyers/users, or see who moved from customer accounts.'

Replace jargon like 'signal composite' and 'ICP fit' with plain language, and surface user-sayable terms such as 'champion tracking' and 'who moved companies' in the description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'detects when they move to a new company', 'researches the new company for ICP fit', 'drafts personalized outreach' — matching the score-3 anchor of several specific concrete actions rather than just naming a domain.	3 / 3
Completeness	Clearly answers what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains some user-sayable terms ('job change', 'move to a new company', 'outreach') but leans toward jargon ('signal composite', 'ICP fit') and misses common natural phrasings a user would actually say ('track my champions', 'champion tracking', 'who moved'), which appear in the body but not the description.	2 / 3
Distinctiveness Conflict Risk	The champion/buyer/user job-change niche is clearly scoped and explicitly distinguished from stranger-targeting signals ('leveraging the existing relationship'), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (644 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/outreach/composites/champion-move-outreach/SKILL.md
Commit: 8866b2a

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.