ShulkwiSEC/bb-huge / skills/curated/amend-skill
amend-skill
VerifiedInspects a skill's SKILL.md and its observations/runs.md log, identifies failure patterns, and proposes a targeted amendment to improve the skill. Trigger on: "improve this skill", "fix this skill", "update this skill", "why does X keep failing", "this skill is wrong", "add this to the skill", or automatically when observations/<skill-name>/runs.md contains 3 or more failure entries. Outputs the amendment as a diff the user can review before applying. Records the amendment rationale in observations/<skill-name>/runs.md after user confirmation.
Amend Skill
Purpose
Skills degrade over time as targets change, new bypass techniques emerge, and failure patterns accumulate. This skill closes the feedback loop: it reads execution history, identifies what is systematically failing, and proposes a minimal surgical amendment to the skill.
Trigger Conditions
Activate this skill when:
- User says "improve this skill", "fix this skill", "update this skill", "amend this skill"
- User says "why does X keep failing" where X is a skill name
- User says "add this to the skill" after describing a new technique that worked
observations/<skill-name>/runs.mdcontains 3 or more entries withoutcome: fail
Methodology
- Identify the target skill — confirm the skill name with the user if ambiguous.
- Read the skill — load
skills/<bucket>/<category>/<skill-name>/SKILL.mdin full. - Read the observations — load
observations/<skill-name>/runs.md. - Analyze failure patterns:
- Which steps consistently fail?
- Which payloads are blocked or produce wrong output?
- Which trigger conditions are missing or too broad?
- Are there new bypass techniques that worked but aren't documented?
- Is the output format causing downstream confusion?
- Formulate a single targeted amendment — one focused change rather than a full rewrite. The amendment should be one of:
- Tighten trigger: remove or refine a trigger condition that causes false activation
- Add missing condition: add a step, payload, or bypass that is now needed
- Reorder steps: move a high-value step earlier to avoid wasted time
- Fix payload: update an outdated payload that no longer works
- Change output format: restructure how the skill presents findings
- Output the amendment as a unified diff — show old text and proposed new text side by side.
- Ask for confirmation — do not apply until the user approves.
- Apply and record — edit the SKILL.md, then append to
observations/<skill-name>/runs.md:
---
date: YYYY-MM-DD
skill: <skill-name>
task: Amendment applied via amend-skill
outcome: amendment
what_worked: |
<describe what the amendment changes and why>
what_failed: |
<describe the failure pattern that motivated the amendment>
errors: |
N/A
notes: |
Amendment type: <tighten-trigger | add-condition | reorder-steps | fix-payload | change-output>
Rationale: <one-sentence reason>
---
Example Interaction
User: "why does sql-injection keep failing on this target?"
Process:
- Read
skills/owasp-wstg/injection/sql-injection/SKILL.md - Read
observations/sql-injection/runs.md— finds 3 fail entries, all noting WAF blocking'and-- - Analysis: Bypass section exists but WAF-specific encoding variants not prominent enough in step 2
- Amendment: Move WAF bypass step earlier in Methodology, add a WAF detection pre-step
Output:
-2. Submit `'`, `"`, `;`, `--`, `/* */` individually and observe response differences.
-3. Confirm with boolean pair: append `AND 1=1--` (true) vs `AND 1=2--` (false).
+2. Check for WAF: submit `'` and observe whether the response is a WAF block page (uniform
+ error regardless of input) vs. a database error (input-specific). If WAF present, use
+ encoding variants from the Bypass Techniques section before confirming injection.
+3. Submit `'`, `"`, `;`, `--`, `/* */` individually. If WAF present, substitute with
+ `%27`, `%2D%2D`, and comment fragmentation `UN/**/ION`.
+4. Confirm with boolean pair: `AND 1=1--` vs `AND 1=2--`.
Fix Patterns
This is a meta-skill — it has no fix patterns of its own. Its output is an amendment to another skill's fix patterns.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |