CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

71%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced workflow with typed contracts, exact queries, templates, and human checkpoints at every step. Its weaknesses are length and monolithic structure: repeated schemas, rationale padding, and ~600 lines of inline material that should live in reference files, plus no recovery guidance for rejected checkpoints.

Suggestions

Move the Step 0 configuration questionnaire, the email angle/template tables, and the sample checkpoints into one-level-deep reference files (e.g., references/config-questions.md, references/email-templates.md), keeping SKILL.md as a lean overview.

Replace the repeated person/move schema blocks in Steps 1-3 output contracts with a single shared schema definition referenced by each step.

Add brief guidance on checkpoint rejection (e.g., revise and re-present on 'n', or drop a mover) so each approval gate has a recovery path.

DimensionReasoningScore

Conciseness

The body is information-dense (tables, contracts, exact query strings) but at ~600 lines it includes unnecessary material: the person schema is repeated verbatim across three output contracts, and the "Why this is the #1 signal", "Key Differences from Other Signal Composites", and parts of "Tips" restate rationale that could be tightened or cut. Not 4 because the repetition and rationale padding are more than minor; not 2 because most sections are table-driven domain knowledge Claude would not already know, not generic filler.

3 / 5

Actionability

Fully executable for an instruction-only skill: typed input/output contracts for every step, exact search-query patterns (e.g., '"{full_name}" AND ("{last_known_company}" OR "joined" OR "new role")'), per-approach email template shapes with worked examples, and deterministic tier-assignment rules. The scoring note explicitly says absence of code is not penalized in instruction-only skills when guidance is this actionable.

5 / 5

Workflow Clarity

A clearly sequenced 6-step process (0-5) with an explicit human checkpoint after every step and real validation (movers table, qualification approval, sample approval), plus error fallbacks (email_not_found → LinkedIn; dark profile → manual check). Not 5 because there is no feedback loop for what happens when a checkpoint is rejected or a step partially fails (no revise/re-run guidance), leaving a minor validation gap.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the body is a well-sectioned monolith: the one-time config questionnaire, the email template/example library, and full sample checkpoints are all inline content that clearly belongs in one-level-deep reference files. Not 2 because section structure, headers, and an execution summary make navigation genuinely easy; not 4 because nothing is split out and the file is far too long to qualify for the short-skill exception.

3 / 5

Total

15

/

20

Passed

Description

71%Weight 40%Scale 1-5

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

A specific, third-person description that clearly conveys the full pipeline and its niche, but it omits any explicit "Use when..." trigger guidance, which both caps completeness and leaves natural trigger phrases (which the body already contains) out of the description. Strong on concrete actions and distinctiveness.

Suggestions

Append a trigger clause such as: "Use when the user wants to track job changes of past buyers, champions, or power users, asks about champion tracking, or wants to reach out to contacts who moved to a new company."

Surface 2-3 natural user phrasings into the description (e.g., "champion tracking", "who moved from our customer accounts") so the skill triggers on how users actually ask for this.

State the warm-relationship differentiator in one clause (e.g., "warm outreach to known contacts, not cold outbound") to further reduce overlap with generic outreach skills.

DimensionReasoningScore

Specificity

"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" lists multiple specific concrete actions covering the full pipeline comprehensively; not below 5 because no meaningful action is missing, and the anchors at 3-4 require fewer or less complete action coverage.

5 / 5

Completeness

The "what" is clear and multi-part, but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is not merely implicit-but-usable — it is entirely absent from the description.

3 / 5

Trigger Term Quality

Natural terms like "job change", "champions", "power users", "moved to a new company", and "outreach" are present, but common user phrasings such as "champion tracking", "former customers", or "job change alerts" are missing — the body's "When to Auto-Load" section contains these triggers but they were not surfaced into the description. Not 5 because synonym/variation coverage is incomplete; not 3 because coverage is genuinely good rather than partial.

4 / 5

Distinctiveness Conflict Risk

"champion/buyer/user job change signal composite" carves a distinct niche (tracking known people vs. companies) with low conflict risk against generic outreach skills. Not 5 because "drafts personalized outreach" overlaps with sibling outreach composites (cold-email, linkedin-outreach) and the description does not state the differentiator (warm vs. cold) explicitly enough to eliminate that risk; not 3 because the niche is far more specific than the anchor's generic overlap example.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.