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.

59

Quality

68%

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

77%

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 concise, well-sequenced playbook with clear human checkpoints and good structural organization. Its main weaknesses are a lack of executable guidance (code/commands) and no progressive disclosure into reference files, leaving it as a single monolithic document.

Suggestions

Add at least one executable snippet or concrete command (e.g., a sample signal-skill invocation with keywords) to lift actionability to copy-paste ready.

Extract dense detail such as the signal-source table or the personalization framework into reference files under references/ and link to them from the overview.

Specify concrete inputs/outputs for each step (e.g., expected lead schema, qualification scoring formula) to make the guidance fully actionable.

DimensionReasoningScore

Conciseness

The body is lean and efficiently organized with no conceptual padding, assuming Claude's competence and earning every token via tight step descriptions and tables.

3 / 3

Actionability

It names specific companion skills and lists concrete sub-tasks, but provides no executable code, commands, or arguments — guidance is directional rather than copy-paste ready.

2 / 3

Workflow Clarity

The 8-step process is clearly sequenced with explicit human checkpoints after Steps 3, 6, and 8, providing the validation gates the rubric rewards.

3 / 3

Progressive Disclosure

The single-file playbook is well sectioned, but no bundle files exist and the inline content (signal-source table, cadence, checkpoints) could be split into references; navigation to detail is not signaled.

2 / 3

Total

10

/

12

Passed

Description

60%

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 action-oriented, clearly conveying the end-to-end outbound workflow, but it lacks an explicit 'Use when...' trigger clause and natural user-facing keywords. Adding trigger guidance and common phrasing like 'lead gen' or 'cold outreach' would raise completeness and distinctiveness.

Suggestions

Add a 'Use when...' clause with natural triggers (e.g., 'Use when the user asks to build a lead gen engine, find companies that need a solution, or run cold email outreach').

Include common user phrasings such as 'lead gen', 'cold outreach', and 'email campaigns' to broaden trigger-term coverage.

Reframe in consistent third person and lead with a verb phrase to sharpen distinctiveness from adjacent sales skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign' — matching the highest anchor for specific concrete actions.

3 / 3

Completeness

It clearly answers 'what' the skill does but omits any 'Use when...' clause or explicit trigger guidance, which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

It uses relevant domain terms ('outbound prospecting', 'decision-maker contacts') but misses natural user variations like 'lead gen', 'cold email', or 'find leads', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The prospecting niche is somewhat specific, but without explicit trigger terms it could still overlap with related sales or lead-gen skills, so it does not reach the clear-niche anchor.

2 / 3

Total

9

/

12

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.

Validation15 / 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.