reverse-skill-router

Use the reverse-skill repository from Codex for authorized reverse engineering, security analysis, CTF, and defensive testing tasks. Requires the reverse-skill repository to be available as the current workspace or an explicitly supplied local path.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/reverse-skill/skills/reverse-skill-router/SKILL.md

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.

The body is a tight, well-sequenced adapter that delegates to the canonical repository with concrete script and path references and an explicit scope-validation checkpoint. Its main gaps are the absence of exact command invocation syntax and an error-recovery feedback loop after validation.

Suggestions

Add the exact invocation syntax for the platform-native scripts (e.g., how 'master-route' receives the user's task) to make guidance fully copy-paste executable.

Include a brief feedback loop after the step 3 validation (e.g., 'If case-guard rejects the scope, revise scope.md and re-run case-guard before proceeding').

Add a couple of section headers (e.g., '## When the workspace is reverse-skill', '## Fallback') to formalize the structure for navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line is either an actionable step, a fallback, or a guardrail, so each token earns its place.	5 / 5
Actionability	It points to concrete paths and named scripts (master-route, case-init, case-guard, routing.json, scope.md, tool-index.md), but exact invocation syntax for those scripts is not given, leaving minor gaps in copy-paste executability.	4 / 5
Workflow Clarity	A clear numbered 1-5 sequence is present with an explicit validation checkpoint in step 3 ('create and validate work/<case>/scope.md' via case-guard), but there is no feedback loop describing what to do if validation fails, so it falls just short of 5.	4 / 5
Progressive Disclosure	This short adapter is well-organized and delegates detail to one-level-deep references in the canonical repo (RULES.md, skills/<PRIMARY>/SKILL.md, tool-index.md) with no nested indirection, though it lacks formal section headers beyond the title and prose blocks.	4 / 5
	Total	17 / 20 Passed

Description

61%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 is specific and distinct, naming a clear niche and natural domain trigger terms, but it lacks an explicit 'Use when...' trigger clause and leans on task categories rather than concrete actions. Completeness is capped at 3 by the missing trigger guidance.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when the user requests authorized reverse engineering, security analysis, CTF, or defensive testing within the reverse-skill repository') to raise completeness.

Replace task-category phrasing with concrete actions where possible (e.g., 'disassemble', 'analyze binaries', 'solve CTF challenges') to improve specificity.

Include common synonyms or file extensions users might mention (e.g., 'binary analysis', 'malware analysis', '.exe/.elf') to broaden trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several task categories ('reverse engineering, security analysis, CTF, and defensive testing tasks'), but these are task domains rather than concrete actions like 'extract' or 'fill', so it stops at naming domain plus a few task types.	3 / 5
Completeness	It clearly states what the skill does, but there is no explicit 'Use when...' trigger clause; the 'Requires the reverse-skill repository...' sentence is a precondition, not a usage trigger, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Natural domain terms ('reverse engineering', 'security analysis', 'CTF', 'defensive testing') are present and would be said by users, but synonyms and file/extension variations are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	'reverse-skill repository from Codex' is a distinct niche with specific triggers, though it could overlap with other security/RE skills, so it is mostly distinct with minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zhaoxuya520/reverse-skill
Path: plugins/reverse-skill/skills/reverse-skill-router/SKILL.md
Commit: 7e2097f

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.