anti-reversing-techniques

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

Quality

17%

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

35%

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-structured around safety gates and process, but it provides almost no concrete, actionable technique guidance and defers to a playbook file that is missing from the bundle. Conciseness is hampered by a duplicated authorization block.

Suggestions

Add concrete, executable guidance inline (specific tools, commands, or named techniques such as debugger detection checks, dump-resistance patterns) or ship the referenced resources/implementation-playbook.md so the deferral is not empty.

Merge the two overlapping AUTHORIZED USE ONLY blocks into a single concise authorization preamble to remove redundant tokens.

Add a validation/checkpoint step to the analysis workflow (e.g., confirm scope before each active probe, verify findings against a benign baseline) to support feedback loops for risky operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean safety and process guidance without explaining concepts Claude knows, but the authorization preamble is duplicated (two overlapping AUTHORIZED USE ONLY blocks) which is unnecessary token cost that could be tightened.	2 / 3
Actionability	Instructions are abstract ("Identify protection mechanisms and choose safe analysis methods", "Provide defensive recommendations") with no concrete commands, code, or specific techniques, and the referenced playbook does not exist, so it describes rather than instructs.	1 / 3
Workflow Clarity	The confirmation gate is well sequenced with an explicit wait-for-confirmation checkpoint, but the core analysis workflow lacks validation checkpoints; for probing/exploiting targets (risky operations) the missing feedback loop caps the score at 2.	2 / 3
Progressive Disclosure	The body is organized into clear sections and points one level deep to resources/implementation-playbook.md, but that file does not exist, making the reference a dangling pointer rather than usable navigation.	2 / 3
	Total	7 / 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, leaking blockquote markdown into the YAML string and conveying only abstract policy language with no concrete capability or trigger guidance. It fails specificity, trigger terms, completeness, and distinctiveness.

Suggestions

Rewrite the description as a complete third-person sentence stating concrete actions, e.g. "Identifies and analyzes anti-debugging, anti-dumping, and obfuscation techniques in protected binaries for malware analysis and authorized reverse engineering."

Add an explicit trigger clause such as "Use when analyzing protected or packed binaries, malware with anti-analysis tricks, or obfuscated code within an authorized scope."

Remove the policy/authorization text from the description field (keep it in the body) and ensure the YAML string is not truncated and contains no stray markdown.

Dimension	Reasoning	Score
Specificity	The description names no concrete actions, only abstract phrases like "dual-use security techniques" and "bypass or analysis", matching the vague-actions anchor rather than the domain+actions level.	1 / 3
Completeness	It answers neither "what" (no concrete capability) nor "when" (no "Use when..." clause), and the text is a truncated fragment leaking markdown ("> 1.") into the YAML, so it fails both required parts.	1 / 3
Trigger Term Quality	No natural keywords a user would say appear; terms like "AUTHORIZED USE ONLY", "bypass or analysis" are jargon/policy text rather than user-trigger language such as anti-debugging, obfuscation, or malware.	1 / 3
Distinctiveness Conflict Risk	"Security techniques" and "bypass or analysis" are extremely generic and would overlap with many other security skills, matching the high-conflict anchor.	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
Path: skills/anti-reversing-techniques/SKILL.md
Commit: b7f833d

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