[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EG8HD823KDA5B5GW0QA6RG":3,"skill-same:01M7EG8HD823KDA5B5GW0QA6RG":46},{"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},"01M7EG8HD823KDA5B5GW0QA6RG","completion-check",null,"Completion Check: Verify Infrastructure Is Wired","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-安全渗透\u002Fcompletion-check\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: completion-check\ndescription: \"Completion Check: Verify Infrastructure Is Wired\"\nuser-invocable: false\n---\n\n# Completion Check: Verify Infrastructure Is Wired\n\nWhen building infrastructure, verify it's actually connected to the system before marking as complete.\n\n## Pattern\n\nInfrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.\n\n## DO\n\n1. **Trace the execution path** - Follow from user intent to actual code execution:\n   ```bash\n   # Example: Verify Task tool spawns correctly\n   grep -r \"claude -p\" src\u002F\n   grep -r \"Task(\" src\u002F\n   ```\n\n2. **Check hooks are registered**, not just implemented:\n   ```bash\n   # Hook exists?\n   ls -la .claude\u002Fhooks\u002Fmy-hook.sh\n\n   # Hook registered in settings?\n   grep \"my-hook\" .claude\u002Fsettings.json\n   ```\n\n3. **Verify database connections** - Ensure infrastructure uses the right backend:\n   ```bash\n   # Check connection strings\n   grep -r \"postgresql:\u002F\u002F\" src\u002F\n   grep -r \"sqlite:\" src\u002F  # Should NOT find if PostgreSQL expected\n   ```\n\n4. **Test end-to-end** - Run the feature and verify infrastructure is invoked:\n   ```bash\n   # Add debug logging\n   echo \"DEBUG: DAG spawn invoked\" >> \u002Ftmp\u002Fdebug.log\n\n   # Trigger feature\n   uv run python -m my_feature\n\n   # Verify infrastructure was called\n   cat \u002Ftmp\u002Fdebug.log\n   ```\n\n5. **Search for orphaned implementations**:\n   ```bash\n   # Find functions defined but never called\n   ast-grep --pattern 'async function $NAME() { $$$ }' | \\\n     xargs -I {} grep -r \"{}\" src\u002F\n   ```\n\n## DON'T\n\n- Mark infrastructure \"complete\" without testing execution path\n- Assume code is wired just because it exists\n- Build parallel systems (Task tool vs claude -p spawn)\n- Use wrong backends (SQLite when PostgreSQL is architected)\n- Skip end-to-end testing (\"it compiles\" ≠ \"it runs\")\n\n## Completion Checklist\n\nBefore declaring infrastructure complete:\n\n- [ ] Traced execution path from entry point to infrastructure\n- [ ] Verified hooks are registered in .claude\u002Fsettings.json\n- [ ] Confirmed correct database\u002Fbackend in use\n- [ ] Ran end-to-end test showing infrastructure invoked\n- [ ] Searched for dead code or parallel implementations\n- [ ] Checked configuration files match implementation\n\n## Example: DAG Task Graph\n\n**Wrong approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Implemented DAG dependencies\n✓ Added spawn logic\n✗ Never wired - Task tool still runs instead\n✗ Used SQLite instead of PostgreSQL\n```\n\n**Right approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Wired into Task tool execution path\n✓ Verified claude -p spawn is called\n✓ Confirmed PostgreSQL backend in use\n✓ Tested: user calls Task() → DAG spawns → beads execute\n✓ No parallel implementations found\n```\n\n## Source Sessions\n\n- This session: Architecture gap discovery - DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL\n","# Completion Check: Verify Infrastructure Is Wired\n\nWhen building infrastructure, verify it's actually connected to the system before marking as complete.\n\n## Pattern\n\nInfrastructure is not done when the code is written - it's done when it's wired into the system and actively used. Dead code (built but never called) is wasted effort.\n\n## DO\n\n1. **Trace the execution path** - Follow from user intent to actual code execution:\n   ```bash\n   # Example: Verify Task tool spawns correctly\n   grep -r \"claude -p\" src\u002F\n   grep -r \"Task(\" src\u002F\n   ```\n\n2. **Check hooks are registered**, not just implemented:\n   ```bash\n   # Hook exists?\n   ls -la .claude\u002Fhooks\u002Fmy-hook.sh\n\n   # Hook registered in settings?\n   grep \"my-hook\" .claude\u002Fsettings.json\n   ```\n\n3. **Verify database connections** - Ensure infrastructure uses the right backend:\n   ```bash\n   # Check connection strings\n   grep -r \"postgresql:\u002F\u002F\" src\u002F\n   grep -r \"sqlite:\" src\u002F  # Should NOT find if PostgreSQL expected\n   ```\n\n4. **Test end-to-end** - Run the feature and verify infrastructure is invoked:\n   ```bash\n   # Add debug logging\n   echo \"DEBUG: DAG spawn invoked\" >> \u002Ftmp\u002Fdebug.log\n\n   # Trigger feature\n   uv run python -m my_feature\n\n   # Verify infrastructure was called\n   cat \u002Ftmp\u002Fdebug.log\n   ```\n\n5. **Search for orphaned implementations**:\n   ```bash\n   # Find functions defined but never called\n   ast-grep --pattern 'async function $NAME() { $$$ }' | \\\n     xargs -I {} grep -r \"{}\" src\u002F\n   ```\n\n## DON'T\n\n- Mark infrastructure \"complete\" without testing execution path\n- Assume code is wired just because it exists\n- Build parallel systems (Task tool vs claude -p spawn)\n- Use wrong backends (SQLite when PostgreSQL is architected)\n- Skip end-to-end testing (\"it compiles\" ≠ \"it runs\")\n\n## Completion Checklist\n\nBefore declaring infrastructure complete:\n\n- [ ] Traced execution path from entry point to infrastructure\n- [ ] Verified hooks are registered in .claude\u002Fsettings.json\n- [ ] Confirmed correct database\u002Fbackend in use\n- [ ] Ran end-to-end test showing infrastructure invoked\n- [ ] Searched for dead code or parallel implementations\n- [ ] Checked configuration files match implementation\n\n## Example: DAG Task Graph\n\n**Wrong approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Implemented DAG dependencies\n✓ Added spawn logic\n✗ Never wired - Task tool still runs instead\n✗ Used SQLite instead of PostgreSQL\n```\n\n**Right approach:**\n```\n✓ Built BeadsTaskGraph class\n✓ Wired into Task tool execution path\n✓ Verified claude -p spawn is called\n✓ Confirmed PostgreSQL backend in use\n✓ Tested: user calls Task() → DAG spawns → beads execute\n✓ No parallel implementations found\n```\n\n## Source Sessions\n\n- This session: Architecture gap discovery - DAG built but not wired, Task tool runs instead of spawn, SQLite used instead of PostgreSQL\n",{"name":5,"description":7,"user-invocable":20},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fcompletion-check",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 completion-check",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill completion-check",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill completion-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fcompletion-check\u002FSKILL.md",true,[],[47,55,60,67,74,81],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":54},"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":56,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":54},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":54},"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":68,"name":69,"nameZh":6,"description":70,"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":54},"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":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":54},"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":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":54},"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",[],[]]