[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CX2FNARK0TP4VSKC14CY4X":3,"skill-same:01M6CX2FNARK0TP4VSKC14CY4X":63},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":62},"01M6CX2FNARK0TP4VSKC14CY4X","dot-ai-prd-create",null,"Create documentation-first PRDs that guide development through user-facing content","vfarcic\u002Fdot-ai-headlamp","vfarcic","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5716227?v=4","01M6C41XBA7GK0NJG2D4GV11SC","Viktor Farcic","01M6CX1QQ81N9D052KA5HJE8YS",3,"MIT","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-prd-create\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34],"create","prd","dot","dot ai prd create","dot ai","documentation","development","content","first","user","guide","2026-11-10 10:12:30",false,"---\nname: dot-ai-prd-create\ndescription: Create documentation-first PRDs that guide development through user-facing content\nuser-invocable: true\n---\n\n# PRD Creation Slash Command\n\n## Instructions\n\nYou are helping create a Product Requirements Document (PRD) for a new feature. This process involves two main components:\n\n1. **GitHub Issue**: Short, immutable concept description that links to the detailed PRD\n2. **PRD File**: Project management document with milestone tracking and implementation plan\n\n## Process\n\n### Step 1: Understand the Feature Concept\nAsk the user to describe the feature idea to understand the core concept and scope.\n\n### Step 2: Create GitHub Issue FIRST\nCreate the GitHub issue immediately to get the issue ID. This ID is required for proper PRD file naming.\n\n**IMPORTANT: Add the \"PRD\" label to the issue for discoverability.**\n\n### Step 3: Create PRD File with Correct Naming\nCreate the PRD file using the actual GitHub issue ID: `prds\u002F[issue-id]-[feature-name].md`\n\n### Step 4: Update GitHub Issue with PRD Link\nAdd the PRD file link to the GitHub issue description now that the filename is known.\n\n### Step 5: Create PRD as a Project Management Document\nWork through the PRD template focusing on project management, milestone tracking, and implementation planning. Documentation updates should be included as part of the implementation milestones.\n\n**Key Principle**: Focus on 5-10 major milestones rather than exhaustive task lists. Each milestone should represent meaningful progress that can be clearly validated.\n\n**Consider Including** (when applicable to the project\u002Ffeature):\n- **Tests** - If the project has tests, include a milestone for test coverage of new functionality\n- **Documentation** - If the feature is user-facing, include a milestone for docs following existing project patterns\n\n**Good Milestones Examples:**\n- [ ] Core functionality implemented and working\n- [ ] Tests passing for new functionality (if project has test suite)\n- [ ] Documentation complete following existing patterns (if user-facing feature)\n- [ ] Integration with existing systems working\n- [ ] Feature ready for user testing\n\n**Avoid Micro-Tasks:**\n- ❌ Update README.md file\n- ❌ Write test for function X\n- ❌ Fix typo in documentation\n- ❌ Individual file modifications\n\n**Milestone Characteristics:**\n- **Meaningful**: Represents significant progress toward completion\n- **Testable**: Clear success criteria that can be validated\n- **User-focused**: Relates to user value or feature capability\n- **Manageable**: Can be completed in reasonable timeframe\n\n## GitHub Issue Template (Keep Short & Stable)\n\n**Initial Issue Creation (without PRD link):**\n```markdown\n## PRD: [Feature Name]\n\n**Problem**: [1-2 sentence problem description]\n\n**Solution**: [1-2 sentence solution overview]\n\n**Detailed PRD**: Will be added after PRD file creation\n\n**Priority**: [High\u002FMedium\u002FLow]\n```\n\n**Don't forget to add the \"PRD\" label to the issue after creation.**\n\n**Issue Update (after PRD file created):**\n```markdown\n## PRD: [Feature Name]\n\n**Problem**: [1-2 sentence problem description]\n\n**Solution**: [1-2 sentence solution overview]\n\n**Detailed PRD**: See [prds\u002F[actual-issue-id]-[feature-name].md](https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai\u002Fblob\u002Fmain\u002Fprds\u002F[actual-issue-id]-[feature-name].md)\n\n**Priority**: [High\u002FMedium\u002FLow]\n```\n\n## Discussion Guidelines\n\n### PRD Planning Questions\n1. **Problem Understanding**: \"What specific problem does this feature solve for users?\"\n2. **User Impact**: \"Walk me through the complete user journey — what will change for them?\"\n3. **Technical Scope**: \"What are the core technical changes required?\"\n4. **Documentation Impact**: \"Which existing docs need updates? What new docs are needed?\"\n5. **Integration Points**: \"How does this feature integrate with existing systems?\"\n6. **Success Criteria**: \"How will we know this feature is working well?\"\n7. **Implementation Phases**: \"How can we deliver value incrementally?\"\n8. **Risk Assessment**: \"What are the main risks and how do we mitigate them?\"\n9. **Dependencies**: \"What other systems or features does this depend on?\"\n10. **Validation Strategy**: \"How will we test and validate the implementation?\"\n\n### Discussion Tips:\n- **Clarify ambiguity**: If something isn't clear, ask follow-up questions until you understand\n- **Challenge assumptions**: Help the user think through edge cases, alternatives, and unintended consequences\n- **Prioritize ruthlessly**: Help distinguish between must-have and nice-to-have based on user impact\n- **Think about users**: Always bring the conversation back to user value, experience, and outcomes\n- **Consider feasibility**: While not diving into implementation details, ensure scope is realistic\n- **Focus on major milestones**: Create 5-10 meaningful milestones rather than exhaustive micro-tasks\n- **Think cross-functionally**: Consider impact on different teams, systems, and stakeholders\n\n**Note**: If any `gh` command fails with \"command not found\", inform the user that GitHub CLI is required and provide the installation link: https:\u002F\u002Fcli.github.com\u002F\n\n**Note**: If creating the GitHub issue fails because the \"PRD\" label does not exist, create the label first (`gh label create \"PRD\" --description \"Product Requirements Document\" --color 0052CC`) and then retry creating the issue.\n\n## Workflow\n\n1. **Concept Discussion**: Get the basic idea and validate the need\n2. **Create GitHub Issue FIRST**: Short, stable concept description to get issue ID\n3. **Create PRD File**: Detailed document using actual issue ID: `prds\u002F[issue-id]-[feature-name].md`\n4. **Update GitHub Issue**: Add link to PRD file now that filename is known\n5. **Section-by-Section Discussion**: Work through each template section systematically\n6. **Milestone Definition**: Define 5-10 major milestones that represent meaningful progress\n7. **Review & Validation**: Ensure completeness and clarity\n\n**CRITICAL**: Steps 2-4 must happen in this exact order to avoid the chicken-and-egg problem of needing the issue ID for the filename.\n\n## Update ROADMAP.md (If It Exists)\n\nAfter creating the PRD, check if `docs\u002FROADMAP.md` exists. If it does, add the new feature to the appropriate timeframe section based on PRD priority:\n- **High Priority** → Short-term section\n- **Medium Priority** → Medium-term section\n- **Low Priority** → Long-term section\n\nFormat: `- [Brief feature description] (PRD #[issue-id])`\n\nThe ROADMAP.md update will be included in the commit at the end of the workflow (Option 2).\n\n## Next Steps After PRD Creation\n\nAfter completing the PRD, present the user with numbered options:\n\n```\n✅ PRD Created Successfully!\n\n**PRD File**: prds\u002F[issue-id]-[feature-name].md\n**GitHub Issue**: #[issue-id]\n\nWhat would you like to do next?\n\n**1. Start working on this PRD now**\n   Begin implementation immediately (recommended if you're ready to start)\n\n**2. Commit and push PRD for later**\n   Save the PRD and work on it later (will use [skip ci] flag)\n\nPlease enter 1 or 2:\n```\n\n### Option 1: Start Working Now\n\nIf user chooses option 1, first commit and push the PRD (same as Option 2), then instruct them:\n\n---\n\n**PRD committed and pushed.**\n\nTo start working on this PRD, run `\u002Fprd-start [issue-id]`\n\n---\n\n### Option 2: Commit and Push for Later\n\nIf user chooses option 2:\n\n```bash\n# Stage the PRD file (and ROADMAP.md if it was updated)\ngit add prds\u002F[issue-id]-[feature-name].md\n# If docs\u002FROADMAP.md exists and was updated, include it:\n# git add docs\u002FROADMAP.md\n\n# Commit with skip CI flag to avoid unnecessary CI runs\ngit commit -m \"docs(prd-[issue-id]): create PRD #[issue-id] - [feature-name] [skip ci]\n\n- Created PRD for [brief feature description]\n- Defined [X] major milestones\n- Documented problem, solution, and success criteria\n- Added to ROADMAP.md ([timeframe] section)\n- Ready for implementation\"\n\n# Pull latest and push to main\ngit pull --rebase origin main && git push origin main\n```\n\n**Confirmation Message:**\n```\n✅ PRD committed and pushed to main\n\nThe PRD is now available in the repository. To start working on it later, execute:\nprd-start [issue-id]\n```\n\n## Important Notes\n\n- **Option 1**: Best when you have time to begin implementation immediately\n- **Option 2**: Best when creating multiple PRDs or planning future work\n- **Skip CI flag**: Always use `[skip ci]` when committing PRD-only changes\n- **Issue reference**: Include issue number in commit message for traceability\n\n","# PRD Creation Slash Command\n\n## Instructions\n\nYou are helping create a Product Requirements Document (PRD) for a new feature. This process involves two main components:\n\n1. **GitHub Issue**: Short, immutable concept description that links to the detailed PRD\n2. **PRD File**: Project management document with milestone tracking and implementation plan\n\n## Process\n\n### Step 1: Understand the Feature Concept\nAsk the user to describe the feature idea to understand the core concept and scope.\n\n### Step 2: Create GitHub Issue FIRST\nCreate the GitHub issue immediately to get the issue ID. This ID is required for proper PRD file naming.\n\n**IMPORTANT: Add the \"PRD\" label to the issue for discoverability.**\n\n### Step 3: Create PRD File with Correct Naming\nCreate the PRD file using the actual GitHub issue ID: `prds\u002F[issue-id]-[feature-name].md`\n\n### Step 4: Update GitHub Issue with PRD Link\nAdd the PRD file link to the GitHub issue description now that the filename is known.\n\n### Step 5: Create PRD as a Project Management Document\nWork through the PRD template focusing on project management, milestone tracking, and implementation planning. Documentation updates should be included as part of the implementation milestones.\n\n**Key Principle**: Focus on 5-10 major milestones rather than exhaustive task lists. Each milestone should represent meaningful progress that can be clearly validated.\n\n**Consider Including** (when applicable to the project\u002Ffeature):\n- **Tests** - If the project has tests, include a milestone for test coverage of new functionality\n- **Documentation** - If the feature is user-facing, include a milestone for docs following existing project patterns\n\n**Good Milestones Examples:**\n- [ ] Core functionality implemented and working\n- [ ] Tests passing for new functionality (if project has test suite)\n- [ ] Documentation complete following existing patterns (if user-facing feature)\n- [ ] Integration with existing systems working\n- [ ] Feature ready for user testing\n\n**Avoid Micro-Tasks:**\n- ❌ Update README.md file\n- ❌ Write test for function X\n- ❌ Fix typo in documentation\n- ❌ Individual file modifications\n\n**Milestone Characteristics:**\n- **Meaningful**: Represents significant progress toward completion\n- **Testable**: Clear success criteria that can be validated\n- **User-focused**: Relates to user value or feature capability\n- **Manageable**: Can be completed in reasonable timeframe\n\n## GitHub Issue Template (Keep Short & Stable)\n\n**Initial Issue Creation (without PRD link):**\n```markdown\n## PRD: [Feature Name]\n\n**Problem**: [1-2 sentence problem description]\n\n**Solution**: [1-2 sentence solution overview]\n\n**Detailed PRD**: Will be added after PRD file creation\n\n**Priority**: [High\u002FMedium\u002FLow]\n```\n\n**Don't forget to add the \"PRD\" label to the issue after creation.**\n\n**Issue Update (after PRD file created):**\n```markdown\n## PRD: [Feature Name]\n\n**Problem**: [1-2 sentence problem description]\n\n**Solution**: [1-2 sentence solution overview]\n\n**Detailed PRD**: See [prds\u002F[actual-issue-id]-[feature-name].md](https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai\u002Fblob\u002Fmain\u002Fprds\u002F[actual-issue-id]-[feature-name].md)\n\n**Priority**: [High\u002FMedium\u002FLow]\n```\n\n## Discussion Guidelines\n\n### PRD Planning Questions\n1. **Problem Understanding**: \"What specific problem does this feature solve for users?\"\n2. **User Impact**: \"Walk me through the complete user journey — what will change for them?\"\n3. **Technical Scope**: \"What are the core technical changes required?\"\n4. **Documentation Impact**: \"Which existing docs need updates? What new docs are needed?\"\n5. **Integration Points**: \"How does this feature integrate with existing systems?\"\n6. **Success Criteria**: \"How will we know this feature is working well?\"\n7. **Implementation Phases**: \"How can we deliver value incrementally?\"\n8. **Risk Assessment**: \"What are the main risks and how do we mitigate them?\"\n9. **Dependencies**: \"What other systems or features does this depend on?\"\n10. **Validation Strategy**: \"How will we test and validate the implementation?\"\n\n### Discussion Tips:\n- **Clarify ambiguity**: If something isn't clear, ask follow-up questions until you understand\n- **Challenge assumptions**: Help the user think through edge cases, alternatives, and unintended consequences\n- **Prioritize ruthlessly**: Help distinguish between must-have and nice-to-have based on user impact\n- **Think about users**: Always bring the conversation back to user value, experience, and outcomes\n- **Consider feasibility**: While not diving into implementation details, ensure scope is realistic\n- **Focus on major milestones**: Create 5-10 meaningful milestones rather than exhaustive micro-tasks\n- **Think cross-functionally**: Consider impact on different teams, systems, and stakeholders\n\n**Note**: If any `gh` command fails with \"command not found\", inform the user that GitHub CLI is required and provide the installation link: https:\u002F\u002Fcli.github.com\u002F\n\n**Note**: If creating the GitHub issue fails because the \"PRD\" label does not exist, create the label first (`gh label create \"PRD\" --description \"Product Requirements Document\" --color 0052CC`) and then retry creating the issue.\n\n## Workflow\n\n1. **Concept Discussion**: Get the basic idea and validate the need\n2. **Create GitHub Issue FIRST**: Short, stable concept description to get issue ID\n3. **Create PRD File**: Detailed document using actual issue ID: `prds\u002F[issue-id]-[feature-name].md`\n4. **Update GitHub Issue**: Add link to PRD file now that filename is known\n5. **Section-by-Section Discussion**: Work through each template section systematically\n6. **Milestone Definition**: Define 5-10 major milestones that represent meaningful progress\n7. **Review & Validation**: Ensure completeness and clarity\n\n**CRITICAL**: Steps 2-4 must happen in this exact order to avoid the chicken-and-egg problem of needing the issue ID for the filename.\n\n## Update ROADMAP.md (If It Exists)\n\nAfter creating the PRD, check if `docs\u002FROADMAP.md` exists. If it does, add the new feature to the appropriate timeframe section based on PRD priority:\n- **High Priority** → Short-term section\n- **Medium Priority** → Medium-term section\n- **Low Priority** → Long-term section\n\nFormat: `- [Brief feature description] (PRD #[issue-id])`\n\nThe ROADMAP.md update will be included in the commit at the end of the workflow (Option 2).\n\n## Next Steps After PRD Creation\n\nAfter completing the PRD, present the user with numbered options:\n\n```\n✅ PRD Created Successfully!\n\n**PRD File**: prds\u002F[issue-id]-[feature-name].md\n**GitHub Issue**: #[issue-id]\n\nWhat would you like to do next?\n\n**1. Start working on this PRD now**\n   Begin implementation immediately (recommended if you're ready to start)\n\n**2. Commit and push PRD for later**\n   Save the PRD and work on it later (will use [skip ci] flag)\n\nPlease enter 1 or 2:\n```\n\n### Option 1: Start Working Now\n\nIf user chooses option 1, first commit and push the PRD (same as Option 2), then instruct them:\n\n---\n\n**PRD committed and pushed.**\n\nTo start working on this PRD, run `\u002Fprd-start [issue-id]`\n\n---\n\n### Option 2: Commit and Push for Later\n\nIf user chooses option 2:\n\n```bash\n# Stage the PRD file (and ROADMAP.md if it was updated)\ngit add prds\u002F[issue-id]-[feature-name].md\n# If docs\u002FROADMAP.md exists and was updated, include it:\n# git add docs\u002FROADMAP.md\n\n# Commit with skip CI flag to avoid unnecessary CI runs\ngit commit -m \"docs(prd-[issue-id]): create PRD #[issue-id] - [feature-name] [skip ci]\n\n- Created PRD for [brief feature description]\n- Defined [X] major milestones\n- Documented problem, solution, and success criteria\n- Added to ROADMAP.md ([timeframe] section)\n- Ready for implementation\"\n\n# Pull latest and push to main\ngit pull --rebase origin main && git push origin main\n```\n\n**Confirmation Message:**\n```\n✅ PRD committed and pushed to main\n\nThe PRD is now available in the repository. To start working on it later, execute:\nprd-start [issue-id]\n```\n\n## Important Notes\n\n- **Option 1**: Best when you have time to begin implementation immediately\n- **Option 2**: Best when creating multiple PRDs or planning future work\n- **Skip CI flag**: Always use `[skip ci]` when committing PRD-only changes\n- **Issue reference**: Include issue number in commit message for traceability\n\n",{"name":5,"description":7,"user-invocable":40},true,"main","6faa9f452f568fc9aa9b1c17ee728de11b760cb7",".claude\u002Fskills\u002Fdot-ai-prd-create",1,"https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp","https:\u002F\u002Fgithub.com\u002Fvfarcic","https:\u002F\u002Fyoutube.com\u002Fc\u002Fdevopstoolkit","Developer Advocate @Upbound","2026-06-19 10:10:13",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":40},[52,55,58],{"tool":53,"command":54},"npx","npx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-create",{"tool":56,"command":57},"bunx","bunx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-create",{"tool":59,"command":60},"pnpm","pnpm dlx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-create","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-prd-create\u002FSKILL.md",[],[64,89,105,120,134,144],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":35},"01M6CX45JYT898C3M792AXA5HS","dot-ai","Kubernetes cluster operations via dot-ai CLI - natural language cluster queries, AI-powered deployment recommendations, issue troubleshooting and remediation, Day 2 operations (scale, update, rollback, delete), resources, namespaces, events, logs, organizational knowledge base (ingest, search, query), organizational patterns\u002Fpolicies\u002Fcapabilities management, project scaffolding and repo audit, and session history and visualization. Run `dot-ai --help` for commands.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai\u002FSKILL.md",[],[26,28,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88],"visualization","delete","repo","deployment","kubernetes","capabilities","search","logs","knowledge","history","project","session","ingest","queries","natural language","query","scaffolding","knowledge base",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":35},"01M6CX42HR85829TGFQ95E7283","dot-ai-write-docs","Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-write-docs\u002FSKILL.md",[],[26,96,28,97,98,99,100,101,29,102,103,104,33],"docs","write","dot ai write docs","write documentation","commands","use","examples","doc","capture",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":35},"01M6CX4023QEXSVV5C22GG68XW","dot-ai-worktree-prd","Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-worktree-prd\u002FSKILL.md",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,113,26,114,28,24,115,116,117,118,119,33],"worktree","dot ai worktree prd","git","git worktree","work","branch","context",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":35},"01M6CX3YETQD0A9BPXXQABX0MW","dot-ai-version","Get comprehensive system health and diagnostics","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-version\u002FSKILL.md",[],[28,127,26,128,129,130,131,132,133],"dot ai version","version","diagnostics","health","system","system health","get",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":35},"01M6CX3X07RSJTPNSFEQRX9ACY","dot-ai-users","Manage users (create, list, delete)","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-users\u002FSKILL.md",[],[28,141,26,24,72,142,143],"dot ai users","list","manage",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":35},"01M6CX3T6YE6PVSBJGP2WSXM9J","dot-ai-tag-release","Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-tag-release\u002FSKILL.md",[],[28,151,26,152,24,153,154,155],"dot ai tag release","release","run","changelog","ready"]