Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hypnguyen1209/writing-offensive-skills
Use when creating or editing a skill in this offensive-claude repo — for the SKILL.md conventions (trigger descriptions, technique map, runnable scripts, OPSEC/detection, red-flags tables, flowchart rules)
Passed 19 of 19 test cases with the skill, and 6 of 19 without it.
and 35 more in the full report
15 fixed7 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our team authored a custom credential harvesting skill, but the frontmatter description currently summarizes the step-by-step workflow instead of acting as a dispatcher trigger. Could you refactor this skill file so the description follows proper agent invocation rules, the file layout aligns with our standard directory organization, and cross-references follow proper notation?
| Checked | Without skill | With skill |
|---|---|---|
| Replaces step-by-step description with trigger conditions starting with 'Use when' | Missed | Passed |
| Uses bold required syntax like **REQUIRED:** scope-discipline instead of @ links for cross-references | Missed | Passed |
| Specifies a progressive directory structure using SKILL.md alongside references and scripts subdirectories | Missed | Passed |
The instructions your model reads when the skill loads.
Conventions for authoring skills in this repo so the dispatcher can find them and operators can trust them. This adapts superpowers' skill conventions to offensive security.
REQUIRED BACKGROUND: superpowers:writing-skills (the general conventions) and superpowers:test-driven-development (skills are tested like code — baseline failure first).
The description: field decides whether the dispatcher loads the skill. Write Use when…
triggering conditions and symptoms ONLY — never summarize the skill's workflow (a workflow summary
makes Claude follow the description instead of reading the skill).
# BAD (summarizes workflow): description: Recon skill that enumerates subdomains then scans ports
# GOOD (triggers only): description: Use when mapping a target's external attack surface — subdomains, hosts, exposed services
Third person, technology-specific only if the skill is. Verb-first / gerund names.
skills/<name>/
SKILL.md # thin router, <=180 lines
references/ # per-technique deep-dives (theory + 2024-2026 + code + detection + OPSEC)
scripts/ # runnable tooling (no placeholders)
Domain (technique) skill SKILL.md sections, in order: frontmatter → When to Activate →
Technique Map (Technique | ATT&CK Txxxx | CWE | reference | script) → Quick Start →
OPSEC & Detection table → Deep Dives (links into references/).
Discipline skill (a hard rule, e.g. finding/scope/opsec-discipline): Overview with the Iron Law → the rule → Red Flags (STOP signals) → Rationalizations table (excuse | reality). State "violating the letter is violating the spirit" and close loopholes explicitly.
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.