CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

anti-debug-bypass

Detect and neutralize anti-debug / anti-VM checks — IsDebuggerPresent, ptrace, NtGlobalFlag, timing, hardware-breakpoint detection.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/reverser/anti-debug-bypass/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, highly actionable playbook: copy-paste ready code and commands for every major platform path, dense lookup tables, and a clear numbered workflow with a post-patch validation step. The only notable weaknesses are minor trimming opportunities and the absence of a feedback loop for verifying dynamic bypasses.

DimensionReasoningScore

Conciseness

The body is dense and command-driven with almost no concept explanation (no 'what a debugger is' filler), and every table row carries a technique or command. Not a 5 because the intro paragraph ("Each check has a known counter.") and the "Known exemplars" section restate malware-family behaviors Claude largely already knows and could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste ready material covers the common cases: a complete LD_PRELOAD bypass.c with gcc build and run commands, gdb catch-syscall sequences, r2 patching commands ("wx 31c0c3 @ <addr>"), and strings/yara scan commands. Not below 5: the few terse bypass cells ("Patch return to FALSE") are pointers for inherently tool-specific actions, not missing detail for the main paths.

5 / 5

Workflow Clarity

A clear numbered sequence (enumerate → check/bypass tables → dynamic debugger routes → static patching → promote/promote-to-KG) with an explicit validation checkpoint for the destructive step ("Run static-validation YARA post-patch to ensure binary still loads" plus the self-checksum caution). Not a 5 because the dynamic-analysis path lacks feedback loops (e.g., verifying the bypass held before proceeding).

4 / 5

Progressive Disclosure

The file is well-organized with clearly headed sections, and no bundle files exist so nothing is mis-nested. Not a 5 because it exceeds the under-50-line single-file exception and inlines content that could be split ("Known exemplars", "Tool cheat sheet", and the per-technique tables) into one-level-deep reference files, which would keep the SKILL.md a leaner overview.

4 / 5

Total

17

/

20

Passed

Description

70%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 crisp, third-person description with strong specificity and highly distinct trigger terms for the anti-debug bypass niche. Its main weakness is the missing 'Use when...' clause, which both caps completeness and leaves natural trigger synonyms like "bypass" and "sandbox detection" unused.

Suggestions

Append an explicit trigger clause, e.g. "Use when a sample exits or misbehaves under a debugger, ptrace/TRACEME fails, TracerPid is checked, or anti-VM/sandbox checks block dynamic analysis."

Add natural synonyms users would say, such as "bypass", "debugger detection", "anti-analysis", and "sandbox evasion", to broaden trigger coverage.

Consider mentioning the outcome-oriented actions (patching checks, hooking via LD_PRELOAD/frida) so the what-side coverage matches the body's scope.

DimensionReasoningScore

Specificity

"Detect and neutralize" gives two concrete verbs and the enumeration "IsDebuggerPresent, ptrace, NtGlobalFlag, timing, hardware-breakpoint detection" names specific APIs/checks rather than vague language. It sits between anchor 3 (1-2 actions, not comprehensive) and anchor 4 (several specific actions, minor gaps): the API-level enumeration puts it noticeably above a bare 'Processes PDF files' style description, but coverage of the what is limited to detection/neutralization.

4 / 5

Completeness

The "what" is clear ("Detect and neutralize anti-debug / anti-VM checks" with named techniques), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines. Not a 2 because the what is specific and well-formed, not vague.

3 / 5

Trigger Term Quality

Terms like "anti-debug", "ptrace", "IsDebuggerPresent", and "hardware-breakpoint detection" are natural phrases a malware analyst would actually say. Not a 5 because common variations such as "bypass", "debugger detection", "anti-analysis", and "sandbox evasion/detection" are absent.

4 / 5

Distinctiveness Conflict Risk

"anti-debug / anti-VM checks — IsDebuggerPresent, ptrace, NtGlobalFlag" carves out a clear niche with distinct named-API triggers that no neighboring skill would claim. Minimal conflict risk with generic reverse-engineering or analysis skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/reverser/anti-debug-bypass/SKILL.md

Reviewed

Table of Contents

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.