anti-reversing-techniques

AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: > 1.

Quality

11%

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

The canonical home for this skill is anti-reversing-techniques in rmyndharis/antigravity-skills

Quality

Content

22%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is almost entirely a policy/authorization wrapper with no actionable technical content. The actual instructions are vague platitudes that defer everything to an external playbook, meaning the SKILL.md body provides virtually no executable guidance. While the authorization framing is appropriate for security-sensitive content, the skill fails to provide even a minimal quick-start or concrete example of what techniques or tools are involved.

Suggestions

Add concrete, actionable content to the Instructions section: specify actual tools (e.g., Ghidra, x64dbg, strace), common protection types (packers, anti-debug checks, obfuscation), and at least one worked example or command sequence.

Include a quick-start workflow with specific steps, e.g., 'Run `file binary` to identify type → Use `strings` for initial recon → Load in Ghidra for static analysis → Check for common anti-debug patterns (IsDebuggerPresent, ptrace checks)'.

Add validation checkpoints to the workflow, such as verifying the binary type before choosing analysis tools, or confirming that a sandbox environment is properly isolated before executing samples.

Provide at least a summary of what's in `resources/implementation-playbook.md` so the SKILL.md overview is useful on its own for simple cases.

Dimension	Reasoning	Score
Conciseness	The authorization disclaimer is lengthy and repeated (once in the blockquote, again in 'Do not use this skill when'). The 'Use this skill when' and 'Do not use this skill when' sections overlap with the disclaimer. However, given the security-sensitive nature, some redundancy is justified.	2 / 3
Actionability	The instructions are entirely abstract and vague: 'Identify protection mechanisms and choose safe analysis methods' provides no concrete techniques, commands, tools, or examples. There is no executable guidance whatsoever—everything is deferred to an external playbook.	1 / 3
Workflow Clarity	The four numbered steps are high-level platitudes ('Confirm authorization', 'Identify protection mechanisms', 'Document findings') with no specifics, no validation checkpoints, and no feedback loops. For a skill involving potentially destructive or sensitive operations, this is insufficient.	1 / 3
Progressive Disclosure	There is a reference to `resources/implementation-playbook.md` which is one level deep and clearly signaled, which is good. However, the SKILL.md itself contains almost no substantive content—it's essentially an empty shell pointing elsewhere, with the overview providing no useful quick-start information.	2 / 3
	Total	6 / 12 Passed

Description

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

This description is essentially a legal/authorization disclaimer rather than a functional skill description. It provides no information about what the skill does, what actions it performs, or when Claude should select it. It is entirely unsuitable for skill selection among a set of available skills.

Suggestions

Replace the disclaimer text with a concrete description of what the skill does, e.g., 'Performs penetration testing analysis on web applications, identifies common vulnerabilities such as XSS and SQL injection.'

Add an explicit 'Use when...' clause with natural trigger terms that users would say, e.g., 'Use when the user asks about security testing, vulnerability scanning, or penetration testing.'

Move the authorization disclaimer to the skill body rather than the description field, which should be reserved for capability and trigger information.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions whatsoever. It mentions 'bypass or analysis' in passing but does not describe what the skill actually does. The text is a disclaimer/warning rather than a capability description.	1 / 3
Completeness	The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no 'Use when...' clause, no explanation of capabilities, and the text is entirely a procedural disclaimer rather than a functional description.	1 / 3
Trigger Term Quality	There are no natural user-facing keywords. Terms like 'dual-use security techniques' and 'bypass or analysis' are vague jargon that users would not naturally use to invoke a skill. No actionable trigger terms are present.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it could apply to virtually any security-related skill. 'Security techniques,' 'bypass,' and 'analysis' are extremely broad and would conflict with many other security-oriented skills.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/anti-reversing-techniques/SKILL.md
Commit: 7520423

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