[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CH5WSSFDYGP2ZGCYVT00C3":3,"skill-same:01M7CH5WSSFDYGP2ZGCYVT00C3":64},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7CH5WSSFDYGP2ZGCYVT00C3","secure-workflow-guide",null,"Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability\u002FERC conformance\u002Ftoken integration), generates visual security diagrams, helps document security properties for fuzzing\u002Fverification, and reviews manual security areas. Use when securing a smart contract end to end rather than hunting one bug, checking a project on every check-in or before deployment, triaging a Slither report, or asking where to start on smart contract security.","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\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: secure-workflow-guide\ndescription: Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability\u002FERC conformance\u002Ftoken integration), generates visual security diagrams, helps document security properties for fuzzing\u002Fverification, and reviews manual security areas. Use when securing a smart contract end to end rather than hunting one bug, checking a project on every check-in or before deployment, triaging a Slither report, or asking where to start on smart contract security.\n---\n\n# Secure Workflow Guide\n\n## Purpose\n\nGuides through Trail of Bits' secure development workflow - a 5-step process to enhance smart contract security throughout development.\n\n**Use this**: On every check-in, before deployment, or when you want a security review\n\n---\n\n## The 5-Step Workflow\n\nCovers a security workflow including:\n\n### Step 1: Check for Known Security Issues\nRun Slither with 70+ built-in detectors to find common vulnerabilities:\n- Parse findings by severity\n- Explain each issue with file references\n- Recommend fixes\n- Help triage false positives\n\n**Goal**: Clean Slither report or documented triages\n\n### Step 2: Check Special Features\nDetect and validate applicable features:\n- **Upgradeability**: slither-check-upgradeability (17 upgrade risks)\n- **ERC conformance**: slither-check-erc (6 common specs)\n- **Token integration**: Recommend token-integration-analyzer skill\n- **Security properties**: slither-prop for ERC20\n\n**Note**: Only runs checks that apply to your codebase\n\n### Step 3: Visual Security Inspection\nGenerate 3 security diagrams:\n- **Inheritance graph**: Identify shadowing and C3 linearization issues\n- **Function summary**: Show visibility and access controls\n- **Variables and authorization**: Map who can write to state variables\n\nReview each diagram for security concerns\n\n### Step 4: Document Security Properties\nHelp document critical security properties:\n- State machine transitions and invariants\n- Access control requirements\n- Arithmetic constraints and precision\n- External interaction safety\n- Standards conformance\n\nThen set up testing:\n- **Echidna**: Property-based fuzzing with invariants\n- **Manticore**: Formal verification with symbolic execution\n- **Custom Slither checks**: Project-specific business logic\n\n**Note**: Most important activity for security\n\n### Step 5: Manual Review Areas\nAnalyze areas automated tools miss:\n- **Privacy**: On-chain secrets, commit-reveal needs\n- **Front-running**: Slippage protection, ordering risks, MEV\n- **Cryptography**: Weak randomness, signature issues, hash collisions\n- **DeFi interactions**: Oracle manipulation, flash loans, protocol assumptions\n\nSearch codebase for these patterns and flag risks\n\nFor detailed instructions, commands, and explanations for each step, see [WORKFLOW_STEPS.md](resources\u002FWORKFLOW_STEPS.md).\n\n---\n\n## How I Work\n\nWhen invoked, I will:\n\n1. **Explore your codebase** to understand structure\n2. **Run Step 1**: Slither security scan\n3. **Detect and run Step 2**: Special feature checks (only what applies)\n4. **Generate Step 3**: Visual security diagrams\n5. **Guide Step 4**: Security property documentation\n6. **Analyze Step 5**: Manual review areas\n7. **Provide action plan**: Prioritized fixes and next steps\n\nAdapts based on:\n- What tools you have installed\n- What's applicable to your project\n- Where you are in development\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Slither not available, I'll check manually\" | Manual checking misses 70+ detector patterns | Install and run Slither, or document why it's blocked |\n| \"Can't generate diagrams, I'll describe the architecture\" | Descriptions aren't visual - diagrams reveal patterns text misses | Execute slither --print commands, generate actual visual outputs |\n| \"No upgrades detected, skip upgradeability checks\" | Proxies and upgrades are often implicit or planned | Verify with codebase search before skipping Step 2 checks |\n| \"Not a token, skip ERC checks\" | Tokens can be integrated without obvious ERC inheritance | Check for token interactions, transfers, balances before skipping |\n| \"Can't set up Echidna now, suggesting it for later\" | Property-based testing is Step 4, not optional | Document properties now, set up fuzzing infrastructure |\n| \"No DeFi interactions, skip oracle\u002Fflash loan checks\" | DeFi patterns appear in unexpected places (price feeds, external calls) | Complete Step 5 manual review, search codebase for patterns |\n| \"This step doesn't apply to my project\" | \"Not applicable\" without verification = missed vulnerabilities | Verify with explicit codebase search before declaring N\u002FA |\n| \"I'll provide generic security advice instead of running workflow\" | Generic advice isn't actionable, workflow finds specific issues | Execute all 5 steps, generate project-specific findings with file:line references |\n\n---\n\n## Example Output\n\nWhen I complete the workflow, you'll get a comprehensive security report covering:\n\n- **Step 1**: Slither findings with severity, file references, and fix recommendations\n- **Step 2**: Special feature validation results (upgradeability, ERC conformance, etc.)\n- **Step 3**: Visual diagrams analyzing inheritance, functions, and state variable authorization\n- **Step 4**: Documented security properties and testing setup (Echidna\u002FManticore)\n- **Step 5**: Manual review findings (privacy, front-running, cryptography, DeFi risks)\n- **Action plan**: Critical\u002Fhigh\u002Fmedium priority tasks with effort estimates\n- **Workflow checklist**: Progress on all 5 steps\n\nFor a complete example workflow report, see [EXAMPLE_REPORT.md](resources\u002FEXAMPLE_REPORT.md).\n\n---\n\n## What You'll Get\n\n**Security Report**:\n- Slither findings with severity and fixes\n- Special feature validation results\n- Visual diagrams (PNG\u002FPDF)\n- Manual review findings\n\n**Action Plan**:\n- [ ] Critical issues to fix immediately\n- [ ] Security properties to document\n- [ ] Testing to set up (Echidna\u002FManticore)\n- [ ] Manual areas to review\n\n**Workflow Checklist**:\n- [ ] Clean Slither report\n- [ ] Special features validated\n- [ ] Visual inspection complete\n- [ ] Properties documented\n- [ ] Manual review done\n\n---\n\n## Getting Help\n\n**Trail of Bits Resources**:\n- Office Hours: Every Tuesday ([schedule](https:\u002F\u002Fmeetings.hubspot.com\u002Ftrailofbits\u002Foffice-hours))\n- Empire Hacking Slack: #crytic and #ethereum channels\n\n**Other Security**:\n- Remember: Security is about more than smart contracts\n- Off-chain security (owner keys, infrastructure) equally critical\n\n---\n\n## Ready to Start\n\nLet me know when you're ready and I'll run through the workflow with your codebase!\n","# Secure Workflow Guide\n\n## Purpose\n\nGuides through Trail of Bits' secure development workflow - a 5-step process to enhance smart contract security throughout development.\n\n**Use this**: On every check-in, before deployment, or when you want a security review\n\n---\n\n## The 5-Step Workflow\n\nCovers a security workflow including:\n\n### Step 1: Check for Known Security Issues\nRun Slither with 70+ built-in detectors to find common vulnerabilities:\n- Parse findings by severity\n- Explain each issue with file references\n- Recommend fixes\n- Help triage false positives\n\n**Goal**: Clean Slither report or documented triages\n\n### Step 2: Check Special Features\nDetect and validate applicable features:\n- **Upgradeability**: slither-check-upgradeability (17 upgrade risks)\n- **ERC conformance**: slither-check-erc (6 common specs)\n- **Token integration**: Recommend token-integration-analyzer skill\n- **Security properties**: slither-prop for ERC20\n\n**Note**: Only runs checks that apply to your codebase\n\n### Step 3: Visual Security Inspection\nGenerate 3 security diagrams:\n- **Inheritance graph**: Identify shadowing and C3 linearization issues\n- **Function summary**: Show visibility and access controls\n- **Variables and authorization**: Map who can write to state variables\n\nReview each diagram for security concerns\n\n### Step 4: Document Security Properties\nHelp document critical security properties:\n- State machine transitions and invariants\n- Access control requirements\n- Arithmetic constraints and precision\n- External interaction safety\n- Standards conformance\n\nThen set up testing:\n- **Echidna**: Property-based fuzzing with invariants\n- **Manticore**: Formal verification with symbolic execution\n- **Custom Slither checks**: Project-specific business logic\n\n**Note**: Most important activity for security\n\n### Step 5: Manual Review Areas\nAnalyze areas automated tools miss:\n- **Privacy**: On-chain secrets, commit-reveal needs\n- **Front-running**: Slippage protection, ordering risks, MEV\n- **Cryptography**: Weak randomness, signature issues, hash collisions\n- **DeFi interactions**: Oracle manipulation, flash loans, protocol assumptions\n\nSearch codebase for these patterns and flag risks\n\nFor detailed instructions, commands, and explanations for each step, see [WORKFLOW_STEPS.md](resources\u002FWORKFLOW_STEPS.md).\n\n---\n\n## How I Work\n\nWhen invoked, I will:\n\n1. **Explore your codebase** to understand structure\n2. **Run Step 1**: Slither security scan\n3. **Detect and run Step 2**: Special feature checks (only what applies)\n4. **Generate Step 3**: Visual security diagrams\n5. **Guide Step 4**: Security property documentation\n6. **Analyze Step 5**: Manual review areas\n7. **Provide action plan**: Prioritized fixes and next steps\n\nAdapts based on:\n- What tools you have installed\n- What's applicable to your project\n- Where you are in development\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Slither not available, I'll check manually\" | Manual checking misses 70+ detector patterns | Install and run Slither, or document why it's blocked |\n| \"Can't generate diagrams, I'll describe the architecture\" | Descriptions aren't visual - diagrams reveal patterns text misses | Execute slither --print commands, generate actual visual outputs |\n| \"No upgrades detected, skip upgradeability checks\" | Proxies and upgrades are often implicit or planned | Verify with codebase search before skipping Step 2 checks |\n| \"Not a token, skip ERC checks\" | Tokens can be integrated without obvious ERC inheritance | Check for token interactions, transfers, balances before skipping |\n| \"Can't set up Echidna now, suggesting it for later\" | Property-based testing is Step 4, not optional | Document properties now, set up fuzzing infrastructure |\n| \"No DeFi interactions, skip oracle\u002Fflash loan checks\" | DeFi patterns appear in unexpected places (price feeds, external calls) | Complete Step 5 manual review, search codebase for patterns |\n| \"This step doesn't apply to my project\" | \"Not applicable\" without verification = missed vulnerabilities | Verify with explicit codebase search before declaring N\u002FA |\n| \"I'll provide generic security advice instead of running workflow\" | Generic advice isn't actionable, workflow finds specific issues | Execute all 5 steps, generate project-specific findings with file:line references |\n\n---\n\n## Example Output\n\nWhen I complete the workflow, you'll get a comprehensive security report covering:\n\n- **Step 1**: Slither findings with severity, file references, and fix recommendations\n- **Step 2**: Special feature validation results (upgradeability, ERC conformance, etc.)\n- **Step 3**: Visual diagrams analyzing inheritance, functions, and state variable authorization\n- **Step 4**: Documented security properties and testing setup (Echidna\u002FManticore)\n- **Step 5**: Manual review findings (privacy, front-running, cryptography, DeFi risks)\n- **Action plan**: Critical\u002Fhigh\u002Fmedium priority tasks with effort estimates\n- **Workflow checklist**: Progress on all 5 steps\n\nFor a complete example workflow report, see [EXAMPLE_REPORT.md](resources\u002FEXAMPLE_REPORT.md).\n\n---\n\n## What You'll Get\n\n**Security Report**:\n- Slither findings with severity and fixes\n- Special feature validation results\n- Visual diagrams (PNG\u002FPDF)\n- Manual review findings\n\n**Action Plan**:\n- [ ] Critical issues to fix immediately\n- [ ] Security properties to document\n- [ ] Testing to set up (Echidna\u002FManticore)\n- [ ] Manual areas to review\n\n**Workflow Checklist**:\n- [ ] Clean Slither report\n- [ ] Special features validated\n- [ ] Visual inspection complete\n- [ ] Properties documented\n- [ ] Manual review done\n\n---\n\n## Getting Help\n\n**Trail of Bits Resources**:\n- Office Hours: Every Tuesday ([schedule](https:\u002F\u002Fmeetings.hubspot.com\u002Ftrailofbits\u002Foffice-hours))\n- Empire Hacking Slack: #crytic and #ethereum channels\n\n**Other Security**:\n- Remember: Security is about more than smart contracts\n- Off-chain security (owner keys, infrastructure) equally critical\n\n---\n\n## Ready to Start\n\nLet me know when you're ready and I'll run through the workflow with your codebase!\n",{"name":5,"description":7},"main","321ccfe628eca0d314b0ee4eaffcdd8a05639aaf","plugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide",0,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills","https:\u002F\u002Fgithub.com\u002Fbongkage","2026-11-06 12:15:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add bongkage\u002Ftrailofbits-skills --skill secure-workflow-guide",{"tool":36,"command":37},"bunx","bunx skills add bongkage\u002Ftrailofbits-skills --skill secure-workflow-guide",{"tool":39,"command":40},"pnpm","pnpm dlx skills add bongkage\u002Ftrailofbits-skills --skill secure-workflow-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002FSKILL.md",true,[44,50,56,60],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",128,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Ftrail-of-bits-mark.svg","ASSET","资产文件",3084,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002Fassets\u002Ftrail-of-bits-mark.svg",{"path":57,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":59},"resources\u002FEXAMPLE_REPORT.md",7374,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002Fresources\u002FEXAMPLE_REPORT.md",{"path":61,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":62,"sourceHtmlUrl":63},"resources\u002FWORKFLOW_STEPS.md",3058,"https:\u002F\u002Fgithub.com\u002Fbongkage\u002Ftrailofbits-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fbuilding-secure-contracts\u002Fskills\u002Fsecure-workflow-guide\u002Fresources\u002FWORKFLOW_STEPS.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[]]