reverse-skill-router

Routes reverse engineering, exploitation, penetration testing, malware, mobile, firmware, browser automation, documentation, and security tasks to the appropriate specialist skill. Use when a task spans modules or the correct reverse-skill entrypoint is unclear.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/SKILL.md

Quality

Content

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

A strong control/router SKILL body: it gives concrete executable commands, a clearly sequenced execution contract with explicit authorization gates and a self-check checklist, and well-signaled references into a real bundle. Its main weakness is redundancy — the routing sequence is restated three times and the inline module catalog duplicates a reference file — which costs conciseness tokens.

Suggestions

Collapse the routing sequence into a single authoritative block; the CRITICAL contract, 统一入口, and 任务完成自检 currently restate the same NOW/ACT/NEXT steps — cross-reference instead of repeating.

Move the ~50-row module catalog out of SKILL.md into references/domain-coverage-map.md (which already exists for this purpose) and keep only the top-level routing categories inline.

Replace placeholders like '<skill-root>' and '工具名' in the bootstrap examples with concrete resolved-path examples or a single explicit variable-definition line so the commands are directly copy-pasteable.

Dimension	Reasoning	Score
Conciseness	Dense with operational contracts, commands, and routing tables rather than padded with concepts Claude already knows, but it repeats the same routing sequence in three places and inlines a ~50-row module catalog that duplicates a reference file's purpose, so it could be tightened.	3 / 5
Actionability	Provides concrete, mostly copy-pasteable platform-specific commands (master-route scripts, bootstrap invocations) and real file paths backed by existing scripts, with minor gaps from placeholders like '<skill-root>' and unresolved routing targets.	4 / 5
Workflow Clarity	Clear NOW/ACT/NEXT sequenced contract with explicit hard gates (auth gate, force hard-door), a precedent read-order table, and a completion self-check checklist; close to 5 but the repeated restatements and a few implicit checkpoints keep it one notch down.	4 / 5
Progressive Disclosure	Good structure with well-signaled one-level-deep references (routing.md, tool-index.md, ops/, field-journal/, and a verified references/community-security-skills.md), with a minor gap that the large inline module table duplicates the role of references/domain-coverage-map.md.	4 / 5
	Total	15 / 20 Passed

Description

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

A well-formed third-person description that clearly states what the skill does and gives an explicit Use-when trigger, with good natural-language keyword coverage across the security/RE domain. The main weakness is that the action is a single abstract routing verb rather than multiple concrete capabilities, and the 'when' clause is a single condition rather than a rich set of triggers.

Dimension	Reasoning	Score
Specificity	Names the routing domain and enumerates a comprehensive list of sub-domains, but the action itself is a single abstract verb ('Routes ... to the appropriate specialist skill') rather than several distinct concrete actions, so it sits at the 3-anchor rather than 4-5.	3 / 5
Completeness	Explicitly answers both 'what' (routes security/RE tasks to specialist skills) and 'when' ('Use when a task spans modules or the correct reverse-skill entrypoint is unclear'), but the 'when' is a single somewhat narrow condition rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Strong keyword coverage with natural terms users would say ('reverse engineering', 'penetration testing', 'malware', 'firmware'), though it leans formal and omits common synonyms/shorthand (e.g. 'RE', 'pwn') and file-type cues.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche as a cross-module meta-router for RE/security, but by design overlaps with the many specialist skills it dispatches to and the broad 'security tasks'/'documentation' language widens the surface slightly.	4 / 5
	Total	15 / 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: skills/SKILL.md
Commit: 7e2097f

Reviewed: ~7 hours 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.