CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

scanner-overview

Stage 1 broad-spectrum scanner playbook. Sharded sweep over very large codebases producing CANDIDATE nodes for the Detector to reason about. Load at scanner-agent startup.

Quality

70%

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 ./packages/decepticon/decepticon/skills/plugins/scanner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 concise, actionable, and well-structured, but its batch workflow lacks an explicit validation/sanity-check checkpoint before candidate promotion, which caps workflow clarity. Adding a verify step would materially raise the score.

Suggestions

Insert an explicit validation checkpoint in the workflow (e.g., dedupe/sanity-check ranked candidates before kg_add_candidate, and re-run scan_shard if a shard returns empty).

Make the workflow fully copy-paste ready by inlining the shard_total selection (e.g., 'pick N from the table above') so step 3 is executable as written.

Tighten the operating-principles prose by dropping the justificatory clauses ('burns tokens and context', 'token budget is precious').

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanation of what sinks are), with only minor justificatory asides like 'Hand-rolled ripgrep through bash burns tokens and context' that could be trimmed.

4 / 5

Actionability

Concrete commands and a shard_total decision table are provided, and the numbered workflow names specific tools (scan_shard, rank_candidates, kg_add_candidate); it stops short of fully copy-paste-ready code because shard count N is resolved via the table rather than inline.

4 / 5

Workflow Clarity

A clear numbered sequence exists, but this is a batch operation over 10^4–10^6 files with no validation/verification checkpoint before promoting candidates, so workflow clarity is capped at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

Sections are well-organized with a clearly signaled pointer to the external regex table (scanner_tools.py); no bundle files exist to split further, and structure is good, but the lone external reference keeps it just short of a 5.

4 / 5

Total

15

/

20

Passed

Description

58%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 distinctive about its pipeline role, but lacks an explicit user-facing 'Use when...' trigger and relies on internal jargon for its trigger terms. Adding a natural-language trigger clause would lift completeness and trigger-term quality.

Suggestions

Append an explicit 'Use when ...' clause naming natural user triggers (e.g., 'Use when launching a broad codebase sweep for vulnerable code locations').

Replace or supplement internal jargon ('CANDIDATE nodes', 'Detector') with terms a user would naturally say ('suspicious code locations', 'downstream analysis').

Add common synonyms/file-agnostic phrasing to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Stage 1 broad-spectrum scanner') and several concrete actions ('Sharded sweep over very large codebases producing CANDIDATE nodes'), with only minor gaps in coverage; not quite the comprehensive multi-action list of a 5.

4 / 5

Completeness

The 'what' is clear (sharded sweep producing CANDIDATE nodes), but the only 'when' guidance is 'Load at scanner-agent startup', which is a load-time directive rather than an explicit user-trigger 'Use when...' clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Relevant domain keywords ('scanner', 'sharded sweep', 'codebases', 'CANDIDATE') appear, but the phrasing leans toward internal jargon ('CANDIDATE nodes', 'Detector') and omits common natural variations a user would actually say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche ('Stage 1 broad-spectrum scanner' feeding a 'Detector'), making it mostly distinct from sibling pipeline stages, with only minor overlap risk against related scanner skills.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/plugins/scanner/SKILL.md

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.