CtrlK
BlogDocsLog inGet started
Tessl Logo

ctf-triage

CTF challenge triage and solve methodology — category detection, tool selection, and multi-step solve chains across pwn/rev/crypto/forensics/web/misc.

62

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

Quality

Content

80%

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 lean, highly actionable command-driven CTF reference with clear phased sequencing, but it is a monolithic single file with limited progressive disclosure and missing explicit validation checkpoints in its destructive operations.

Suggestions

Add explicit validation checkpoints within destructive phases (e.g., confirm the crash offset before building a payload, verify extracted artifacts before analysis) to turn the implicit workflow into validate->fix->retry loops.

Split per-category detail (pwn, rev, crypto, forensics) into one-level-deep reference files linked from a concise overview, improving progressive disclosure for a 340-line skill.

Surface the two external skill pointers (exploit/web/, reverser/packer-unpacking) in a dedicated 'Related skills' navigation section rather than burying them inline.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands, code snippets, and compact tables with minimal prose, and avoids explaining concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

Provides fully executable commands and copy-paste-ready scripts (pwntools, angr, tshark, volatility, ROPgadget) with specific flags; the few placeholders (<modulus>, <PID>) are clearly marked and contextually necessary.

3 / 3

Workflow Clarity

A clear phased sequence and an ordered solve-workflow summary exist, but destructive/batch operations (exploitation, file carving, memory dumping) lack explicit per-phase validation checkpoints and feedback loops, capping this at 2.

2 / 3

Progressive Disclosure

The ~340-line skill is a well-sectioned but monolithic single-file reference that keeps all per-category detail inline; the two external pointers are to other skills rather than a one-level-deep split of this skill's own detail.

2 / 3

Total

10

/

12

Passed

Description

67%

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 clearly scoped to CTF challenges with concrete actions and a distinct niche, but it omits an explicit 'Use when...' trigger clause and relies on jargon/abbreviations rather than natural-language trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when solving CTF challenges, capture-the-flag problems, or analyzing challenge files in pwn, rev, crypto, forensics, web, or misc categories.'

Replace slash-abbreviated trigger terms with natural phrasing a user would say ('binary exploitation', 'reverse engineering', 'steganography') to improve trigger_term_quality.

Expand 'triage and solve methodology' jargon into concrete user-facing verbs to reinforce the when-to-use trigger.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions ('category detection, tool selection, and multi-step solve chains') plus an enumerated category list (pwn/rev/crypto/forensics/web/misc), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does but lacks any 'Use when...' clause or explicit trigger guidance in the description field, capping completeness at 2 per the missing-trigger guideline.

2 / 3

Trigger Term Quality

Contains relevant CTF keywords (CTF, pwn, rev, crypto) but presents them as slash-abbreviations and 'triage...methodology' jargon rather than natural user phrasing, so it only partially covers terms users would say verbatim.

2 / 3

Distinctiveness Conflict Risk

'CTF challenge triage and solve methodology' with an explicit category enumeration is a clear niche unlikely to trigger for the wrong, non-CTF skill.

3 / 3

Total

10

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.