[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6CXW2RFJPHKFK8TA4B978":3,"skill-same:01M6H6CXW2RFJPHKFK8TA4B978":82},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M6H6CXW2RFJPHKFK8TA4B978","m07-concurrency",null,"CRITICAL: Use for concurrency\u002Fasync. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"concurrency","m07 concurrency","await","sync","thread","for","threads","atomic","tokio","condition","false","critical","triggers","async","use","channel","spawn","mutex","2026-11-10 10:12:30",false,"---\nname: m07-concurrency\ndescription: \"CRITICAL: Use for concurrency\u002Fasync. Triggers: E0277 Send Sync, cannot be sent between threads, thread, spawn, channel, mpsc, Mutex, RwLock, Atomic, async, await, Future, tokio, deadlock, race condition, 并发, 线程, 异步, 死锁\"\nuser-invocable: false\n---\n\n# Concurrency\n\n> **Layer 1: Language Mechanics**\n\n## Core Question\n\n**Is this CPU-bound or I\u002FO-bound, and what's the sharing model?**\n\nBefore choosing concurrency primitives:\n- What's the workload type?\n- What data needs to be shared?\n- What's the thread safety requirement?\n\n---\n\n## Error → Design Question\n\n| Error | Don't Just Say | Ask Instead |\n|-------|----------------|-------------|\n| E0277 Send | \"Add Send bound\" | Should this type cross threads? |\n| E0277 Sync | \"Wrap in Mutex\" | Is shared access really needed? |\n| Future not Send | \"Use spawn_local\" | Is async the right choice? |\n| Deadlock | \"Reorder locks\" | Is the locking design correct? |\n\n---\n\n## Thinking Prompt\n\nBefore adding concurrency:\n\n1. **What's the workload?**\n   - CPU-bound → threads (std::thread, rayon)\n   - I\u002FO-bound → async (tokio, async-std)\n   - Mixed → hybrid approach\n\n2. **What's the sharing model?**\n   - No sharing → message passing (channels)\n   - Immutable sharing → Arc\u003CT>\n   - Mutable sharing → Arc\u003CMutex\u003CT>> or Arc\u003CRwLock\u003CT>>\n\n3. **What are the Send\u002FSync requirements?**\n   - Cross-thread ownership → Send\n   - Cross-thread references → Sync\n   - Single-thread async → spawn_local\n\n---\n\n## Trace Up ↑ (MANDATORY)\n\n**CRITICAL**: Don't just fix the error. Trace UP to find domain constraints.\n\n### Domain Detection Table\n\n| Context Keywords | Load Domain Skill | Key Constraint |\n|-----------------|-------------------|----------------|\n| Web API, HTTP, axum, actix, handler | **domain-web** | Handlers run on any thread |\n| 交易, 支付, trading, payment | **domain-fintech** | Audit + thread safety |\n| gRPC, kubernetes, microservice | **domain-cloud-native** | Distributed tracing |\n| CLI, terminal, clap | **domain-cli** | Usually single-thread OK |\n\n### Example: Web API + Rc Error\n\n```\n\"Rc cannot be sent between threads\" in Web API context\n    ↑ DETECT: \"Web API\" → Load domain-web\n    ↑ FIND: domain-web says \"Shared state must be thread-safe\"\n    ↑ FIND: domain-web says \"Rc in state\" is Common Mistake\n    ↓ DESIGN: Use Arc\u003CT> with State extractor\n    ↓ IMPL: axum::extract::State\u003CArc\u003CAppConfig>>\n```\n\n### Generic Trace\n\n```\n\"Send not satisfied for my type\"\n    ↑ Ask: What domain is this? Load domain-* skill\n    ↑ Ask: Does this type need to cross thread boundaries?\n    ↑ Check: m09-domain (is the data model correct?)\n```\n\n| Situation | Trace To | Question |\n|-----------|----------|----------|\n| Send\u002FSync in Web | **domain-web** | What's the state management pattern? |\n| Send\u002FSync in CLI | **domain-cli** | Is multi-thread really needed? |\n| Mutex vs channels | m09-domain | Shared state or message passing? |\n| Async vs threads | m10-performance | What's the workload profile? |\n\n---\n\n## Trace Down ↓\n\nFrom design to implementation:\n\n```\n\"Need parallelism for CPU work\"\n    ↓ Use: std::thread or rayon\n\n\"Need concurrency for I\u002FO\"\n    ↓ Use: async\u002Fawait with tokio\n\n\"Need to share immutable data across threads\"\n    ↓ Use: Arc\u003CT>\n\n\"Need to share mutable data across threads\"\n    ↓ Use: Arc\u003CMutex\u003CT>> or Arc\u003CRwLock\u003CT>>\n    ↓ Or: channels for message passing\n\n\"Need simple atomic operations\"\n    ↓ Use: AtomicBool, AtomicUsize, etc.\n```\n\n---\n\n## Send\u002FSync Markers\n\n| Marker | Meaning | Example |\n|--------|---------|---------|\n| `Send` | Can transfer ownership between threads | Most types |\n| `Sync` | Can share references between threads | `Arc\u003CT>` |\n| `!Send` | Must stay on one thread | `Rc\u003CT>` |\n| `!Sync` | No shared refs across threads | `RefCell\u003CT>` |\n\n## Quick Reference\n\n| Pattern | Thread-Safe | Blocking | Use When |\n|---------|-------------|----------|----------|\n| `std::thread` | Yes | Yes | CPU-bound parallelism |\n| `async\u002Fawait` | Yes | No | I\u002FO-bound concurrency |\n| `Mutex\u003CT>` | Yes | Yes | Shared mutable state |\n| `RwLock\u003CT>` | Yes | Yes | Read-heavy shared state |\n| `mpsc::channel` | Yes | Optional | Message passing |\n| `Arc\u003CMutex\u003CT>>` | Yes | Yes | Shared mutable across threads |\n\n## Decision Flowchart\n\n```\nWhat type of work?\n├─ CPU-bound → std::thread or rayon\n├─ I\u002FO-bound → async\u002Fawait\n└─ Mixed → hybrid (spawn_blocking)\n\nNeed to share data?\n├─ No → message passing (channels)\n├─ Immutable → Arc\u003CT>\n└─ Mutable →\n   ├─ Read-heavy → Arc\u003CRwLock\u003CT>>\n   └─ Write-heavy → Arc\u003CMutex\u003CT>>\n   └─ Simple counter → AtomicUsize\n\nAsync context?\n├─ Type is Send → tokio::spawn\n├─ Type is !Send → spawn_local\n└─ Blocking code → spawn_blocking\n```\n\n---\n\n## Common Errors\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| E0277 `Send` not satisfied | Non-Send in async | Use Arc or spawn_local |\n| E0277 `Sync` not satisfied | Non-Sync shared | Wrap with Mutex |\n| Deadlock | Lock ordering | Consistent lock order |\n| `future is not Send` | Non-Send across await | Drop before await |\n| `MutexGuard` across await | Guard held during suspend | Scope guard properly |\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why Bad | Better |\n|--------------|---------|--------|\n| Arc\u003CMutex\u003CT>> everywhere | Contention, complexity | Message passing |\n| thread::sleep in async | Blocks executor | tokio::time::sleep |\n| Holding locks across await | Blocks other tasks | Scope locks tightly |\n| Ignoring deadlock risk | Hard to debug | Lock ordering, try_lock |\n\n---\n\n## Async-Specific Patterns\n\n### Avoid MutexGuard Across Await\n\n```rust\n\u002F\u002F Bad: guard held across await\nlet guard = mutex.lock().await;\ndo_async().await;  \u002F\u002F guard still held!\n\n\u002F\u002F Good: scope the lock\n{\n    let guard = mutex.lock().await;\n    \u002F\u002F use guard\n}  \u002F\u002F guard dropped\ndo_async().await;\n```\n\n### Non-Send Types in Async\n\n```rust\n\u002F\u002F Rc is !Send, can't cross await in spawned task\n\u002F\u002F Option 1: use Arc instead\n\u002F\u002F Option 2: use spawn_local (single-thread runtime)\n\u002F\u002F Option 3: ensure Rc is dropped before .await\n```\n\n---\n\n## Related Skills\n\n| When | See |\n|------|-----|\n| Smart pointer choice | m02-resource |\n| Interior mutability | m03-mutability |\n| Performance tuning | m10-performance |\n| Domain concurrency needs | domain-* |\n","# Concurrency\n\n> **Layer 1: Language Mechanics**\n\n## Core Question\n\n**Is this CPU-bound or I\u002FO-bound, and what's the sharing model?**\n\nBefore choosing concurrency primitives:\n- What's the workload type?\n- What data needs to be shared?\n- What's the thread safety requirement?\n\n---\n\n## Error → Design Question\n\n| Error | Don't Just Say | Ask Instead |\n|-------|----------------|-------------|\n| E0277 Send | \"Add Send bound\" | Should this type cross threads? |\n| E0277 Sync | \"Wrap in Mutex\" | Is shared access really needed? |\n| Future not Send | \"Use spawn_local\" | Is async the right choice? |\n| Deadlock | \"Reorder locks\" | Is the locking design correct? |\n\n---\n\n## Thinking Prompt\n\nBefore adding concurrency:\n\n1. **What's the workload?**\n   - CPU-bound → threads (std::thread, rayon)\n   - I\u002FO-bound → async (tokio, async-std)\n   - Mixed → hybrid approach\n\n2. **What's the sharing model?**\n   - No sharing → message passing (channels)\n   - Immutable sharing → Arc\u003CT>\n   - Mutable sharing → Arc\u003CMutex\u003CT>> or Arc\u003CRwLock\u003CT>>\n\n3. **What are the Send\u002FSync requirements?**\n   - Cross-thread ownership → Send\n   - Cross-thread references → Sync\n   - Single-thread async → spawn_local\n\n---\n\n## Trace Up ↑ (MANDATORY)\n\n**CRITICAL**: Don't just fix the error. Trace UP to find domain constraints.\n\n### Domain Detection Table\n\n| Context Keywords | Load Domain Skill | Key Constraint |\n|-----------------|-------------------|----------------|\n| Web API, HTTP, axum, actix, handler | **domain-web** | Handlers run on any thread |\n| 交易, 支付, trading, payment | **domain-fintech** | Audit + thread safety |\n| gRPC, kubernetes, microservice | **domain-cloud-native** | Distributed tracing |\n| CLI, terminal, clap | **domain-cli** | Usually single-thread OK |\n\n### Example: Web API + Rc Error\n\n```\n\"Rc cannot be sent between threads\" in Web API context\n    ↑ DETECT: \"Web API\" → Load domain-web\n    ↑ FIND: domain-web says \"Shared state must be thread-safe\"\n    ↑ FIND: domain-web says \"Rc in state\" is Common Mistake\n    ↓ DESIGN: Use Arc\u003CT> with State extractor\n    ↓ IMPL: axum::extract::State\u003CArc\u003CAppConfig>>\n```\n\n### Generic Trace\n\n```\n\"Send not satisfied for my type\"\n    ↑ Ask: What domain is this? Load domain-* skill\n    ↑ Ask: Does this type need to cross thread boundaries?\n    ↑ Check: m09-domain (is the data model correct?)\n```\n\n| Situation | Trace To | Question |\n|-----------|----------|----------|\n| Send\u002FSync in Web | **domain-web** | What's the state management pattern? |\n| Send\u002FSync in CLI | **domain-cli** | Is multi-thread really needed? |\n| Mutex vs channels | m09-domain | Shared state or message passing? |\n| Async vs threads | m10-performance | What's the workload profile? |\n\n---\n\n## Trace Down ↓\n\nFrom design to implementation:\n\n```\n\"Need parallelism for CPU work\"\n    ↓ Use: std::thread or rayon\n\n\"Need concurrency for I\u002FO\"\n    ↓ Use: async\u002Fawait with tokio\n\n\"Need to share immutable data across threads\"\n    ↓ Use: Arc\u003CT>\n\n\"Need to share mutable data across threads\"\n    ↓ Use: Arc\u003CMutex\u003CT>> or Arc\u003CRwLock\u003CT>>\n    ↓ Or: channels for message passing\n\n\"Need simple atomic operations\"\n    ↓ Use: AtomicBool, AtomicUsize, etc.\n```\n\n---\n\n## Send\u002FSync Markers\n\n| Marker | Meaning | Example |\n|--------|---------|---------|\n| `Send` | Can transfer ownership between threads | Most types |\n| `Sync` | Can share references between threads | `Arc\u003CT>` |\n| `!Send` | Must stay on one thread | `Rc\u003CT>` |\n| `!Sync` | No shared refs across threads | `RefCell\u003CT>` |\n\n## Quick Reference\n\n| Pattern | Thread-Safe | Blocking | Use When |\n|---------|-------------|----------|----------|\n| `std::thread` | Yes | Yes | CPU-bound parallelism |\n| `async\u002Fawait` | Yes | No | I\u002FO-bound concurrency |\n| `Mutex\u003CT>` | Yes | Yes | Shared mutable state |\n| `RwLock\u003CT>` | Yes | Yes | Read-heavy shared state |\n| `mpsc::channel` | Yes | Optional | Message passing |\n| `Arc\u003CMutex\u003CT>>` | Yes | Yes | Shared mutable across threads |\n\n## Decision Flowchart\n\n```\nWhat type of work?\n├─ CPU-bound → std::thread or rayon\n├─ I\u002FO-bound → async\u002Fawait\n└─ Mixed → hybrid (spawn_blocking)\n\nNeed to share data?\n├─ No → message passing (channels)\n├─ Immutable → Arc\u003CT>\n└─ Mutable →\n   ├─ Read-heavy → Arc\u003CRwLock\u003CT>>\n   └─ Write-heavy → Arc\u003CMutex\u003CT>>\n   └─ Simple counter → AtomicUsize\n\nAsync context?\n├─ Type is Send → tokio::spawn\n├─ Type is !Send → spawn_local\n└─ Blocking code → spawn_blocking\n```\n\n---\n\n## Common Errors\n\n| Error | Cause | Fix |\n|-------|-------|-----|\n| E0277 `Send` not satisfied | Non-Send in async | Use Arc or spawn_local |\n| E0277 `Sync` not satisfied | Non-Sync shared | Wrap with Mutex |\n| Deadlock | Lock ordering | Consistent lock order |\n| `future is not Send` | Non-Send across await | Drop before await |\n| `MutexGuard` across await | Guard held during suspend | Scope guard properly |\n\n---\n\n## Anti-Patterns\n\n| Anti-Pattern | Why Bad | Better |\n|--------------|---------|--------|\n| Arc\u003CMutex\u003CT>> everywhere | Contention, complexity | Message passing |\n| thread::sleep in async | Blocks executor | tokio::time::sleep |\n| Holding locks across await | Blocks other tasks | Scope locks tightly |\n| Ignoring deadlock risk | Hard to debug | Lock ordering, try_lock |\n\n---\n\n## Async-Specific Patterns\n\n### Avoid MutexGuard Across Await\n\n```rust\n\u002F\u002F Bad: guard held across await\nlet guard = mutex.lock().await;\ndo_async().await;  \u002F\u002F guard still held!\n\n\u002F\u002F Good: scope the lock\n{\n    let guard = mutex.lock().await;\n    \u002F\u002F use guard\n}  \u002F\u002F guard dropped\ndo_async().await;\n```\n\n### Non-Send Types in Async\n\n```rust\n\u002F\u002F Rc is !Send, can't cross await in spawned task\n\u002F\u002F Option 1: use Arc instead\n\u002F\u002F Option 2: use spawn_local (single-thread runtime)\n\u002F\u002F Option 3: ensure Rc is dropped before .await\n```\n\n---\n\n## Related Skills\n\n| When | See |\n|------|-----|\n| Smart pointer choice | m02-resource |\n| Interior mutability | m03-mutability |\n| Performance tuning | m10-performance |\n| Domain concurrency needs | domain-* |\n",{"name":5,"description":7,"user-invocable":38},"main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","archive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill m07-concurrency",{"tool":56,"command":57},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill m07-concurrency",{"tool":59,"command":60},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill m07-concurrency","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002FSKILL.md",true,[64,70,74,78],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"comparison.md","REFERENCE","参考文档",7436,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002Fcomparison.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"examples\u002Fthread-patterns.md",8291,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002Fexamples\u002Fthread-patterns.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"patterns\u002Fasync-patterns.md",8263,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002Fpatterns\u002Fasync-patterns.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"patterns\u002Fcommon-errors.md",6568,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fchasebuild-agent-skills\u002Frust\u002Fskills\u002Fm07-concurrency\u002Fpatterns\u002Fcommon-errors.md",[83,114,132,142,168,195],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":94,"publishedAt":37},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[95,96,97,98,99,100,101,31,102,103,104,105,106,107,108,109,110,111,112,113],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":37},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[121,122,123,124,125,126,127,128,129,24,130,131],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":37},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[139,121,140,126,141],"super swarm spark","spark","commands",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":37},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","codex","files",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":37},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000023","Skill与智能体开发",[178,179,180,108,181,182,183,184,24,185,186,187,188,189,190,33,191,192,193,194],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":196,"name":123,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":37},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[123,201,24,26,202,203,31,128,141,204,205,33,206,207,208,209,210,164,100,211],"outline","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]