anti-reversing-techniques

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

Quality

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 ./plugins/antigravity-awesome-skills/skills/anti-reversing-techniques/SKILL.md

Quality

Content

14%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 essentially a policy/authorization wrapper with no substantive technical content. All concrete guidance is deferred to a referenced playbook file that does not exist in the bundle, leaving the skill with no actionable instructions, no executable examples, and no meaningful workflow. The authorization and safety framing, while important for this domain, is repetitive and constitutes the bulk of the content.

Suggestions

Include at least a summary of key techniques and concrete tool commands (e.g., specific debugger commands, common anti-debugging patterns) directly in the SKILL.md rather than deferring everything to a missing file.

Add a concrete workflow with specific steps, tools, and validation checkpoints (e.g., 'Run `file <binary>` to identify format → Check for packing with `detect-it-easy` → If packed, unpack with...').

Either provide the referenced `resources/implementation-playbook.md` as a bundle file, or inline its essential content so the skill is self-contained.

Consolidate the repeated authorization language into a single concise block to reduce redundancy and free up space for actionable content.

Dimension	Reasoning	Score
Conciseness	The authorization preamble and safety disclaimers are somewhat verbose and repetitive (e.g., 'authorized' appears many times). The 'Use this skill when' and 'Do not use this skill when' sections overlap with the authorization block. However, for a security-sensitive skill, some of this repetition 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, code, or tool references. There is nothing executable or copy-paste ready. All substantive content is deferred to a referenced file that doesn't exist in the bundle.	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, no error recovery, and no concrete sequencing of actual analysis tasks.	1 / 3
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for all substantive content, but no bundle files are provided, meaning the reference leads nowhere. The SKILL.md itself contains no actionable content, making it an empty shell that depends entirely on a missing file.	1 / 3
	Total	5 / 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 truncated authorization disclaimer rather than a functional skill description. It provides no information about what the skill does, when it should be used, or what triggers should activate it. It fails on every dimension of the rubric.

Suggestions

Replace the authorization disclaimer with a concrete description of what the skill does, e.g., 'Performs security vulnerability analysis on web applications, identifies common exploits such as XSS and SQL injection.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about penetration testing, vulnerability scanning, security audits, or exploit analysis.'

Move any authorization or safety disclaimers into 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 or capabilities. 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 functional 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 explicit triggers, and the text appears to be a truncated authorization warning rather than a skill 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 and not terms a user would naturally use to invoke a skill. No file types, tools, or specific domains are mentioned.	1 / 3
Distinctiveness Conflict Risk	The description is extremely generic and could apply to any security-related skill. 'Security techniques,' 'bypass,' and 'analysis' are broad terms that 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: popey/claude-code-skills
Path: plugins/antigravity-awesome-skills/skills/anti-reversing-techniques/SKILL.md
Commit: a5a6601

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