go-rust-reverse

Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.

Quality

86%

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

Quality

Content

72%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 content is token-efficient and well-structured with a sensible progression and a real one-level reference, but its workflow is checklist-only without concrete executable commands or validation checkpoints. Actionability and workflow_clarity are the limiting dimensions.

Suggestions

Add at least one concrete, copy-paste command per language (e.g. `GoReSym -t -d binary > symbols.json` or a strings/rabin2 one-liner) to move actionability toward executable.

Add an explicit validation/verify checkpoint in the workflow — e.g. "after recovery, confirm N key function names map or re-run GoReSym" — with a retry-on-fail feedback loop.

Replace the vague self-check bullets with pass/fail criteria tied to concrete artifacts (recovered function count, identified runtime evidence strings).

Dimension	Reasoning	Score
Conciseness	The body is lean checklist/table form with no concept explanations Claude already knows; every section earns its tokens.	3 / 3
Actionability	Names concrete tools (GoReSym, redress, radare2, rabin2) and specific techniques, but offers checklist action items rather than executable commands or copy-paste code, so it is not fully executable.	2 / 3
Workflow Clarity	A clear NOW/NEXT/ACT sequence and per-language sub-workflows exist, but checkpoints are implicit checkboxes with no explicit validation/verify gate or feedback loop.	2 / 3
Progressive Disclosure	The short body points to a real one-level-deep reference (references/go-rust-notes.md) and peer skill paths, with well-organized sections and easy navigation.	3 / 3
	Total	10 / 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 concise yet specific, naming concrete Go/Rust reverse-engineering actions and an explicit "Use for" trigger that addresses both what and when. It is clearly distinguishable and unlikely to mis-route. A minor typo ("moduel") does not materially affect the score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery" — across both Go and Rust, matching the multi-action anchor.	3 / 3
Completeness	"Use for ..." gives an explicit when-trigger and the action list answers what it does, satisfying both halves; it is not capped at 2 because an explicit trigger clause is present.	3 / 3
Trigger Term Quality	"Use for reverse engineering stripped Go and Rust binaries" uses natural trigger terms (reverse engineering, stripped, Go/Rust binaries) a user would actually say for this niche.	3 / 3
Distinctiveness Conflict Risk	The stripped Go/Rust binary RE niche is narrow with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 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/go-rust-reverse/SKILL.md
Commit: 6aa1362

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