CtrlK
BlogDocsLog inGet started
Tessl Logo

ctf-reverse

Provides reverse engineering techniques for CTF challenges. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.

78

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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-organized reverse-engineering quick reference: lean inline commands and a triage workflow, supported by a clearly signaled one-level-deep file index. It assumes Claude's competence and avoids concept re-explanation.

DimensionReasoningScore

Conciseness

The body is lean and command-driven — "strings binary | grep -E", "b *main+0xca", "x/s $rsi" — with no concept explanations Claude already knows; the dense reference index is purposeful navigation rather than padding.

3 / 3

Actionability

It provides copy-paste-ready commands across static and dynamic analysis (r2, GDB, ltrace/strace, angr, Frida) plus concrete patterns such as "XOR with position index (^ i or ^ (i & 0xff))", fully executable guidance.

3 / 3

Workflow Clarity

The numbered "Problem-Solving Workflow" is a clear escalation ladder (strings → ltrace/strace → Frida → angr → Qiling → map control flow → automate → validate) with an explicit validation step ("Validate assumptions by comparing decompiler outputs") and a "When to Pivot" redirect table.

3 / 3

Progressive Disclosure

It is a concise overview (Quick Wins, workflow, quick reference) plus a categorized, one-level-deep index of ~20 supporting files each with a one-line description, matching the anchor-3 pattern of well-signaled single-depth references.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 third-person, concise, and tightly scoped: it states concrete capabilities, natural trigger terms, clear use-conditions, and explicit boundaries against adjacent skills. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

"Provides reverse engineering techniques" names the action, and it enumerates concrete target types — "binaries, APKs, WASM, firmware, custom VMs, bytecode, game clients, malware-like loaders, and anti-debug or anti-analysis logic" — far more comprehensive than the anchor-2 example.

3 / 3

Completeness

It states both what ("reverse engineering techniques for CTF challenges") and when ("Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works"), plus explicit negative triggers ("Do not use it when the vulnerability is already understood... use pwn instead").

3 / 3

Trigger Term Quality

Natural terms a user would say in a CTF/RE context are well covered: "reverse engineering", "CTF challenges", "obfuscated, packed, or virtualized", "APKs", "WASM", "firmware", "custom VMs", "anti-debug", matching the anchor-3 breadth.

3 / 3

Distinctiveness Conflict Risk

The CTF reverse-engineering niche is sharply bounded with explicit disambiguation against pwn, web, forensics, crypto, and malware skills, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 19 missing

Warning

Total

14

/

16

Passed

Repository
ljagiello/ctf-skills
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.