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 understanding software protection mechanisms.

Quality

64%

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/anti-reversing-techniques/SKILL.md

Quality

Content

50%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 skill body is brief and well-intentioned with clear authorized-use framing and section structure, but it offers little actionable guidance and points to a resources/implementation-playbook.md file that is absent from the bundle. Strengthening concrete instructions and either providing or removing the dangling reference would materially improve it.

Suggestions

Add concrete, executable guidance — e.g., specific tool invocations or commands for identifying common anti-debug/obfuscation mechanisms — rather than generic steps like 'Identify protection mechanisms'.

Add an explicit validation checkpoint in the workflow (e.g., 'Confirm authorization in writing before proceeding to step 2') to satisfy the destructive/batch-operation feedback-loop requirement.

Resolve the dangling reference: create resources/implementation-playbook.md or remove the pointer so progressive disclosure points to a real file.

Dimension	Reasoning	Score
Conciseness	The body is short and largely free of padding, assuming Claude's competence; the main inefficiency is the duplicated reference to the playbook appearing both inline and in the Resources section.	4 / 5
Actionability	Guidance is high-level ('Identify protection mechanisms and choose safe analysis methods', 'Document findings') with no concrete commands, tool invocations, or executable steps — only vague direction.	2 / 5
Workflow Clarity	A 4-step sequence is listed but it lacks concrete validation checkpoints; for analysis involving destructive/batch-adjacent operations the cap guidance applies, keeping this at 3.	3 / 5
Progressive Disclosure	Sections are organized and a one-level reference to resources/implementation-playbook.md is signaled, but the referenced file does not exist in the bundle, so navigation is incomplete and the structure cannot be verified.	3 / 5
	Total	12 / 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 solid description that clearly answers both what the skill covers and when to use it, with natural trigger phrases for an authorized-security-analysis context. It is slightly generic in its action verbs and could add concrete artifacts (e.g., 'packed executables', '.bin files') to improve specificity and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (anti-reversing, obfuscation, protection) and a couple of concrete activities ('analyzing protected binaries', 'bypassing anti-debugging'), but the actions are generic verbs rather than a comprehensive, specific action list.	3 / 5
Completeness	Explicitly states both what the skill does ('Understand anti-reversing, obfuscation, and protection techniques...') and when to use it with concrete trigger phrases ('Use when analyzing protected binaries, bypassing anti-debugging...').	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('protected binaries', 'bypassing anti-debugging', 'software protection mechanisms') that a user might say, though it lacks file extensions and a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (anti-reversing/protection analysis) with distinct triggers and minimal overlap risk, though 'understanding software protection mechanisms' is broad enough to brush against adjacent security skills.	4 / 5
	Total	16 / 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: rmyndharis/antigravity-skills
Path: skills/anti-reversing-techniques/SKILL.md
Commit: 3eff4af

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