CtrlK
BlogDocsLog inGet started
Tessl Logo

scan-signals

Use when reviewing supplied dated evidence for recent account signals, buying-context changes, or a manual weekly pulse.

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/scan-signals/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured, lean instruction skill with a clearly sequenced, validation-rich workflow and a concrete output template; its only weak spot is slight verbosity in the guardrail list.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining what accounts or signals are; a few guardrail bullets could be condensed further, keeping it just short of fully lean.

4 / 5

Actionability

It provides concrete, executable guidance — a numbered workflow, an explicit output-format template, and a quality check — though as an instruction-only skill it lacks code, which is acceptable here.

4 / 5

Workflow Clarity

The seven-step workflow is clearly sequenced with explicit validation checkpoints (date separation, TIMING UNVERIFIED labels, exclusion of uncited/out-of-window items, eligibility gating) and a closing quality-check loop.

5 / 5

Progressive Disclosure

Under 50 lines with no external references needed, the content is organized into well-signaled sections (Purpose, Required inputs, Workflow, Output format, Guardrails, Quality check), meeting the simple-skill bar for a top score.

5 / 5

Total

18

/

20

Passed

Description

62%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 clearly signals a specialized niche (time-bounded account-signal review) with an explicit 'Use when' trigger, but its 'what' is somewhat abstract and the trigger-term vocabulary is narrow.

Suggestions

Enumerate the concrete outputs the skill produces (e.g. 'Produce a manual seven-day pulse with ranked signals, excluded candidates, and a next-pulse checklist') to raise specificity.

Add natural user-facing synonyms to the trigger clause (e.g. 'account activity', 'engagement signals', 'weekly review').

Tighten the 'what' so it pairs unambiguously with the existing 'when' clause.

DimensionReasoningScore

Specificity

It names the domain ('account signals', 'buying-context changes', 'manual weekly pulse') and one concrete action ('reviewing supplied dated evidence'), but the actions remain fairly abstract rather than a comprehensive list of specific operations.

3 / 5

Completeness

It explicitly answers 'when' via the 'Use when reviewing supplied dated evidence for recent account signals...' clause and gives a clear 'what', though the 'what' could be more explicitly enumerated to reach full clarity.

4 / 5

Trigger Term Quality

Relevant domain terms like 'account signals', 'buying-context changes', and 'manual weekly pulse' appear, but common synonyms or phrasings a user might naturally vary are missing.

3 / 5

Distinctiveness Conflict Risk

The niche framing around dated account signals and manual pulse is fairly distinct with only minor overlap risk against related account-monitoring skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
llaskin/AI-SDR-Skill-Pack
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.