anti-reversing-techniques
Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u...
72
Quality
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-anti-reversing-techniques/SKILL.mdQuality
Discovery
75%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 establishes a clear specialized niche in software protection analysis with an explicit 'Use when' clause. However, it appears truncated (ending with 'or u...') which limits the full evaluation. The technical terminology is appropriate for the domain but could benefit from more natural user-facing trigger terms.
Suggestions
Complete the truncated description to ensure all trigger scenarios are captured
Add more natural trigger terms users might say, such as 'packed executable', 'malware analysis', 'reverse engineering', 'unpacking', or 'deobfuscation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (anti-reversing, obfuscation, protection techniques) and mentions some actions (analyzing protected binaries, bypassing anti-debugging), but the description is truncated and doesn't provide a comprehensive list of concrete actions. | 2 / 3 |
Completeness | Clearly answers both what (understand anti-reversing, obfuscation, protection techniques) and when (Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis). Has explicit 'Use when...' clause with trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'anti-reversing', 'obfuscation', 'protection techniques', 'anti-debugging', and 'protected binaries', but these are fairly technical. Missing more natural variations users might say like 'packed executable', 'crackme', 'malware analysis', or 'reverse engineering protection'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche focusing on software protection and anti-reversing techniques. Unlikely to conflict with general coding or document skills due to the specialized security/reverse engineering domain. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at conciseness and appropriate content structuring with clear references to detailed resources. However, it critically lacks actionable content - the main body contains no concrete techniques, code examples, or specific commands, making it essentially a policy document that defers all substantive guidance to an external file. For a security analysis skill, the workflow also needs explicit validation checkpoints.
Suggestions
Add at least 2-3 concrete, executable examples of common anti-debugging detection or bypass techniques (e.g., specific debugger detection checks, timing-based detection patterns) directly in the skill body
Include specific tool commands or code snippets for identifying protection mechanisms (e.g., using objdump, radare2, or Python scripts)
Add explicit validation checkpoints to the workflow, such as 'Verify analysis environment is isolated before proceeding' or 'Confirm no network connectivity for malware samples'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose without padding or verbose descriptions of what anti-reversing or obfuscation means. | 3 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete code, commands, or specific examples. Instructions like 'Identify protection mechanisms' and 'choose safe analysis methods' describe rather than instruct, with all actual techniques deferred to an external file. | 1 / 3 |
Workflow Clarity | Steps are listed in a numbered sequence, but they lack validation checkpoints and specific details. For security-sensitive operations involving protected binaries, there are no explicit verification steps or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | The skill appropriately structures content as an overview with clear, one-level-deep references to the implementation playbook. Navigation is well-signaled with explicit file paths for detailed techniques. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
5c5ae21
- 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.