[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ES8VAJWAPE6700C5K40TPC":3,"skill-same:01M7ES8VAJWAPE6700C5K40TPC":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ES8VAJWAPE6700C5K40TPC","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\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","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fsecure-workflow-guide",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill secure-workflow-guide",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill secure-workflow-guide",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill secure-workflow-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecure-workflow-guide\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",250,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecure-workflow-guide\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"resources\u002FEXAMPLE_REPORT.md",7374,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecure-workflow-guide\u002Fresources\u002FEXAMPLE_REPORT.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"resources\u002FWORKFLOW_STEPS.md",3058,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fsecure-workflow-guide\u002Fresources\u002FWORKFLOW_STEPS.md",[61,69,74,81,88,95],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":70,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":68},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":68},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":68},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":68},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":68},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]