outbound-prospecting-engine

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

Quality

73%

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

Quality

Content

75%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 content is a well-structured, concise orchestration playbook with concrete per-step skill references and explicit human checkpoints. Its main weakness is reliance on delegated skills for executable detail rather than inline commands or examples.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, using short step descriptions and a compact signal-source table rather than over-explaining concepts, with only minor phrasing that could be trimmed.	4 / 5
Actionability	Each step names a concrete skill (lead-qualification, company-contact-finder, cold-email-outreach) and gives specific sub-actions like "Get email addresses and LinkedIn URLs", though it relies on delegated skills rather than inline executable detail.	4 / 5
Workflow Clarity	An explicit 8-step sequence is present with Human Checkpoints after Steps 3, 6, and 8 plus a Monitor & Iterate feedback loop, satisfying validation for this batch operation; minor gaps remain in automated verification detail.	4 / 5
Progressive Disclosure	Content is well organized into When to Use, Prerequisites, Steps, Ongoing Cadence, and Human Checkpoints with no nested references; as an orchestrating playbook it is appropriately self-contained, with only minor organization gaps.	4 / 5
	Total	16 / 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.

The description is specific and distinct, naming a clear multi-step action set, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. It is written in appropriate third-person imperative voice.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers, e.g. "Use when setting up outbound prospecting, building a lead-gen engine, or finding and reaching out to target companies."

Include common synonyms such as "lead generation", "cold email", and "sales outreach" to broaden natural trigger-term coverage.

Tighten distinctiveness by foregrounding the orchestration angle (e.g. "coordinates signal, qualification, and outreach skills") to reduce overlap with the individual sub-skills.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions ("detect intent signals, research companies, find decision-maker contacts, personalize messaging, launch campaign"), giving comprehensive coverage of the prospecting workflow.	5 / 5
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms like "outbound prospecting", "intent signals", and "decision-maker contacts", but omits common synonyms users might say such as "lead gen", "cold email", or "sales outreach".	4 / 5
Distinctiveness Conflict Risk	"End-to-end outbound prospecting" carves a clear niche with distinct triggers, though terms like "research companies" and "intent signals" create minor overlap risk with the individual signal skills it orchestrates.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/outreach/playbooks/outbound-prospecting-engine/SKILL.md
Commit: 2523432

Reviewed: 7 days 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.