CtrlK
BlogDocsLog inGet started
Tessl Logo

outbound-prospecting-engine

End-to-end outbound prospecting: detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign.

61

Quality

77%

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/playbooks/outbound-prospecting-engine/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured orchestrator playbook: an efficient, correctly ordered eight-step workflow with named sub-skills, concrete scoring heuristics, explicit human checkpoints, and iteration cadence. Its only real weaknesses are minor — a redundant opening line and slightly underspecified personalization/campaign-tool steps. No bundle files are present, and none are referenced, so progressive disclosure rests on the body's own organization, which is good.

DimensionReasoningScore

Conciseness

The body is lean — a compact signal-source table, one-line step descriptions, and terse bullet lists with no explanation of concepts Claude already knows. It is not a 5 only because of minor redundancy: the opening line restates the description's pipeline verbatim, and a few bullets (e.g. "Track open rates, reply rates, meeting bookings") state the obvious for the domain.

4 / 5

Actionability

As an instruction-only playbook it gives concrete, executable guidance: each step names the exact sub-skill to invoke (lead-qualification, company-contact-finder, contact-cache, cold-email-outreach), a signal-to-source selection table, and specific lead-scoring rules ("Job posting + funding = strongest intent"). It falls short of 5 due to minor gaps — "Set up the outreach campaign in your chosen tool" and the personalization step lack a concrete example or template.

4 / 5

Workflow Clarity

The eight steps are clearly sequenced, and a dedicated "Human Checkpoints" section places explicit review/validation gates after Steps 3, 6, and 8, while Step 8 plus "Ongoing Cadence" define feedback loops (re-run signals weekly, adjust messaging on metrics). This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops'); although the campaign is a batch operation, validation is present, so the batch-operation cap does not apply.

5 / 5

Progressive Disclosure

The skill is well-organized into scannable sections (When to Use, Prerequisites, Steps, Cadence, Checkpoints) with nothing inlined that clearly belongs in a separate file, and no bundle files exist to verify. It sits at anchor 4 rather than 5: at ~95 lines it exceeds the under-50-line simple-skill exception, and a couple of sections (the signal-source table or cadence details) could arguably be split out if the skill grows.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and comprehensive about what the skill does, listing the full five-stage pipeline in third person. Its main weaknesses are the complete absence of a 'Use when...' trigger clause and sparse natural trigger-term coverage (no 'cold email', 'lead gen', 'B2B outreach'). Adding an explicit when-to-use clause with common synonyms would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to build outbound prospecting, lead generation, or cold-email campaigns for a client."

Include natural synonyms users would actually say — "cold email", "lead gen", "B2B outreach", "find leads" — alongside the current terminology.

Optionally signal the orchestrating nature ("coordinates signal-detection and outreach sub-skills") to further reduce overlap with the individual sub-skills it names in the body.

DimensionReasoningScore

Specificity

The description lists five concrete pipeline actions — "detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign" — giving comprehensive coverage of the workflow. It clearly matches the score-5 anchor ('multiple specific concrete actions; comprehensive coverage') and is well above anchor 4, since no meaningful capability of the pipeline is omitted.

5 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It fits anchor 3 ('clear what but when is missing or only weakly implied') and is not anchor 4 because no explicit usage-trigger statement exists anywhere in the description.

3 / 5

Trigger Term Quality

Terms like "outbound prospecting", "intent signals", and "campaign" are relevant, but common natural phrases users would say — "cold email", "lead generation" / "lead gen", "B2B outreach", "find leads" — are absent. This matches anchor 3 ('some relevant keywords but missing common variations or synonyms'); it is above anchor 2 because the keywords present are domain-specific rather than generic, but below anchor 4 because several natural trigger phrases are missing.

3 / 5

Distinctiveness Conflict Risk

"End-to-end outbound prospecting" carves out a distinct orchestration niche with specific pipeline triggers. It is not a 5 because the pipeline phases (contact finding, cold-email outreach) overlap semantically with the individual sub-skills it orchestrates, creating minor conflict risk with closely related skills — exactly anchor 4. It is above anchor 3 since the full-pipeline framing is far more specific than a generic 'works with outreach' claim.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.