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?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

27%

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

The body is well-intentioned and safety-conscious but offers no concrete, executable guidance, and its only detailed reference points to a file that does not exist. It functions as a cautionary overview rather than an actionable skill.

Suggestions

Provide concrete, executable guidance — specific tools, commands, or named techniques (e.g., detecting IsDebuggerPresent, handling packers) — rather than abstract directives like 'choose safe analysis methods'.

Either create the referenced 'resources/implementation-playbook.md' with real detailed techniques or remove the broken reference; a dead link undermines navigation.

Add validation checkpoints to the workflow (e.g., confirm authorization in writing before step 2, verify analysis environment isolation) so the sequence has explicit feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is fairly lean and does not explain concepts Claude already knows, but the authorization/scope message is repeated across the preamble, 'Use this skill when', 'Instructions', and 'Safety', and the implementation-playbook reference appears twice, so it could be tightened.	2 / 3
Actionability	Steps are abstract ('Identify protection mechanisms and choose safe analysis methods', 'avoid modifying artifacts unnecessarily') with no concrete commands, code, or specific techniques; the one actionable pointer references a resources file that does not exist.	1 / 3
Workflow Clarity	A numbered sequence is present in 'Instructions', but it lacks validation checkpoints and feedback loops; the sole referenced playbook path is dead, leaving the actual workflow underspecified.	2 / 3
Progressive Disclosure	The body points to 'resources/implementation-playbook.md' and lists it under Resources, but no such file or resources/ directory exists in the bundle, so the disclosed reference is broken and navigation fails.	1 / 3
	Total	6 / 12 Passed

Description

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 frontmatter description is malformed and truncated mid-sentence, containing no concrete actions, natural trigger terms, or explicit 'Use when' guidance. It reads as a corrupted legal preamble rather than a capability statement.

Suggestions

Rewrite the description to first state concrete actions in third person (e.g., 'Analyzes protected binaries to identify anti-debugging and obfuscation techniques') instead of a truncated legal preamble.

Add an explicit 'Use when...' clause with natural trigger terms users would say, such as 'authorized malware analysis', 'reverse engineering a binary I own', or 'CTF anti-debugging challenge'.

Move authorization/legal caveats into the body or a Safety section so the description can focus on capabilities and trigger conditions.

Dimension	Reasoning	Score
Specificity	The description names no concrete actions at all, ending mid-sentence at 'Before proceeding with any bypass or analysis: > 1.'; it is truncated and abstract, matching the 'vague or no actions' anchor.	1 / 3
Completeness	Both 'what does this do' and 'when to use it' are missing or unparseable because the description is cut off at '> 1.', so it fails to answer either question explicitly.	1 / 3
Trigger Term Quality	There are no natural user keywords; the only phrasing is jargon-ish ('dual-use security techniques'), and a user needing malware analysis would not naturally utter this broken text.	1 / 3
Distinctiveness Conflict Risk	With no specific capabilities or triggers, the language is too generic to distinguish it from other security skills and would trigger for the wrong skill.	1 / 3
	Total	4 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Commit: 9fc5f98

Reviewed: about 3 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.