[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EZX9R5M4TG4QFN98C2Q7MS":3,"skill-same:01M6EZX9R5M4TG4QFN98C2Q7MS":129},{"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":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":6,"ownerHtmlUrl":62,"ownerBlogUrl":6,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6EZX9R5M4TG4QFN98C2Q7MS","speckit",null,"Specification-Driven Development (SDD) toolkit. Transforms ideas into executable specifications, implementation plans, and task lists. Use for feature planning, PRD creation, or when user invokes \u002Fspeckit.specify, \u002Fspeckit.plan, \u002Fspeckit.tasks commands.","luokai0\u002Fai-agent-skills-by-luo-kai","luokai0","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F266954973?v=4","01M6E16VNT42JB8B3X3254QWJ7","luo kai","01M6E16VTFVP6S5XJF1V1MPV90",14,"MIT","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"task","transforms","feature planning","plans","feature","creation","commands","sdd","ideas","tasks","specification","use","context","command","plan","specify","planning","toolkit","development","2026-11-10 10:12:30",false,"---\nname: speckit\ndescription: Specification-Driven Development (SDD) toolkit. Transforms ideas into executable specifications, implementation plans, and task lists. Use for feature planning, PRD creation, or when user invokes \u002Fspeckit.specify, \u002Fspeckit.plan, \u002Fspeckit.tasks commands.\nlicense: MIT\ngovernance_phases: [frame, shape]\norgan_affinity: [organ-iv]\ntriggers: [user-asks-about-specifications, command:speckit, context:specification]\n---\n\n# Spec Kit: Specification-Driven Development\n\n## Overview\n\nSpec Kit implements **Specification-Driven Development (SDD)** - a methodology where specifications drive code, not vice versa. Instead of specs serving as documentation for code, code becomes the expression of specifications.\n\n### The Power Inversion\n\nTraditional development: Code is truth, specs are scaffolding\n**SDD**: Specifications are truth, code is generated output\n\nThis eliminates the gap between intent and implementation by making specifications executable through AI.\n\n## Commands\n\n### `\u002Fspeckit.specify \u003Cfeature-description>`\n\nCreates a comprehensive feature specification from a natural language description.\n\n**Usage**: `\u002Fspeckit.specify Real-time chat with message history and presence`\n\n**Output**:\n- `specs\u002F{feature-name}\u002Fspec.md` - Complete feature specification\n- `specs\u002F{feature-name}\u002Fchecklists\u002Frequirements.md` - Quality validation checklist\n\n**Process**:\n1. Parse user description, extract key concepts (actors, actions, data, constraints)\n2. Generate user scenarios with prioritized stories (P1, P2, P3)\n3. Define functional requirements (FR-001, FR-002, etc.)\n4. Create measurable success criteria\n5. Identify key entities\n6. Validate against quality checklist\n7. Present clarification questions (max 3) if critical ambiguities exist\n\n**Guidelines**:\n- Focus on WHAT users need and WHY\n- Avoid HOW (no tech stack, APIs, code structure)\n- Make informed guesses using industry standards\n- Limit `[NEEDS CLARIFICATION]` markers to 3 maximum\n- Every requirement must be testable\n\nFor detailed template: read `assets\u002Ftemplates\u002Fspec-template.md`\nFor command details: read `references\u002Fcommands\u002Fspecify.md`\n\n---\n\n### `\u002Fspeckit.plan [tech-context]`\n\nCreates an implementation plan from an existing specification.\n\n**Usage**: `\u002Fspeckit.plan WebSocket, PostgreSQL, Redis` or `\u002Fspeckit.plan` (will determine tech from context)\n\n**Prerequisites**: `spec.md` must exist in the feature directory\n\n**Output**:\n- `specs\u002F{feature}\u002Fplan.md` - Implementation plan with tech decisions\n- `specs\u002F{feature}\u002Fresearch.md` - Technology research and decisions\n- `specs\u002F{feature}\u002Fdata-model.md` - Entity definitions\n- `specs\u002F{feature}\u002Fcontracts\u002F` - API specifications (OpenAPI\u002FGraphQL)\n- `specs\u002F{feature}\u002Fquickstart.md` - Validation scenarios\n\n**Process**:\n1. Load feature specification and project constitution\n2. Fill Technical Context section\n3. Run Constitution Check (evaluate architectural gates)\n4. Phase 0: Research unknowns, generate `research.md`\n5. Phase 1: Design data models, generate contracts\n6. Re-evaluate constitution compliance post-design\n\n**Constitution Gates** (if using constitution):\n- Simplicity Gate: Using ≤3 projects? No future-proofing?\n- Anti-Abstraction Gate: Using framework directly?\n- Integration-First Gate: Contracts defined?\n\nFor detailed template: read `assets\u002Ftemplates\u002Fplan-template.md`\nFor command details: read `references\u002Fcommands\u002Fplan.md`\n\n---\n\n### `\u002Fspeckit.tasks`\n\nGenerates an executable task list from the implementation plan.\n\n**Usage**: `\u002Fspeckit.tasks`\n\n**Prerequisites**: `plan.md` and `spec.md` must exist\n\n**Output**:\n- `specs\u002F{feature}\u002Ftasks.md` - Dependency-ordered task list\n\n**Process**:\n1. Load plan.md (tech stack, structure) and spec.md (user stories)\n2. Optionally load: data-model.md, contracts\u002F, research.md\n3. Generate tasks organized by user story:\n   - Phase 1: Setup (shared infrastructure)\n   - Phase 2: Foundational (blocking prerequisites)\n   - Phase 3+: User Stories in priority order (P1, P2, P3...)\n   - Final Phase: Polish & cross-cutting\n4. Mark parallelizable tasks with `[P]`\n5. Number tasks (T001, T002...)\n6. Generate dependency graph and parallel execution examples\n\n**Task Format**: `[ID] [P?] [Story] Description`\n- `[P]` = Can run in parallel (different files, no dependencies)\n- `[Story]` = Which user story (US1, US2, US3)\n\nFor detailed template: read `assets\u002Ftemplates\u002Ftasks-template.md`\nFor command details: read `references\u002Fcommands\u002Ftasks.md`\n\n---\n\n## Workflow Example\n\n```bash\n# 1. Create specification (5 min)\n\u002Fspeckit.specify Real-time chat with message history and user presence\n\n# 2. Generate implementation plan (5 min)\n\u002Fspeckit.plan WebSocket for messaging, PostgreSQL for history, Redis for presence\n\n# 3. Create task list (5 min)\n\u002Fspeckit.tasks\n```\n\n**Result** (in 15 minutes):\n- Complete feature spec with user stories and acceptance criteria\n- Detailed implementation plan with technology rationale\n- API contracts and data models\n- Executable task list organized by user story\n\n## Project Constitution\n\nA constitution defines immutable architectural principles for a project. When present at `memory\u002Fconstitution.md`, the `\u002Fspeckit.plan` command will:\n\n1. Validate against constitutional gates before planning\n2. Require justification for any violations\n3. Track complexity deviations\n\n**Sample principles**:\n- Library-First: Features start as standalone libraries\n- Test-First: TDD mandatory (Red-Green-Refactor)\n- Simplicity: Maximum 3 projects, YAGNI\n- Integration-First: Real databases over mocks\n\nFor constitution template: read `assets\u002Ftemplates\u002Fconstitution-template.md`\n\n## Key Concepts\n\n### User Story Organization\n\nTasks are grouped by user story to enable:\n- Independent implementation\n- Independent testing\n- Incremental delivery (ship P1, then P2, then P3)\n\n### MVP-First Delivery\n\n1. Complete Setup + Foundational phases\n2. Implement User Story 1 (P1) → Test → Deploy\n3. Add User Story 2 (P2) → Test → Deploy\n4. Continue incrementally\n\n### Template-Driven Quality\n\nTemplates constrain AI behavior for better outcomes:\n- Prevent premature implementation details\n- Force explicit uncertainty markers\n- Enforce test-first thinking\n- Prevent speculative features\n\n## File Locations\n\nWhen working in a project:\n- Specifications: `specs\u002F{feature-name}\u002F`\n- Constitution: `memory\u002Fconstitution.md`\n\n## Reference Files\n\n### Templates (fill-in artifacts for output)\n\n- `assets\u002Ftemplates\u002Fspec-template.md` - Feature specification template\n- `assets\u002Ftemplates\u002Fplan-template.md` - Implementation plan template\n- `assets\u002Ftemplates\u002Ftasks-template.md` - Task list template\n- `assets\u002Ftemplates\u002Fconstitution-template.md` - Project constitution template\n\n### Documentation (methodology and command details)\n\n- `references\u002Fmethodology.md` - Full SDD philosophy document\n- `references\u002Fcommands\u002Fspecify.md` - `\u002Fspeckit.specify` command definition\n- `references\u002Fcommands\u002Fplan.md` - `\u002Fspeckit.plan` command definition\n- `references\u002Fcommands\u002Ftasks.md` - `\u002Fspeckit.tasks` command definition\n","# Spec Kit: Specification-Driven Development\n\n## Overview\n\nSpec Kit implements **Specification-Driven Development (SDD)** - a methodology where specifications drive code, not vice versa. Instead of specs serving as documentation for code, code becomes the expression of specifications.\n\n### The Power Inversion\n\nTraditional development: Code is truth, specs are scaffolding\n**SDD**: Specifications are truth, code is generated output\n\nThis eliminates the gap between intent and implementation by making specifications executable through AI.\n\n## Commands\n\n### `\u002Fspeckit.specify \u003Cfeature-description>`\n\nCreates a comprehensive feature specification from a natural language description.\n\n**Usage**: `\u002Fspeckit.specify Real-time chat with message history and presence`\n\n**Output**:\n- `specs\u002F{feature-name}\u002Fspec.md` - Complete feature specification\n- `specs\u002F{feature-name}\u002Fchecklists\u002Frequirements.md` - Quality validation checklist\n\n**Process**:\n1. Parse user description, extract key concepts (actors, actions, data, constraints)\n2. Generate user scenarios with prioritized stories (P1, P2, P3)\n3. Define functional requirements (FR-001, FR-002, etc.)\n4. Create measurable success criteria\n5. Identify key entities\n6. Validate against quality checklist\n7. Present clarification questions (max 3) if critical ambiguities exist\n\n**Guidelines**:\n- Focus on WHAT users need and WHY\n- Avoid HOW (no tech stack, APIs, code structure)\n- Make informed guesses using industry standards\n- Limit `[NEEDS CLARIFICATION]` markers to 3 maximum\n- Every requirement must be testable\n\nFor detailed template: read `assets\u002Ftemplates\u002Fspec-template.md`\nFor command details: read `references\u002Fcommands\u002Fspecify.md`\n\n---\n\n### `\u002Fspeckit.plan [tech-context]`\n\nCreates an implementation plan from an existing specification.\n\n**Usage**: `\u002Fspeckit.plan WebSocket, PostgreSQL, Redis` or `\u002Fspeckit.plan` (will determine tech from context)\n\n**Prerequisites**: `spec.md` must exist in the feature directory\n\n**Output**:\n- `specs\u002F{feature}\u002Fplan.md` - Implementation plan with tech decisions\n- `specs\u002F{feature}\u002Fresearch.md` - Technology research and decisions\n- `specs\u002F{feature}\u002Fdata-model.md` - Entity definitions\n- `specs\u002F{feature}\u002Fcontracts\u002F` - API specifications (OpenAPI\u002FGraphQL)\n- `specs\u002F{feature}\u002Fquickstart.md` - Validation scenarios\n\n**Process**:\n1. Load feature specification and project constitution\n2. Fill Technical Context section\n3. Run Constitution Check (evaluate architectural gates)\n4. Phase 0: Research unknowns, generate `research.md`\n5. Phase 1: Design data models, generate contracts\n6. Re-evaluate constitution compliance post-design\n\n**Constitution Gates** (if using constitution):\n- Simplicity Gate: Using ≤3 projects? No future-proofing?\n- Anti-Abstraction Gate: Using framework directly?\n- Integration-First Gate: Contracts defined?\n\nFor detailed template: read `assets\u002Ftemplates\u002Fplan-template.md`\nFor command details: read `references\u002Fcommands\u002Fplan.md`\n\n---\n\n### `\u002Fspeckit.tasks`\n\nGenerates an executable task list from the implementation plan.\n\n**Usage**: `\u002Fspeckit.tasks`\n\n**Prerequisites**: `plan.md` and `spec.md` must exist\n\n**Output**:\n- `specs\u002F{feature}\u002Ftasks.md` - Dependency-ordered task list\n\n**Process**:\n1. Load plan.md (tech stack, structure) and spec.md (user stories)\n2. Optionally load: data-model.md, contracts\u002F, research.md\n3. Generate tasks organized by user story:\n   - Phase 1: Setup (shared infrastructure)\n   - Phase 2: Foundational (blocking prerequisites)\n   - Phase 3+: User Stories in priority order (P1, P2, P3...)\n   - Final Phase: Polish & cross-cutting\n4. Mark parallelizable tasks with `[P]`\n5. Number tasks (T001, T002...)\n6. Generate dependency graph and parallel execution examples\n\n**Task Format**: `[ID] [P?] [Story] Description`\n- `[P]` = Can run in parallel (different files, no dependencies)\n- `[Story]` = Which user story (US1, US2, US3)\n\nFor detailed template: read `assets\u002Ftemplates\u002Ftasks-template.md`\nFor command details: read `references\u002Fcommands\u002Ftasks.md`\n\n---\n\n## Workflow Example\n\n```bash\n# 1. Create specification (5 min)\n\u002Fspeckit.specify Real-time chat with message history and user presence\n\n# 2. Generate implementation plan (5 min)\n\u002Fspeckit.plan WebSocket for messaging, PostgreSQL for history, Redis for presence\n\n# 3. Create task list (5 min)\n\u002Fspeckit.tasks\n```\n\n**Result** (in 15 minutes):\n- Complete feature spec with user stories and acceptance criteria\n- Detailed implementation plan with technology rationale\n- API contracts and data models\n- Executable task list organized by user story\n\n## Project Constitution\n\nA constitution defines immutable architectural principles for a project. When present at `memory\u002Fconstitution.md`, the `\u002Fspeckit.plan` command will:\n\n1. Validate against constitutional gates before planning\n2. Require justification for any violations\n3. Track complexity deviations\n\n**Sample principles**:\n- Library-First: Features start as standalone libraries\n- Test-First: TDD mandatory (Red-Green-Refactor)\n- Simplicity: Maximum 3 projects, YAGNI\n- Integration-First: Real databases over mocks\n\nFor constitution template: read `assets\u002Ftemplates\u002Fconstitution-template.md`\n\n## Key Concepts\n\n### User Story Organization\n\nTasks are grouped by user story to enable:\n- Independent implementation\n- Independent testing\n- Incremental delivery (ship P1, then P2, then P3)\n\n### MVP-First Delivery\n\n1. Complete Setup + Foundational phases\n2. Implement User Story 1 (P1) → Test → Deploy\n3. Add User Story 2 (P2) → Test → Deploy\n4. Continue incrementally\n\n### Template-Driven Quality\n\nTemplates constrain AI behavior for better outcomes:\n- Prevent premature implementation details\n- Force explicit uncertainty markers\n- Enforce test-first thinking\n- Prevent speculative features\n\n## File Locations\n\nWhen working in a project:\n- Specifications: `specs\u002F{feature-name}\u002F`\n- Constitution: `memory\u002Fconstitution.md`\n\n## Reference Files\n\n### Templates (fill-in artifacts for output)\n\n- `assets\u002Ftemplates\u002Fspec-template.md` - Feature specification template\n- `assets\u002Ftemplates\u002Fplan-template.md` - Implementation plan template\n- `assets\u002Ftemplates\u002Ftasks-template.md` - Task list template\n- `assets\u002Ftemplates\u002Fconstitution-template.md` - Project constitution template\n\n### Documentation (methodology and command details)\n\n- `references\u002Fmethodology.md` - Full SDD philosophy document\n- `references\u002Fcommands\u002Fspecify.md` - `\u002Fspeckit.specify` command definition\n- `references\u002Fcommands\u002Fplan.md` - `\u002Fspeckit.plan` command definition\n- `references\u002Fcommands\u002Ftasks.md` - `\u002Fspeckit.tasks` command definition\n",{"name":5,"license":15,"triggers":48,"description":7,"organ_affinity":52,"governance_phases":54},[49,50,51],"user-asks-about-specifications","command:speckit","context:specification",[53],"organ-iv",[55,56],"frame","shape","main","4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c","ai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit",1,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai","https:\u002F\u002Fgithub.com\u002Fluokai0","a solo builder.","2026-05-06 04:29:04",{"source":8,"skillName":5,"commands":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill speckit",{"tool":71,"command":72},"bunx","bunx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill speckit",{"tool":74,"command":75},"pnpm","pnpm dlx skills add luokai0\u002Fai-agent-skills-by-luo-kai --skill speckit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002FSKILL.md",true,[79,85,89,93,97,103,107,111,115,119,125],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"assets\u002Ftemplates\u002Fconstitution-template.md","ASSET","资产文件",2345,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fassets\u002Ftemplates\u002Fconstitution-template.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"assets\u002Ftemplates\u002Fplan-template.md",3651,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fassets\u002Ftemplates\u002Fplan-template.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Ftemplates\u002Fspec-template.md",3960,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fassets\u002Ftemplates\u002Fspec-template.md",{"path":94,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Ftemplates\u002Ftasks-template.md",9174,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fassets\u002Ftemplates\u002Ftasks-template.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fcommands\u002Fplan.md","REFERENCE","参考文档",3824,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Freferences\u002Fcommands\u002Fplan.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fcommands\u002Fspecify.md",4466,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Freferences\u002Fcommands\u002Fspecify.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fcommands\u002Ftasks.md",4855,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Freferences\u002Fcommands\u002Ftasks.md",{"path":112,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fmethodology.md",25311,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Freferences\u002Fmethodology.md",{"path":116,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fworkflow-integration.md",7272,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Freferences\u002Fworkflow-integration.md",{"path":120,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Finit_spec_dir.py","SCRIPT","脚本",3930,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fscripts\u002Finit_spec_dir.py",{"path":126,"resourceType":121,"resourceTypeDesc":122,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fvalidate_spec.py",6352,"https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F21-external-registries\u002F18-organvm-skills\u002Ftools\u002Fspeckit\u002Fscripts\u002Fvalidate_spec.py",[130,157,174,202,234,269],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":43},"01M6F2SKTE208174C7S7JJCZC7","write-contracts","Generates secure Aptos Move V2 smart contracts with Object model, Digital Asset integration, security patterns, and storage type guidance. Includes comprehensive storage decision framework for optimal data structure selection. Triggers on: 'write contract', 'create NFT collection', 'build marketplace', 'implement minting', 'generate Move module', 'create token contract', 'build DAO', 'implement staking'. Ask storage questions when: 'store', 'track', 'registry', 'mapping', 'list', 'collection'.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fwrite-contracts\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154,155,156],"write","contracts","write contracts","storage","secure","create","generate","collection","model","decision","ask","smart-contracts","selection","objects","structure","nft","token","aptos","critical","move",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":43},"01M6F2RFXJ6T9MKW0A7N7GM45B","web-search","通用网络搜索技能，支持多引擎搜索（百度、必应、DuckDuckGo），无需API密钥即可获取实时信息","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fweb-search-ex-skill\u002FSKILL.md",[],[164,165,166,167,168,169,170,171,172,173],"web","search","web search","搜索","baidu","bing","duckduckgo","百度","多引擎","internet",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":185,"publishedAt":43},"01M6F2K968G1FZEZFPW2E6B222","solo-build","Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says \"build it\", \"start building\", \"execute plan\", \"implement tasks\", \"ship it\", or references a track ID. Do NOT use for planning (use \u002Fplan) or scaffolding (use \u002Fscaffold).","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fsolo-build\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[186,187,188,189,190,191,33,192,165,193,38,194,137,195,196,197,198,199,200,201],"build","solo","solo build","MCP","workflow","commit","code","Bash","read","auto","references","context7","query","scaffolding","ship it","project",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":214,"publishedAt":43},"01M6F2GKN39SGHSPWYB3662YC8","react-email","Use when building HTML email templates with React components, adding a visual email editor to an application using the React Email visual editor, rendering emails to HTML, or sending emails with Resend. Covers welcome emails, password resets, notifications, order confirmations, newsletters, transactional emails, and the embeddable email editor component.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Freact-email-skills\u002FSKILL.md",[208,211],{"categoryNo":209,"categoryName":210,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":212,"categoryName":213,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000009","前端开发",[215,216,217,218,219,220,221,222,223,224,225,226,227,35,228,229,230,231,232,233],"react","email","react email","github","editor","components","react components","component","welcome","https","notifications","password","node","html","resend","visual","emails","rendering","with",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":250,"publishedAt":43},"01M6F2FBVGVDFSG8SSFJGXA40C","APITester Agent-Driven API Testing","Test API endpoints and document responses. Define tests in plain English, run them, get formatted results. Agent-driven Postman alternative.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fopenclaw-api-tester\u002FSKILL.md",[240,243,246,247],{"categoryNo":241,"categoryName":242,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":244,"categoryName":245,"taxonomyType":183,"taxonomyTypeDesc":184},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":181,"categoryName":182,"taxonomyType":183,"taxonomyTypeDesc":184},{"categoryNo":248,"categoryName":249,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[251,252,253,254,255,256,257,258,259,260,261,262,263,264,265,266,267,268],"testing","api","api testing","driven","APITester Agent Driven API Testing","test","run","postman","results","plain english","tester","endpoints","document","get","define","tests","english","api-tester",{"skillNo":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":273,"categories":274,"keywords":275,"publishedAt":43},"01M6F273Y3NGAPVJZ608BC0G9G","hubspot-implementation-plan","Generate a phased implementation plan from a HubSpot audit report. Creates prioritized, sequenced cleanup processes with effort estimates, dependencies, and automation feasibility. Use after running \u002Fhubspot-audit.","https:\u002F\u002Fgithub.com\u002Fluokai0\u002Fai-agent-skills-by-luo-kai\u002Fblob\u002Fmain\u002Fai-agent-skills\u002F22-clawhub-skills\u002Fhubspot-implementation-plan\u002FSKILL.md",[],[38,276,277,278,279,280,281,143,40,282,283,284,285,35,286,287,233,288],"implementation","hubspot","hubspot implementation plan","automation","feasibility","cleanup","report","audit","audit report","phased implementation","dependencies","processes","hubspot audit"]