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

70%

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 ./skills/go-rust-reverse/SKILL.md

Quality

Content

61%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 terse, well-structured bilingual checklist skill that names the right tools and artifacts without over-explaining. Its main weakness is actionability and in-workflow validation: it gives checklist hints rather than executable commands or explicit verify-before-proceeding checkpoints.

Suggestions

Add concrete executable examples for the key tools (e.g., a sample GoReSym command with flags and expected output) to lift actionability.

Insert explicit validation checkpoints in the Go/Rust workflows (e.g., 'Confirm pclntab parsed before naming functions'; 'Verify recovered main.main before analyzing logic').

Separate the single in-bundle reference (references/go-rust-notes.md) from the out-of-skill routing paths in 参考 to clarify navigation.

Dimension	Reasoning	Score
Conciseness	Lean checklist/table form that assumes Claude's competence (no explanation of what Go/Rust or pclntab are), with only minor administrative scaffolding (ACTION REQUIRED, routing context, self-check) that could be trimmed.	4 / 5
Actionability	Names concrete tools (GoReSym, redress, radare2, rabin2) and target artifacts (go.buildid, pclntab, rust_begin_unwind, crypto/*), but stays at checklist-level direction without specific command syntax, flags, or executable steps.	3 / 5
Workflow Clarity	A clear NOW/NEXT/ACT sequence plus a closing self-check exist, but in-process validation checkpoints are only implicit (no 'verify X before proceeding' feedback loops).	3 / 5
Progressive Disclosure	Well-organized sections with one real one-level-deep bundle reference (references/go-rust-notes.md) that exists on disk; minor gap is that the 参考 section mixes that bundle file with several out-of-skill '../' routing paths, slightly muddying navigation.	4 / 5
	Total	14 / 20 Passed

Description

78%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 strong, concrete description that names its niche and several specific actions with an explicit 'Use for' trigger. Minor gaps in keyword synonyms and a small typo keep it just below the top anchor on specificity and completeness.

Suggestions

Add natural synonyms/extensions a user might say (e.g., 'Go malware', 'Rust .exe/.elf', 'golang') to broaden trigger-term coverage.

Split the 'when' into an explicit trigger clause (e.g., 'Use when reversing stripped Go or Rust binaries, Go malware, or Rust executables with missing symbols') for a cleaner completeness 5.

Fix the 'moduel' typo ('module data recovery') to avoid a credibility nit.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery' — against a clearly named domain, with only minor coverage gaps (and a 'moduel' typo).	4 / 5
Completeness	Both 'what' (RE actions) and 'when' ('Use for ... stripped Go and Rust binaries') are present and concrete, but the trigger is folded into the action listing rather than stated as a separate explicit trigger phrase, falling just short of the 5 anchor.	4 / 5
Trigger Term Quality	Contains natural user-facing terms ('reverse engineering', 'stripped', 'Go', 'Rust', 'panic strings') with good coverage, though it misses common synonyms and file extensions a user might say.	4 / 5
Distinctiveness Conflict Risk	'Stripped Go and Rust binaries' carves a clear niche with distinct triggers and minimal overlap risk against general RE skills.	5 / 5
	Total	17 / 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/go-rust-reverse/SKILL.md
Commit: 3ae5c59

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