CtrlK
BlogDocsLog inGet started
Tessl Logo

signal-detection-pipeline

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

57

Quality

72%

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

Quality

Content

78%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 tight, well-structured orchestration playbook with concrete skill invocations, inputs/outputs, a clear combining workflow, and an explicit human checkpoint. The only meaningful gaps are the undefined signal-strength scale and the undefined 'top leads' cutoff in the enrichment step.

DimensionReasoningScore

Conciseness

The body is lean — each signal source gets a one-line rationale plus input/output, with no padding or explanation of concepts Claude already knows. A slightly redundant intro sentence ("Combine signals for higher-confidence leads" duplicates the Combining Signals section) keeps it just below the 'every token earns its place' anchor.

4 / 5

Actionability

Concrete, executable orchestration guidance: named skills per source with explicit inputs and outputs, and a consolidation step enumerating sheet columns (Company, Signal Sources, Signal Strength, Context, Outreach Angle). Minor gaps — no signal-strength scale is defined and "top leads" is left undefined — hold it below fully executable.

4 / 5

Workflow Clarity

A clearly sequenced workflow (run sources in parallel, deduplicate, score, enrich, consolidate, prioritize) with an explicit human checkpoint after combining. It is not a destructive or batch operation, but the scoring step lacks a feedback loop or validation detail, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed: the skill is a short, self-contained playbook with well-organized one-level sections and clearly named external skills. Per the simple-skill guidance, well-organized sections alone warrant the top score.

5 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, third-person 'what' with a distinct niche, but it entirely lacks a 'when to use' clause and has thin trigger-term coverage. It is serviceable but below the standard of the good examples, which pair concrete capabilities with explicit use-when triggers.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to find companies that need a product, run signal detection, research buying signals, or build a lead list for outreach."

Add natural synonyms users would actually say — "prospecting", "lead generation", "find in-market companies", "account research" — to broaden trigger-term coverage.

Make the actions more concrete: name the signal sources (job postings, funding, events, social posts) and the output artifact (e.g. a scored lead sheet) instead of "from multiple sources" and "outreach context".

DimensionReasoningScore

Specificity

Names the domain and three actions ("detect buying signals", "qualify leads", "generate outreach context"), but each stays at the business-process level without concrete mechanics, matching the '1-2 concrete actions but not comprehensive' anchor rather than the more mechanically concrete anchor 4.

3 / 5

Completeness

The 'what' is clear (detect signals, qualify leads, generate outreach context), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Buying signals", "leads", and "outreach" are natural terms, but common variations users would say ("prospecting", "find companies", "lead generation", "in-market") are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The buying-signal/lead-qualification niche is mostly distinct with only minor overlap risk against generic lead-generation or prospect-research skills; without explicit trigger phrases, anchor 4 fits better than 5.

4 / 5

Total

13

/

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.