CtrlK
BlogDocsLog inGet started
Tessl Logo

signal-detection-pipeline

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

66

Quality

80%

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

100%

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: concise, highly actionable, with a clear sequenced workflow and an explicit human validation checkpoint. It is a strong example of an instruction-only skill that earns a top score across all content dimensions.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — each source is a compact Input/Output block with a one-line rationale, and it never explains concepts Claude already knows, matching the score-3 anchor where every token earns its place.

3 / 3

Actionability

It names the exact sub-skills to invoke, their inputs and outputs, concrete scoring combinations ("Job posting + funding = highest intent"), and the precise Google Sheet columns to populate — fully actionable, copy-ready guidance.

3 / 3

Workflow Clarity

"Combining Signals" is a clearly numbered 5-step sequence (deduplicate → score → enrich → consolidate → prioritize) with an explicit validation checkpoint under "Human Checkpoints" for the batch consolidation step.

3 / 3

Progressive Disclosure

Content is well-organized into clearly signaled sections, and the only references are one-level-deep pointers to named sub-skills with no nested bundle indirection, so navigation is straightforward.

3 / 3

Total

12

/

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, but it omits an explicit "Use when..." trigger clause, which caps both completeness and trigger-term quality. Adding natural user-facing trigger phrasing would lift the weakest dimensions.

Suggestions

Append a "Use when..." clause naming natural user triggers, e.g. "Use when finding companies in-market for a solution, qualifying leads, or preparing outreach context for [problem area]."

Add common trigger variations users would actually say ("find buying signals", "qualify leads", "lead generation pipeline") to broaden trigger-term coverage.

Sharpen distinctiveness by noting the multi-source combining behavior so it is less likely to conflict with single-source lead skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Detect buying signals from multiple sources, qualify leads, and generate outreach context" — each tied to a clear object, matching the score-3 anchor for listing several specific actions.

3 / 3

Completeness

It clearly answers "what does this do" but offers no explicit "when should Claude use it" guidance; per the judging guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Terms like "buying signals", "qualify leads", and "outreach context" are reasonably natural, but there is no "Use when..." clause and common user phrasings (e.g. "find buying signals", "lead qualification") are missing, so coverage is partial rather than comprehensive.

2 / 3

Distinctiveness Conflict Risk

The sales-signal niche is somewhat specific, but with no explicit triggers in the description it could overlap with other lead-generation or outreach skills, matching the score-2 anchor of being specific yet still overlapping.

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.