[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CH7D5M3WWZPQTWP2WDQ0FT":3,"skill-same:01M7CH7D5M3WWZPQTWP2WDQ0FT":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7CH7D5M3WWZPQTWP2WDQ0FT","skill-improver",null,"Runs an autonomous review-and-fix improvement loop over a Claude Code skill until a review comes back clean, with a cross-round findings ledger, escalation when fixes stop converging, and a mechanical scope guard. Reviews are performed by the plugin-dev skill-reviewer agent. Use to fix skill quality issues, iteratively refine a skill, or resume a loop after an escalation ('fix my skill', 'improve this skill until it passes review', 'skill improvement loop'). NOT for a one-time review — use the plugin-dev skill-reviewer agent directly.","bongkage\u002Ftrailofbits-skills","bongkage","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F101378796?v=4","01M7CH419QTJ16DNJ33P0WCWBE","01M7CH41A9NWK8D2JBRK9F0M2C",1,"CC-BY-SA-4.0","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-improver\u002Fskills\u002Fskill-improver\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-improver\ndescription: \"Runs an autonomous review-and-fix improvement loop over a Claude Code skill until a review comes back clean, with a cross-round findings ledger, escalation when fixes stop converging, and a mechanical scope guard. Reviews are performed by the plugin-dev skill-reviewer agent. Use to fix skill quality issues, iteratively refine a skill, or resume a loop after an escalation ('fix my skill', 'improve this skill until it passes review', 'skill improvement loop'). NOT for a one-time review — use the plugin-dev skill-reviewer agent directly.\"\nargument-hint: \"\u003CSKILL_NAME_OR_PATH> [--max-rounds N]\"\nallowed-tools: Bash Glob Read TaskOutput TaskStop Workflow\n---\n\n# Skill Improver\n\nImprove a Claude Code skill by running `\u002Fcode-improver:improve` — a dynamic workflow\nthat loops a reviewer and a fixer subagent until a review reports zero critical\u002Fmajor\nfindings, then strips its own residue. This entry point wires the loop to the\n`plugin-dev:skill-reviewer` agent, so the **plugin-dev plugin must be installed**\n(marketplace `claude-plugins-official`). The loop, its ledger, and its guards live in\nthe workflow; this skill resolves the target and relays the outcome.\n\n## Starting the loop\n\nThe user provided: `$ARGUMENTS` (if empty, take the target skill from the conversation).\n\n### 1. Resolve the skill path\n\n1. If the input ends with `\u002FSKILL.md` and the file exists, use its directory\n2. If the input is a directory containing `SKILL.md`, use that path\n3. Otherwise `Glob(pattern=\"**\u002FSKILL.md\")` and filter by skill name or path substring:\n   - **Multiple matches:** ask the user to choose\n   - **No matches:** report the available skills\n   - **Single match:** proceed\n\n### 2. Resolve the loop script\n\nThe loop is the dynamic workflow `workflows\u002Fimprove.js` in this plugin. Launch it by\npath: `scriptPath` takes a resolved absolute path, and the Workflow tool's `name` resolves\nbuilt-in and project workflows, so a marketplace-installed one may not answer to\n`code-improver:improve`. Try in order, first hit wins — the home directories come before\n`.` so an installed copy beats a checkout of this marketplace:\n\n1. `Bash: ls -d -- \"${CLAUDE_PLUGIN_ROOT}\u002Fworkflows\u002Fimprove.js\"`\n2. `Bash: ls -d -- \"${CODEX_PLUGIN_ROOT}\u002Fworkflows\u002Fimprove.js\"` (if that variable is set instead)\n3. `Bash: find ~\u002F.claude ~\u002F.codex . -maxdepth 7 -path '*\u002Fcode-improver\u002Fworkflows\u002Fimprove.js' -print -quit 2>\u002Fdev\u002Fnull`\n\nUse the path exactly as printed. Its plugin directory — the path with\n`\u002Fworkflows\u002Fimprove.js` removed — is `pluginRoot`. If all three come back empty, try\n`{name: \"code-improver:improve\"}` once; if that is unavailable too, stop and say the loop\ncould not be located. Do not assemble a path by hand and do not improvise the loop.\n\n### 3. Invoke the workflow\n\nRun it with the Workflow tool, `{scriptPath: \"\u003Cthe path from step 2>\", args: {...}}`:\n\n```json\n{\n  \"target\": \"\u003Cresolved absolute path>\",\n  \"reviewer\": {\n    \"kind\": \"agent\",\n    \"name\": \"plugin-dev:skill-reviewer\",\n    \"notes\": \"The target is a Claude Code skill directory; review it as a skill (frontmatter, triggering description, progressive disclosure, referenced files).\"\n  },\n  \"pluginRoot\": \"\u003Cthe plugin directory from step 2>\",\n  \"maxRounds\": 5\n}\n```\n\n- `maxRounds` only if the user asked for a different cap (`--max-rounds N`).\n- `pluginRoot` lets the run find its metrics collector; omit the key only if step 2 fell\n  through to the workflow name — the workflow then searches for itself.\n- `scope` (repo-relative globs) only if the user restricted or widened what the loop may\n  touch; by default the workflow scopes to the skill's plugin directory.\n- `decision` only on continuation (below).\n\nThe workflow runs in the background and needs no babysitting: it reviews, fixes,\nre-reviews, checks scope after every fix round, and can only complete on a clean review.\nIt never commits; all changes stay in the working tree.\n\n**If the Workflow tool is unavailable or denied, stop and say so.** Do not improvise the\nloop inline with direct edits — the ledger, scope guard, and escalation guarantees live\nin the workflow, and an inline imitation has none of them (observed failure: an inline\nfallback \"fixed\" a finding by weakening the documented guarantee, exactly what the loop\nexists to prevent).\n\n**If the result is `halted: \"reviewer-unavailable\"`, relay it and stop.** The reviewer\nthis skill names is not installed; tell the user to install the `plugin-dev` plugin from\nthe `claude-plugins-official` marketplace and re-run. Do not review the skill yourself.\n\n**Do not end your turn while the loop is running.** The Workflow tool returns a task id\nimmediately; the result comes later. In an interactive session the completion\nnotification re-invokes you — wait for it. In a non-interactive run (scripted, CI, eval)\nthere is no later turn: stopping abandons the loop mid-round, so after launching, poll\nthe task (TaskOutput with the returned task id, or sleep-and-recheck) until it completes,\nthen relay the result. A session that answers \"the loop is running, I'll report later\"\nhas lost the run.\n\n## Relaying the result\n\nThe workflow returns a structured result. Report it honestly — the distinctions matter:\n\n- **`converged: true`** — the last action was a review with zero critical\u002Fmajor findings.\n  Report rounds used, remaining minor findings (`open_minor_count`), and the artifact\n  paths (`ledger_path`, `metrics`).\n- **`capped: true`** — the fix budget ran out and the FINAL review still found blocking\n  issues. Say plainly: **capped, NOT converged**, and list `open_blocking`. Do not\n  present this as success.\n- **`escalation`** — the loop detected it was not converging (recurring findings,\n  non-decreasing counts, or a fix relocating a problem). Relay the escalation message and\n  finding ids to the user: this needs a design decision, not more rounds.\n- **`halted`** — a guard fired (scope violation, unregistered new files, a dead or\n  unavailable reviewer, or a finalize pass whose own edits failed the check that follows\n  it). Relay the paths in `violations`\u002F`new_untracked_files`, the sites in\n  `finalize_regressions`, and the notes.\n- **`notes`** always travel with the result — surface them; they include loud warnings\n  such as \"a git repository was initialized\".\n\n## Continuing after an escalation\n\nThe loop stops on escalation by design. When the user decides (e.g. \"keep the blocklist\nand document the limitation\"), start a fresh run with the same `target` plus:\n\n```json\n{ \"decision\": \"\u003Cthe user's ruling, verbatim>\" }\n```\n\nThe new run reloads the on-disk ledger, so every finding, rejection, and verdict carries\nover — rounds restart, re-derivation does not.\n\nTo stop a running loop, stop the workflow task (TaskStop); the ledger on disk is current\nto the last round and a re-run resumes from it.\n\n## What the loop enforces (so you do not have to)\n\n- **Fix verification** — the next review verifies every fix; fixes to executable\n  behavior carry pins that fail against the pre-fix code.\n- **Scope** — a mechanical git-diff check after every fix round, and after the finalize\n  pass, halts on any out-of-scope change; out-of-scope files git does not track are\n  guarded by content hash, since no diff would show them; completion also requires no\n  unregistered new files in scope.\n- **Report everything** — reviewers report all findings with severity; filtering happens\n  once, at the ledger verdict, and rejections are not re-litigated without new evidence.\n- **Finalize** — before completion the loop strips narration comments, collapses version\n  churn to exactly one bump (in `plugin.json` and the marketplace entry that repeats it),\n  and runs a docs-match-code pass. Those edits land after the last review, so a check\n  reads them: an over-eager narration strip or a false docs claim halts with\n  `finalize-regression` instead of passing as done.\n\n## When NOT to use\n\n- **One-time review**: dispatch the `plugin-dev:skill-reviewer` agent directly\n- **Quick single fixes**: edit the file directly\n- **Non-skill targets**: use the `code-improver` skill with a reviewer that fits the\n  target, or `pr-improver` for a branch\n- **Exploratory drafting**: manual iteration gives more control while the shape is fluid\n","# Skill Improver\n\nImprove a Claude Code skill by running `\u002Fcode-improver:improve` — a dynamic workflow\nthat loops a reviewer and a fixer subagent until a review reports zero critical\u002Fmajor\nfindings, then strips its own residue. This entry point wires the loop to the\n`plugin-dev:skill-reviewer` agent, so the **plugin-dev plugin must be installed**\n(marketplace `claude-plugins-official`). The loop, its ledger, and its guards live in\nthe workflow; this skill resolves the target and relays the outcome.\n\n## Starting the loop\n\nThe user provided: `$ARGUMENTS` (if empty, take the target skill from the conversation).\n\n### 1. Resolve the skill path\n\n1. If the input ends with `\u002FSKILL.md` and the file exists, use its directory\n2. If the input is a directory containing `SKILL.md`, use that path\n3. Otherwise `Glob(pattern=\"**\u002FSKILL.md\")` and filter by skill name or path substring:\n   - **Multiple matches:** ask the user to choose\n   - **No matches:** report the available skills\n   - **Single match:** proceed\n\n### 2. Resolve the loop script\n\nThe loop is the dynamic workflow `workflows\u002Fimprove.js` in this plugin. Launch it by\npath: `scriptPath` takes a resolved absolute path, and the Workflow tool's `name` resolves\nbuilt-in and project workflows, so a marketplace-installed one may not answer to\n`code-improver:improve`. Try in order, first hit wins — the home directories come before\n`.` so an installed copy beats a checkout of this marketplace:\n\n1. `Bash: ls -d -- \"${CLAUDE_PLUGIN_ROOT}\u002Fworkflows\u002Fimprove.js\"`\n2. `Bash: ls -d -- \"${CODEX_PLUGIN_ROOT}\u002Fworkflows\u002Fimprove.js\"` (if that variable is set instead)\n3. `Bash: find ~\u002F.claude ~\u002F.codex . -maxdepth 7 -path '*\u002Fcode-improver\u002Fworkflows\u002Fimprove.js' -print -quit 2>\u002Fdev\u002Fnull`\n\nUse the path exactly as printed. Its plugin directory — the path with\n`\u002Fworkflows\u002Fimprove.js` removed — is `pluginRoot`. If all three come back empty, try\n`{name: \"code-improver:improve\"}` once; if that is unavailable too, stop and say the loop\ncould not be located. Do not assemble a path by hand and do not improvise the loop.\n\n### 3. Invoke the workflow\n\nRun it with the Workflow tool, `{scriptPath: \"\u003Cthe path from step 2>\", args: {...}}`:\n\n```json\n{\n  \"target\": \"\u003Cresolved absolute path>\",\n  \"reviewer\": {\n    \"kind\": \"agent\",\n    \"name\": \"plugin-dev:skill-reviewer\",\n    \"notes\": \"The target is a Claude Code skill directory; review it as a skill (frontmatter, triggering description, progressive disclosure, referenced files).\"\n  },\n  \"pluginRoot\": \"\u003Cthe plugin directory from step 2>\",\n  \"maxRounds\": 5\n}\n```\n\n- `maxRounds` only if the user asked for a different cap (`--max-rounds N`).\n- `pluginRoot` lets the run find its metrics collector; omit the key only if step 2 fell\n  through to the workflow name — the workflow then searches for itself.\n- `scope` (repo-relative globs) only if the user restricted or widened what the loop may\n  touch; by default the workflow scopes to the skill's plugin directory.\n- `decision` only on continuation (below).\n\nThe workflow runs in the background and needs no babysitting: it reviews, fixes,\nre-reviews, checks scope after every fix round, and can only complete on a clean review.\nIt never commits; all changes stay in the working tree.\n\n**If the Workflow tool is unavailable or denied, stop and say so.** Do not improvise the\nloop inline with direct edits — the ledger, scope guard, and escalation guarantees live\nin the workflow, and an inline imitation has none of them (observed failure: an inline\nfallback \"fixed\" a finding by weakening the documented guarantee, exactly what the loop\nexists to prevent).\n\n**If the result is `halted: \"reviewer-unavailable\"`, relay it and stop.** The reviewer\nthis skill names is not installed; tell the user to install the `plugin-dev` plugin from\nthe `claude-plugins-official` marketplace and re-run. Do not review the skill yourself.\n\n**Do not end your turn while the loop is running.** The Workflow tool returns a task id\nimmediately; the result comes later. In an interactive session the completion\nnotification re-invokes you — wait for it. In a non-interactive run (scripted, CI, eval)\nthere is no later turn: stopping abandons the loop mid-round, so after launching, poll\nthe task (TaskOutput with the returned task id, or sleep-and-recheck) until it completes,\nthen relay the result. A session that answers \"the loop is running, I'll report later\"\nhas lost the run.\n\n## Relaying the result\n\nThe workflow returns a structured result. Report it honestly — the distinctions matter:\n\n- **`converged: true`** — the last action was a review with zero critical\u002Fmajor findings.\n  Report rounds used, remaining minor findings (`open_minor_count`), and the artifact\n  paths (`ledger_path`, `metrics`).\n- **`capped: true`** — the fix budget ran out and the FINAL review still found blocking\n  issues. Say plainly: **capped, NOT converged**, and list `open_blocking`. Do not\n  present this as success.\n- **`escalation`** — the loop detected it was not converging (recurring findings,\n  non-decreasing counts, or a fix relocating a problem). Relay the escalation message and\n  finding ids to the user: this needs a design decision, not more rounds.\n- **`halted`** — a guard fired (scope violation, unregistered new files, a dead or\n  unavailable reviewer, or a finalize pass whose own edits failed the check that follows\n  it). Relay the paths in `violations`\u002F`new_untracked_files`, the sites in\n  `finalize_regressions`, and the notes.\n- **`notes`** always travel with the result — surface them; they include loud warnings\n  such as \"a git repository was initialized\".\n\n## Continuing after an escalation\n\nThe loop stops on escalation by design. When the user decides (e.g. \"keep the blocklist\nand document the limitation\"), start a fresh run with the same `target` plus:\n\n```json\n{ \"decision\": \"\u003Cthe user's ruling, verbatim>\" }\n```\n\nThe new run reloads the on-disk ledger, so every finding, rejection, and verdict carries\nover — rounds restart, re-derivation does not.\n\nTo stop a running loop, stop the workflow task (TaskStop); the ledger on disk is current\nto the last round and a re-run resumes from it.\n\n## What the loop enforces (so you do not have to)\n\n- **Fix verification** — the next review verifies every fix; fixes to executable\n  behavior carry pins that fail against the pre-fix code.\n- **Scope** — a mechanical git-diff check after every fix round, and after the finalize\n  pass, halts on any out-of-scope change; out-of-scope files git does not track are\n  guarded by content hash, since no diff would show them; completion also requires no\n  unregistered new files in scope.\n- **Report everything** — reviewers report all findings with severity; filtering happens\n  once, at the ledger verdict, and rejections are not re-litigated without new evidence.\n- **Finalize** — before completion the loop strips narration comments, collapses version\n  churn to exactly one bump (in `plugin.json` and the marketplace entry that repeats it),\n  and runs a docs-match-code pass. Those edits land after the last review, so a check\n  reads them: an over-eager narration strip or a false docs claim halts with\n  `finalize-regression` instead of passing as done.\n\n## When NOT to use\n\n- **One-time review**: dispatch the `plugin-dev:skill-reviewer` agent directly\n- **Quick single fixes**: edit the file directly\n- **Non-skill targets**: use the `code-improver` skill with a reviewer that fits the\n  target, or `pr-improver` for a branch\n- **Exploratory drafting**: manual iteration gives more control while the shape is fluid\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24},"Bash Glob Read TaskOutput TaskStop Workflow","\u003CSKILL_NAME_OR_PATH> [--max-rounds N]","main","321ccfe628eca0d314b0ee4eaffcdd8a05639aaf","plugins\u002Fcode-improver\u002Fskills\u002Fskill-improver",0,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills","https:\u002F\u002Fgithub.com\u002Fbongkage","2026-11-06 12:15:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add bongkage\u002Ftrailofbits-skills --skill skill-improver",{"tool":38,"command":39},"bunx","bunx skills add bongkage\u002Ftrailofbits-skills --skill skill-improver",{"tool":41,"command":42},"pnpm","pnpm dlx skills add bongkage\u002Ftrailofbits-skills --skill skill-improver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fcode-improver\u002Fskills\u002Fskill-improver\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M7CHJAESZRWKJXFQG55BMNAA","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fzeroize-audit\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7CHJ543G42A9GQC3PJE4F4V","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fyara-authoring\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7CHHYVFS1AKDTH3YDS1Y4K4","writing-lean-proofs","Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting-lean-proofs\u002Fskills\u002Fwriting-lean-proofs\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7CHHQXA39M4965MV2RMM5YS","vulnerability-triage-brocards","This skill should be used when the user asks to \"triage a vulnerability report\", \"assess a CVE\", \"evaluate a bug bounty submission\", \"decide if a finding is valid\", \"review a security finding\", \"dismiss a vulnerability\", \"should we fix this CVE\", \"prioritize a vulnerability report\", or needs to determine whether an incoming vulnerability report warrants investigation. Applies 7 brocards (rules of thumb) to systematically accept, dismiss, or request more information on vulnerability reports, or needs to filter raw findings from agentic vulnerability discovery pipelines before human review.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fvulnerability-triage-brocards\u002Fskills\u002Fvulnerability-triage-brocards\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7CHHJVQC2ZG2M310GXT0T42","variant-analysis","Hunts for the other instances of a bug already found — the variants of one root cause across a codebase. Use immediately after a vulnerability, logic bug, or bad pattern turns up in a specific file and the question becomes where else it occurs, including the bare conversational form (\"are there others like this?\", \"is this the same bug?\"). Also for generalizing one known instance into a CodeQL or Semgrep query for its whole pattern family, and for triaging a set of look-alike candidates against a known root cause. Not for initial discovery with no bug in hand.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fvariant-analysis\u002Fskills\u002Fvariant-analysis\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7CHHC1GM5GH585ZWGP7D03P","vector-forge","Mutation-driven test vector generation. Finds implementations of a cryptographic algorithm or protocol, runs mutation testing to identify escaped mutants, then generates new test vectors that deliberately exercise the uncovered code paths. Compares before\u002Fafter mutation kill rates to prove vector effectiveness. Use when generating cryptographic test vectors, measuring Wycheproof coverage gaps, finding escaped mutants via mutation testing, creating cross-implementation test suites, or improving test vector coverage for crypto primitives.","https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Ftrailmark\u002Fskills\u002Fvector-forge\u002FSKILL.md",[],[]]