CtrlK
BlogDocsLog inGet started
Tessl Logo

ghidra-reverse

Use for free/open reverse engineering with Ghidra (headless or GUI), including decompile, cross-refs, and optional Ghidra MCP workflows when IDA is unavailable.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A compact, well-structured skill body with a concrete headless command and a useful cheat sheet, but it leans on an un-provided script and external files while lacking validation checkpoints for batch operations.

Suggestions

Add an inline validation/checkpoint step in the headless batch workflow (e.g. verify the export file exists and is non-empty before proceeding), since batch operations should not proceed without confirmation.

Either bundle the referenced ExportDecomp.py script or inline a minimal version so the headless example is fully copy-paste ready rather than dependent on a missing file.

Resolve the external first-step references (../field-journal/precedent-reverse.md, ../tool-index.md): either include them in the bundle or replace them with self-contained guidance so navigation does not depend on files outside the skill.

DimensionReasoningScore

Conciseness

The body is lean — checklists, tables, and one short command — with no padding or explanations of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Provides one concrete executable command and points to a real shortcut cheat sheet, but references an un-provided ExportDecomp.py script and leaves several steps as abstract checkboxes, so key details are missing.

2 / 3

Workflow Clarity

Four numbered phases plus a final self-check give a clear sequence, but there are no inline validation checkpoints for the headless batch operation, which caps workflow clarity at 2.

2 / 3

Progressive Disclosure

Sections are well-organized and the in-bundle references/ghidra-cheatsheet.md is clearly signaled, but the critical first 'ACTION REQUIRED' steps point to external files (../field-journal/precedent-reverse.md, ../tool-index.md) absent from the bundle, making navigation uncertain.

2 / 3

Total

9

/

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.

A strong, concise description that states concrete capabilities and an explicit trigger condition with natural keywords. It cleanly distinguishes Ghidra from IDA and other RE tools.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'decompile, cross-refs', 'headless or GUI', and 'Ghidra MCP workflows' — rather than vague language, matching the anchor for naming several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('decompile, cross-refs… MCP workflows') and when via the 'Use for… when IDA is unavailable' trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ('reverse engineering', 'Ghidra', 'decompile', 'cross-refs', 'IDA') with good coverage of common variations, not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (free/open Ghidra RE) and is explicitly contrasted with IDA, making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
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.