CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyst-specialist-methods

Evidence-led analyst technical methods and evidence interpretation for the relevant environment.

Quality

62%

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/specialist-methods/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 an exemplar of token-efficient reference writing: dense with non-obvious evidentiary guidance, well-organized into three sections, and appropriately sized to need no bundle files. Its weakness is actionability — it states criteria and caveats but defers all implementation detail to other skills without commands, procedures, or an ordered checklist. As intentionally declarative notes rather than a workflow, it partially escapes the workflow-clarity anchors, but no sequence or validation loop is offered for tasks like crash minimization or patch comparison.

Suggestions

Add one compact concrete procedure for the most execution-heavy topic, e.g., the exact commands to minimize a fuzzer crash and preserve the seed ('afl-tmin -i crash -o minimized -- ./target @@'), so the fuzzing section is executable rather than purely cautionary.

Give the patch-comparison section a short ordered checklist (pin exact revisions → diff with callers and surrounding code → record build flags and runtime versions → verify the changed behavior) with an explicit verification step before concluding a bug is real.

DimensionReasoningScore

Conciseness

The body is dense and lean with zero padding: every sentence carries non-obvious information such as the fuzzing tool mapping (libFuzzer/AFL++, Atheris, Jazzer, cargo-fuzz) and evidentiary caveats ('A crash is not by itself arbitrary code execution'). It assumes Claude's competence throughout, matching the anchor 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

There are concrete elements (semgrep/SARIF candidate handling, the kg_ingest("sarif", path) call, specific fuzzers per runtime, 'retain sanitizer output and seed'), but no executable commands or step-level procedures, and implementation is deferred to unspecified 'existing skills'. Anchor 3 ('Some concrete guidance but incomplete; missing key details') fits better than 4, which expects mostly executable guidance.

3 / 5

Workflow Clarity

The body explicitly disclaims stage ordering ('they do not define an engagement stage order') and its three sections are standalone guidance notes with no sequenced steps or validation checkpoints. The organization per topic is clear, matching anchor 3 ('sequence present but checkpoints missing or implicit') as reference material, but no multi-step workflow is articulated, so it cannot score higher.

3 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files, so nothing needs offloading; sections are well-organized with headers, and cross-skill pointers ('use the existing analyst vulnerability-class skills', 'trust-boundary and pattern-exhaustion skills') are clearly signaled one level deep. Per the simple-skill guideline this matches the anchor for a clear, well-organized overview.

5 / 5

Total

16

/

20

Passed

Description

36%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 names its domain but gives no concrete capabilities, no natural trigger phrases, and no use-when guidance, functioning more as a topic label than a skill description. Users asking for vulnerability triage, fuzzing, or patch comparison would not naturally match this text. It is third-person and concise, but its usefulness for triggering depends on the metadata when_to_use field rather than the description itself.

Suggestions

Rewrite the description to lead with the concrete capabilities from the body, e.g., 'Performs source taint analysis, dependency/advisory matching, patch comparison, and fuzzing with evidence standards for security analyst engagements.'

Add an explicit 'Use when...' clause with natural trigger terms users actually say, such as 'Use when triaging vulnerabilities, matching advisories to installed dependencies, diffing security patches, or setting up fuzzing harnesses.'

Remove the vague tail 'for the relevant environment', which adds no information a user or dispatcher could act on.

DimensionReasoningScore

Specificity

The description names the domain ("analyst technical methods", "evidence interpretation") but lists no concrete actions, and "for the relevant environment" is generic filler. This matches the anchor 'Names the domain but actions are minimal or generic' rather than level 3, which requires at least one or two concrete actions.

2 / 5

Completeness

The 'what' is vague ("technical methods and evidence interpretation") and there is no 'Use when...' clause; "for the relevant environment" does not function as a trigger. This matches anchor 2 ('Has a vague what and no when'), and the missing trigger guidance independently caps completeness at 3, which the vague what falls below.

2 / 5

Trigger Term Quality

"analyst" and "evidence" are terms a user might naturally say, but the description misses the common phrases that would trigger this skill (e.g., vulnerability, fuzzing, patch diff, taint analysis, triage). Anchor 3 ('Some relevant keywords but missing common variations or synonyms') fits better than 4, since keyword coverage is thin rather than good with a few gaps.

3 / 5

Distinctiveness Conflict Risk

The "analyst" scoping gives it some distinctness within a security-engagement skill set, but "technical methods and evidence interpretation" is broad enough to overlap with other analyst, evidence-review, or methodology skills. Anchor 3 ('Somewhat specific but could still overlap with similar skills') is the best fit — not 4, since no concrete capability anchors the niche.

3 / 5

Total

10

/

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/specialist-methods/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.