CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyst-overview

Root pointer for the analyst's vulnerability research playbooks and catalog of vuln-class and chain-building skills.

Quality

71%

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

Quality

Content

82%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.

This is a well-built router/catalog skill: token-efficient tables, concrete per-scenario skill paths, and clean section organization. The main weaknesses are external — the referenced playbook paths don't resolve in the bundle — plus minor workflow gaps around unmatched lanes and iteration.

Suggestions

Anchor the catalog paths relative to the skill tree root (or document the path convention) so the referenced playbooks can be validated and resolved at load time.

Add a fallback line for lanes not in the table, e.g. "If no row matches, hunt generically and revisit this catalog once a weakness class emerges".

Add one sentence on iteration — when to return to this catalog after a playbook run — since the frontmetadata advertises 'routing iteration' but the body never explains it.

DimensionReasoningScore

Conciseness

The body is lean tables and one-line scoping instructions ("Load the one matching your current hunting lane — don't load them all at once") with zero explanation of concepts Claude already knows and no padding. Every row carries routing information; this matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete, copy-paste-loadable skill paths are mapped to specific hunting conditions (e.g. "/skills/standard/analyst/sql-injection/SKILL.md | String-concat + format-string → SQL sink"), covering 11 vuln classes and 4 chains. It falls short of 5 because the referenced paths do not resolve in this skill's bundle/tree, and there is no guidance for what to do when no table row matches the observed lane.

4 / 5

Workflow Clarity

The sequence is clear: identify the target's language/framework, select the matching vuln-class skill, and combine individual findings via chain playbooks whose "prerequisites and effects can be combined into a complete impact path". Minor gaps keep it at 4 rather than 5: no fallback when no skill matches, and no iteration/re-entrancy guidance even though the frontmatter's when_to_use mentions 'routing iteration start'.

4 / 5

Progressive Disclosure

Well-organized sections (taint/source-review, research expansion, chains, technique selection) with one-level-deep, clearly signaled references — exactly the structure a catalog skill should have. It is not 5 because the referenced sibling paths (/skills/standard/analyst/...) are absolute and cannot be validated against the actual tree from this skill's location, leaving navigation correctness unverifiable.

4 / 5

Total

17

/

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 communicates a clear niche role (router/catalog for vulnerability research playbooks) but is mediocre across all dimensions: it lacks any 'Use when' trigger clause, uses internal jargon ('root pointer', 'vuln-class') over natural user phrases, and doesn't distinguish when this root skill should fire versus its child playbooks. All dimensions land at the midpoint.

Suggestions

Add an explicit trigger clause, e.g. "Use when starting vulnerability research, choosing a hunting playbook, or combining individual findings into an exploit chain" — this would raise completeness from the capped 3.

Replace internal jargon like "root pointer" and "vuln-class" with natural user phrases such as "security research", "bug hunting", and "exploit chains" to improve trigger term quality.

Clarify the boundary with child skills, e.g. "Use this first to pick the right playbook; load the specific playbook once the weakness class is identified" to reduce conflict risk with the cataloged skills.

DimensionReasoningScore

Specificity

"Root pointer for the analyst's vulnerability research playbooks and catalog of vuln-class and chain-building skills" names a specific domain (vulnerability research, chain-building) and one concrete function (routing/cataloging), but lists no further concrete actions. It sits at the 'names domain and 1-2 concrete actions' anchor — above 2 because the domain is specific and the pointer/catalog function is stated, below 4 because it doesn't enumerate several specific capabilities.

3 / 5

Completeness

The 'what' is stated (root pointer / catalog of playbooks) but the 'when' is entirely absent — there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. It is not 4 because the 'when' is not even weakly implied in the description text, and not 2 because the 'what' is reasonably clear.

3 / 5

Trigger Term Quality

Relevant keywords like "vulnerability research" and "chain building" are present, but common variations users would naturally say ("security research", "bug hunting", "exploit chains", "finding chains") are missing, and "root pointer" and "vuln-class" are internal jargon rather than user phrases. This matches the 'some relevant keywords but missing common variations' anchor — not 4, since the natural-term coverage has clear gaps.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a niche (the analyst's routing hub), but its trigger territory ("vulnerability research") overlaps with the very child skills it catalogs, so it could fire when a specific playbook is the better target. This matches 'somewhat specific but could still overlap with similar skills' — below 4 due to the deliberate overlap with its own children's triggers.

3 / 5

Total

12

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/analyst/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.