[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79PD5P6SN8GVMC84WTX68MH":3,"skill-same:01M79PD5P6SN8GVMC84WTX68MH":68},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M79PD5P6SN8GVMC84WTX68MH","differential-review",null,"Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.","ankaboot-source\u002Fboucle","ankaboot-source","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F88089122?v=4","01M79P4HZGM4NXFWV0SB0HGQ51","ankaboot","01M79P4J0GNNZ7E7F9B0RZNSNX",2,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: differential-review\ndescription: >\n  Performs security-focused differential review of code changes (PRs, commits, diffs).\n  Adapts analysis depth to codebase size, uses git history for context, calculates\n  blast radius, checks test coverage, and generates comprehensive markdown reports.\n  Automatically detects and prevents security regressions.\nallowed-tools: Read Write Grep Glob Bash\n---\n\n# Differential Security Review\n\nSecurity-focused code review for PRs, commits, and diffs.\n\n## Core Principles\n\n1. **Risk-First**: Focus on auth, crypto, value transfer, external calls\n2. **Evidence-Based**: Every finding backed by git history, line numbers, attack scenarios\n3. **Adaptive**: Scale to codebase size (SMALL\u002FMEDIUM\u002FLARGE)\n4. **Honest**: Explicitly state coverage limits and confidence level\n5. **Output-Driven**: Always generate comprehensive markdown report file\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Small PR, quick review\" | Heartbleed was 2 lines | Classify by RISK, not size |\n| \"I know this codebase\" | Familiarity breeds blind spots | Build explicit baseline context |\n| \"Git history takes too long\" | History reveals regressions | Never skip Phase 1 |\n| \"Blast radius is obvious\" | You'll miss transitive callers | Calculate quantitatively |\n| \"No tests = not my problem\" | Missing tests = elevated risk rating | Flag in report, elevate severity |\n| \"Just a refactor, no security impact\" | Refactors break invariants | Analyze as HIGH until proven LOW |\n| \"I'll explain verbally\" | No artifact = findings lost | Always write report |\n\n---\n\n## Quick Reference\n\n### Codebase Size Strategy\n\n| Codebase Size | Strategy | Approach |\n|---------------|----------|----------|\n| SMALL (\u003C20 files) | DEEP | Read all deps, full git blame |\n| MEDIUM (20-200) | FOCUSED | 1-hop deps, priority files |\n| LARGE (200+) | SURGICAL | Critical paths only |\n\n### Risk Level Triggers\n\n| Risk Level | Triggers |\n|------------|----------|\n| HIGH | Auth, crypto, external calls, value transfer, validation removal |\n| MEDIUM | Business logic, state changes, new public APIs |\n| LOW | Comments, tests, UI, logging |\n\n---\n\n## Workflow Overview\n\n```\nPre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage\n    ↓              ↓                    ↓                        ↓\nPhase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report\n```\n\n---\n\n## Decision Tree\n\n**Starting a review?**\n\n```\n├─ Need detailed phase-by-phase methodology?\n│  └─ Read: methodology.md\n│     (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)\n│\n├─ Analyzing HIGH RISK change?\n│  ├─ Read: adversarial.md\n│  │  (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)\n│  └─ Or delegate to: adversarial-modeler agent\n│     (Autonomous attacker modeling with concrete exploit scenarios)\n│\n├─ Writing the final report?\n│  └─ Read: reporting.md\n│     (Phase 6: Report structure, templates, formatting guidelines)\n│\n├─ Looking for specific vulnerability patterns?\n│  └─ Read: patterns.md\n│     (Regressions, reentrancy, access control, overflow, etc.)\n│\n└─ Quick triage only?\n   └─ Use Quick Reference above, skip detailed docs\n```\n\n---\n\n## Agents\n\n**`adversarial-modeler`** — Models attacker perspectives and builds exploit\nscenarios for HIGH RISK code changes. Follows the 5-step adversarial\nmethodology (attacker model, attack vectors, exploitability rating, exploit\nscenario, baseline cross-reference) and produces structured vulnerability\nreports. Delegate to this agent when Phase 5 analysis is needed on high-risk\nchanges.\n\n---\n\n## Quality Checklist\n\nBefore delivering:\n\n- [ ] All changed files analyzed\n- [ ] Git blame on removed security code\n- [ ] Blast radius calculated for HIGH risk\n- [ ] Attack scenarios are concrete (not generic)\n- [ ] Findings reference specific line numbers + commits\n- [ ] Report file generated\n- [ ] User notified with summary\n\n---\n\n## Integration\n\n**audit-context-building skill:**\n- Pre-Analysis: Build baseline context\n- Phase 4: Deep context on HIGH RISK changes\n\n**issue-writer skill:**\n- Transform findings into formal audit reports\n- Command: `issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`\n\n---\n\n## Example Usage\n\n### Quick Triage (Small PR)\n```\nInput: 5 file PR, 2 HIGH RISK files\nStrategy: Use Quick Reference\n1. Classify risk level per file (2 HIGH, 3 LOW)\n2. Focus on 2 HIGH files only\n3. Git blame removed code\n4. Generate minimal report\nTime: ~30 minutes\n```\n\n### Standard Review (Medium Codebase)\n```\nInput: 80 files, 12 HIGH RISK changes\nStrategy: FOCUSED (see methodology.md)\n1. Full workflow on HIGH RISK files\n2. Surface scan on MEDIUM\n3. Skip LOW risk files\n4. Complete report with all sections\nTime: ~3-4 hours\n```\n\n### Deep Audit (Large, Critical Change)\n```\nInput: 450 files, auth system rewrite\nStrategy: SURGICAL + audit-context-building\n1. Baseline context with audit-context-building\n2. Deep analysis on auth changes only\n3. Blast radius analysis\n4. Adversarial modeling\n5. Comprehensive report\nTime: ~6-8 hours\n```\n\n---\n\n## When NOT to Use This Skill\n\n- **Greenfield code** (no baseline to compare)\n- **Documentation-only changes** (no security impact)\n- **Formatting\u002Flinting** (cosmetic changes)\n- **User explicitly requests quick summary only** (they accept risk)\n\nFor these cases, use standard code review instead.\n\n---\n\n## Red Flags (Stop and Investigate)\n\n**Immediate escalation triggers:**\n- Removed code from \"security\", \"CVE\", or \"fix\" commits\n- Access control modifiers removed (onlyOwner, internal → external)\n- Validation removed without replacement\n- External calls added without checks\n- High blast radius (50+ callers) + HIGH risk change\n\nThese patterns require adversarial analysis even in quick triage.\n\n---\n\n## Tips for Best Results\n\n**Do:**\n- Start with git blame for removed code\n- Calculate blast radius early to prioritize\n- Generate concrete attack scenarios\n- Reference specific line numbers and commits\n- Be honest about coverage limitations\n- Always generate the output file\n\n**Don't:**\n- Skip git history analysis\n- Make generic findings without evidence\n- Claim full analysis when time-limited\n- Forget to check test coverage\n- Miss high blast radius changes\n- Output report only to chat (file required)\n\n---\n\n## Supporting Documentation\n\n- **[methodology.md](methodology.md)** - Detailed phase-by-phase workflow (Phases 0-4)\n- **[adversarial.md](adversarial.md)** - Attacker modeling and exploit scenarios (Phase 5)\n- **[reporting.md](reporting.md)** - Report structure and formatting (Phase 6)\n- **[patterns.md](patterns.md)** - Common vulnerability patterns reference\n\n---\n\n**For first-time users:** Start with [methodology.md](methodology.md) to understand the complete workflow.\n\n**For experienced users:** Use this page's Quick Reference and Decision Tree to navigate directly to needed content.\n","# Differential Security Review\n\nSecurity-focused code review for PRs, commits, and diffs.\n\n## Core Principles\n\n1. **Risk-First**: Focus on auth, crypto, value transfer, external calls\n2. **Evidence-Based**: Every finding backed by git history, line numbers, attack scenarios\n3. **Adaptive**: Scale to codebase size (SMALL\u002FMEDIUM\u002FLARGE)\n4. **Honest**: Explicitly state coverage limits and confidence level\n5. **Output-Driven**: Always generate comprehensive markdown report file\n\n---\n\n## Rationalizations (Do Not Skip)\n\n| Rationalization | Why It's Wrong | Required Action |\n|-----------------|----------------|-----------------|\n| \"Small PR, quick review\" | Heartbleed was 2 lines | Classify by RISK, not size |\n| \"I know this codebase\" | Familiarity breeds blind spots | Build explicit baseline context |\n| \"Git history takes too long\" | History reveals regressions | Never skip Phase 1 |\n| \"Blast radius is obvious\" | You'll miss transitive callers | Calculate quantitatively |\n| \"No tests = not my problem\" | Missing tests = elevated risk rating | Flag in report, elevate severity |\n| \"Just a refactor, no security impact\" | Refactors break invariants | Analyze as HIGH until proven LOW |\n| \"I'll explain verbally\" | No artifact = findings lost | Always write report |\n\n---\n\n## Quick Reference\n\n### Codebase Size Strategy\n\n| Codebase Size | Strategy | Approach |\n|---------------|----------|----------|\n| SMALL (\u003C20 files) | DEEP | Read all deps, full git blame |\n| MEDIUM (20-200) | FOCUSED | 1-hop deps, priority files |\n| LARGE (200+) | SURGICAL | Critical paths only |\n\n### Risk Level Triggers\n\n| Risk Level | Triggers |\n|------------|----------|\n| HIGH | Auth, crypto, external calls, value transfer, validation removal |\n| MEDIUM | Business logic, state changes, new public APIs |\n| LOW | Comments, tests, UI, logging |\n\n---\n\n## Workflow Overview\n\n```\nPre-Analysis → Phase 0: Triage → Phase 1: Code Analysis → Phase 2: Test Coverage\n    ↓              ↓                    ↓                        ↓\nPhase 3: Blast Radius → Phase 4: Deep Context → Phase 5: Adversarial → Phase 6: Report\n```\n\n---\n\n## Decision Tree\n\n**Starting a review?**\n\n```\n├─ Need detailed phase-by-phase methodology?\n│  └─ Read: methodology.md\n│     (Pre-Analysis + Phases 0-4: triage, code analysis, test coverage, blast radius)\n│\n├─ Analyzing HIGH RISK change?\n│  ├─ Read: adversarial.md\n│  │  (Phase 5: Attacker modeling, exploit scenarios, exploitability rating)\n│  └─ Or delegate to: adversarial-modeler agent\n│     (Autonomous attacker modeling with concrete exploit scenarios)\n│\n├─ Writing the final report?\n│  └─ Read: reporting.md\n│     (Phase 6: Report structure, templates, formatting guidelines)\n│\n├─ Looking for specific vulnerability patterns?\n│  └─ Read: patterns.md\n│     (Regressions, reentrancy, access control, overflow, etc.)\n│\n└─ Quick triage only?\n   └─ Use Quick Reference above, skip detailed docs\n```\n\n---\n\n## Agents\n\n**`adversarial-modeler`** — Models attacker perspectives and builds exploit\nscenarios for HIGH RISK code changes. Follows the 5-step adversarial\nmethodology (attacker model, attack vectors, exploitability rating, exploit\nscenario, baseline cross-reference) and produces structured vulnerability\nreports. Delegate to this agent when Phase 5 analysis is needed on high-risk\nchanges.\n\n---\n\n## Quality Checklist\n\nBefore delivering:\n\n- [ ] All changed files analyzed\n- [ ] Git blame on removed security code\n- [ ] Blast radius calculated for HIGH risk\n- [ ] Attack scenarios are concrete (not generic)\n- [ ] Findings reference specific line numbers + commits\n- [ ] Report file generated\n- [ ] User notified with summary\n\n---\n\n## Integration\n\n**audit-context-building skill:**\n- Pre-Analysis: Build baseline context\n- Phase 4: Deep context on HIGH RISK changes\n\n**issue-writer skill:**\n- Transform findings into formal audit reports\n- Command: `issue-writer --input DIFFERENTIAL_REVIEW_REPORT.md --format audit-report`\n\n---\n\n## Example Usage\n\n### Quick Triage (Small PR)\n```\nInput: 5 file PR, 2 HIGH RISK files\nStrategy: Use Quick Reference\n1. Classify risk level per file (2 HIGH, 3 LOW)\n2. Focus on 2 HIGH files only\n3. Git blame removed code\n4. Generate minimal report\nTime: ~30 minutes\n```\n\n### Standard Review (Medium Codebase)\n```\nInput: 80 files, 12 HIGH RISK changes\nStrategy: FOCUSED (see methodology.md)\n1. Full workflow on HIGH RISK files\n2. Surface scan on MEDIUM\n3. Skip LOW risk files\n4. Complete report with all sections\nTime: ~3-4 hours\n```\n\n### Deep Audit (Large, Critical Change)\n```\nInput: 450 files, auth system rewrite\nStrategy: SURGICAL + audit-context-building\n1. Baseline context with audit-context-building\n2. Deep analysis on auth changes only\n3. Blast radius analysis\n4. Adversarial modeling\n5. Comprehensive report\nTime: ~6-8 hours\n```\n\n---\n\n## When NOT to Use This Skill\n\n- **Greenfield code** (no baseline to compare)\n- **Documentation-only changes** (no security impact)\n- **Formatting\u002Flinting** (cosmetic changes)\n- **User explicitly requests quick summary only** (they accept risk)\n\nFor these cases, use standard code review instead.\n\n---\n\n## Red Flags (Stop and Investigate)\n\n**Immediate escalation triggers:**\n- Removed code from \"security\", \"CVE\", or \"fix\" commits\n- Access control modifiers removed (onlyOwner, internal → external)\n- Validation removed without replacement\n- External calls added without checks\n- High blast radius (50+ callers) + HIGH risk change\n\nThese patterns require adversarial analysis even in quick triage.\n\n---\n\n## Tips for Best Results\n\n**Do:**\n- Start with git blame for removed code\n- Calculate blast radius early to prioritize\n- Generate concrete attack scenarios\n- Reference specific line numbers and commits\n- Be honest about coverage limitations\n- Always generate the output file\n\n**Don't:**\n- Skip git history analysis\n- Make generic findings without evidence\n- Claim full analysis when time-limited\n- Forget to check test coverage\n- Miss high blast radius changes\n- Output report only to chat (file required)\n\n---\n\n## Supporting Documentation\n\n- **[methodology.md](methodology.md)** - Detailed phase-by-phase workflow (Phases 0-4)\n- **[adversarial.md](adversarial.md)** - Attacker modeling and exploit scenarios (Phase 5)\n- **[reporting.md](reporting.md)** - Report structure and formatting (Phase 6)\n- **[patterns.md](patterns.md)** - Common vulnerability patterns reference\n\n---\n\n**For first-time users:** Start with [methodology.md](methodology.md) to understand the complete workflow.\n\n**For experienced users:** Use this page's Quick Reference and Decision Tree to navigate directly to needed content.\n",{"name":5,"description":24,"allowed-tools":25},"Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.\n","Read Write Grep Glob Bash","main","b1e46a5b01665a6910c6cfc503880b3156429f73",".jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review",0,"https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle","https:\u002F\u002Fboucle.dev","https:\u002F\u002Fgithub.com\u002Fankaboot-source","https:\u002F\u002Fwww.ankaboot.io\u002F","customer-engagement tech · privacy by design","2026-11-14 05:53:11",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ankaboot-source\u002Fboucle --skill differential-review",{"tool":42,"command":43},"bunx","bunx skills add ankaboot-source\u002Fboucle --skill differential-review",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ankaboot-source\u002Fboucle --skill differential-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002FSKILL.md",true,[50,56,60,64],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"adversarial.md","REFERENCE","参考文档",5062,"https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002Fadversarial.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"methodology.md",6738,"https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002Fmethodology.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"patterns.md",6999,"https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002Fpatterns.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"reporting.md",7006,"https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Ftrailofbits\u002Fdifferential-review\u002Freporting.md",[69,77,84,92,101,108],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79PEWFFK2Z3D0MB2681C6P7","boucle","The boucle protocol — the labels, markers, state machine and handoff rules a\nboucle loop speaks. Use when interacting with a boucle loop on any consumer\nrepository: reading or writing boucle:* labels, emitting or parsing\n\u003C!-- boucle:* --> markers, posting a SHA-anchored verdict, driving an issue\nthrough triage\u002Fworker\u002Freviewer\u002Fe2e, or answering \"what is this loop waiting\non\". Runtime-agnostic and forge-agnostic (GitLab and GitHub).","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79PEN7B3R3TJ19FZFZHTGPW","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79PEE1ZRT65Z4AW0N7X9D3C","web-design-guidelines","Web platform design and accessibility guidelines. Use when building web interfaces, auditing accessibility, implementing responsive layouts, or reviewing web UI code. Triggers on tasks involving HTML, CSS, web components, WCAG compliance, responsive design, or web performance.","MIT","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79PE7NFMZCVF5BQ7CNHP73Y","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M79PE4AYTMSWM8C35RQ780YK","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M79PE17KCVNPPFRDW5BN76PW","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fankaboot-source\u002Fboucle\u002Fblob\u002Fmain\u002F.jcode\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[]]