signal-detection-pipeline

Detect buying signals from multiple sources, qualify leads, and generate outreach context

Quality

61%

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/lead-generation/playbooks/signal-detection-pipeline/SKILL.md

Quality

Content

72%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 lean, well-structured orchestration playbook with concrete per-source skill pointers and a human checkpoint, but the consolidation workflow is high-level and lacks validation for a batch operation. Adding executable specifics for the combine step and a verification loop would raise actionability and workflow clarity.

Suggestions

Make the consolidation step executable: specify the Google Sheet tool/script and the exact columns to populate, rather than naming them inline as prose.

Add a validation/verification checkpoint after consolidation (e.g., confirm dedup ran, verify row count against source totals, spot-check top leads) to lift workflow clarity above the batch-operation cap of 3.

Provide one concrete scoring rubric or threshold for signal strength instead of the qualitative examples, so the "Score" step is repeatable rather than interpretive.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet-driven, assuming Claude's competence with no padding or explanation of concepts Claude already knows, matching anchor 5; every line earns its place, so it is not downgraded to 4.	5 / 5
Actionability	It names a concrete skill per signal source with explicit Input/Output, but the combine-and-consolidate steps remain high-level ("Score each lead", "Enrich with web search") without executable specifics, fitting anchor 3; it is not 4 because key execution details (which tool, what command, how to write the sheet) are missing, and not 2 because the per-source skill pointers are concrete.	3 / 5
Workflow Clarity	The sequence is clearly listed (run sources in parallel, then dedupe/score/enrich/consolidate/prioritize) with one explicit human checkpoint, but this batch consolidation into a Google Sheet lacks validation/verification steps beyond that single checkpoint, so per the rubric cap for batch operations it sits at anchor 3 rather than 4.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no external bundle files and is organized into clearly labeled sections (When to Use, Signal Sources, Combining Signals, Human Checkpoints), so per the simple-skill scoring note it qualifies for anchor 5.	5 / 5
	Total	16 / 20 Passed

Description

50%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 concise and names three concrete actions in a distinct niche, but it omits any explicit "Use when..." trigger guidance and relies on generic terms that limit trigger-term quality and distinctiveness. Adding a concrete trigger clause would lift completeness and trigger coverage.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to find companies in-market for a solution, run buying-signal detection, or build a qualified lead list."

Add natural user phrasings as trigger terms ("find companies that need", "lead generation", "prospecting") to improve trigger-term quality beyond anchor 3.

Sharpen distinctiveness by naming the multi-source combination angle ("combines job postings, funding, and social signals") so it does not overlap with single-source lead skills.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ("Detect buying signals", "qualify leads", "generate outreach context"), which sits between the anchor 3 (1-2 actions) and anchor 4 (several actions with minor gaps); it is not above 4 because the actions are terse without elaboration, and not below 3 because it does name multiple concrete verbs.	3 / 5
Completeness	It has a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3; it is not a 4 because the "when" is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	It includes some relevant natural keywords ("buying signals", "leads", "outreach") but misses common user phrasings like "find companies that need X" or "lead generation", matching anchor 3 rather than 4 which requires good keyword coverage with only a few natural terms missing.	3 / 5
Distinctiveness Conflict Risk	The buying-signal/lead-qualification niche is somewhat specific but could still overlap with other sales-prospecting skills, fitting anchor 3; it is not 4 because the generic terms ("leads", "outreach") leave non-trivial overlap risk with adjacent skills.	3 / 5
	Total	12 / 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/lead-generation/playbooks/signal-detection-pipeline/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.