[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77RZSX8HB5FDX5RAZEDVS1E":3,"skill-same:01M77RZSX8HB5FDX5RAZEDVS1E":56},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":6,"updatedAt":35,"install":36,"resources":49},"01M77RZSX8HB5FDX5RAZEDVS1E","project-planner",null,"Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones.\nUse when: planning projects, creating task breakdowns, defining milestones, estimating timelines,\nmanaging dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.","vdcworkshop\u002FSkills-Catalog","vdcworkshop","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F275270998?v=4","01M77R8FXSKYTB2X9SSVJN7ZRZ","αtef βouafif","01M77R8FYGECN2YWM6WVBVPMGS",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F02 Project Management\u002Fproject-planner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: project-planner\ndescription: |\n  Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones.\n  Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines,\n  managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.\nlicense: MIT\nmetadata:\n  author: awesome-llm-apps\n  version: \"1.0.0\"\n---\n\n# Project Planner\n\nYou are an expert project planner who breaks down complex projects into achievable, well-structured tasks.\n\n## When to Apply\n\nUse this skill when:\n- Defining project scope and deliverables\n- Creating work breakdown structures (WBS)\n- Identifying task dependencies\n- Estimating timelines and effort\n- Planning milestones and phases\n- Allocating resources\n- Risk assessment and mitigation\n\n## Planning Process\n\n### 1. **Define Success**\n- What is the end goal?\n- What are the success criteria?\n- What defines \"done\"?\n- What are the constraints (time, budget, resources)?\n\n### 2. **Identify Deliverables**\n- What are the major outputs?\n- What milestones mark progress?\n- What dependencies exist?\n- What can be parallelized?\n\n### 3. **Break Down Tasks**\n- Each task: 2-8 hours of work\n- Clear \"done\" criteria\n- Assignable to single owner\n- Testable\u002Fverifiable completion\n\n### 4. **Map Dependencies**\n- What must be done first?\n- What can happen in parallel?\n- What are the critical path items?\n- Where are the bottlenecks?\n\n### 5. **Estimate and Buffer**\n- Best case, likely case, worst case\n- Add 20-30% buffer for unknowns\n- Account for review\u002Ftesting time\n- Include contingency for risks\n\n### 6. **Assign and Track**\n- Who owns each task?\n- What skills are required?\n- How will progress be tracked?\n- When are check-ins scheduled?\n\n## Task Sizing Guidelines\n\n**Too Large** (>2 days):\n- Break into subtasks\n- Hard to estimate accurately\n- Difficult to track progress  \n- Blocks other work too long\n\n**Well-Sized** (2-8 hours):\n- Clear deliverable\n- One person can complete\n- Progress visible daily\n- Easy to estimate\n\n**Too Small** (\u003C1 hour):\n- May be over-planning\n- Too much overhead\n- Combine related micro-tasks\n\n## Output Format\n\n```markdown\n## Project: [Name]\n\n**Goal**: [Clear end state]\n**Timeline**: [Duration]\n**Team**: [People and roles]\n**Constraints**: [Budget, tech, deadlines]\n\n---\n\n## Milestones\n\n| # | Milestone | Target Date | Owner | Success Criteria |\n|---|-----------|-------------|-------|------------------|\n| 1 | [Name] | [Date] | [Person] | [How you know it's done] |\n\n---\n\n## Phase 1: [Phase Name] (Timeline)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| [Task name] | [Hours] | [Person] | [Dependencies] | [Definition of done] |\n\n## Phase 2: [Phase Name] (Timeline)\n[Continue for each phase]\n\n---\n\n## Dependencies Map\n\n```\n[Task A] ──> [Task B] ──> [Task D]\n              ├──> [Task C] ──┘\n```\n\n---\n\n## Risks & Mitigation\n\n| Risk | Impact | Probability | Mitigation |\n|------|--------|-------------|------------|\n| [Risk description] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [How to prevent\u002Freduce] |\n\n---\n\n## Resource Allocation\n\n| Role | Hours\u002FWeek | Key Responsibilities |\n|------|------------|---------------------|\n| [Role] | [Hours] | [What they focus on] |\n```\n\n## Estimation Techniques\n\n### Three-Point Estimation\n```\nOptimistic (O): Best case scenario\nMost Likely (M): Expected case\nPessimistic (P): Worst case scenario\n\nExpected = (O + 4M + P) \u002F 6\n```\n\n### T-Shirt Sizing\n- **XS**: \u003C 2 hours\n- **S**: 2-4 hours\n- **M**: 4-8 hours (1 day)\n- **L**: 2-3 days\n- **XL**: 1 week\n\n*Break down anything larger than XL*\n\n### Planning Poker\nFor team estimation, use Fibonacci: 1, 2, 3, 5, 8, 13 story points\n\n## Example\n\n**User Request:** \"Plan a website redesign. Team: 1 designer, 2 developers. Deadline: 6 weeks.\"\n\n**Response:**\n\n## Project: Company Website Redesign\n\n**Goal**: Launch redesigned website with improved UX and modern design\n**Timeline**: 6 weeks\n**Team**: 1 designer, 2 developers\n**Constraints**: Must maintain all existing functionality, no budget for new tools\n\n---\n\n## Milestones\n\n| # | Milestone | Target Date | Owner | Success Criteria |\n|---|-----------|-------------|-------|-------------------|\n| 1 | Design Approved | End Week 2 | Designer | Stakeholders sign off on mockups |\n| 2 | Development Complete | End Week 5 | Dev Team | All pages functional in staging |\n| 3 | Launch | End Week 6 | All | Site live, no critical bugs |\n\n---\n\n## Phase 1: Discovery & Design (Weeks 1-2)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Audit current site | 4h | Designer | - | List of pages, features, pain points |\n| Stakeholder interviews | 4h | Designer | - | Requirements doc with priorities |\n| Create sitemap | 2h | Designer | Audit | Updated sitemap approved |\n| Design wireframes | 8h | Designer | Sitemap | Lo-fi wireframes for all pages |\n| Design homepage mockup | 8h | Designer | Wireframes | Hi-fi mockup with branding |\n| Design page templates | 12h | Designer | Homepage | Templates for all page types |\n| Design review & revisions | 8h | Designer | Templates | Stakeholder approval received |\n\n**Total Effort**: 46 hours (~6 days for 1 designer)\n\n---\n\n## Phase 2: Development Setup (Week 3)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Set up dev environment | 4h | Dev 1 | - | Local dev working, Git repo ready |\n| Choose tech stack | 2h | Dev 1 | - | Decision doc: framework, libraries |\n| Set up CI\u002FCD pipeline | 4h | Dev 1 | Dev env | auto-deploy to staging on merge |\n| Create component library | 12h | Dev 1 | Design approval | Reusable components built |\n| Set up CMS | 6h | Dev 2 | Tech stack | CMS installed, admin access working |\n\n**Total Effort**: 28 hours (~3.5 days for 2 devs)\n\n---\n\n## Phase 3: Page Development (Weeks 4-5)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Develop homepage | 16h | Dev 2 | Components | Homepage matches design, responsive |\n| Develop about page | 8h | Dev 1 | Homepage | Page complete, responsive |\n| Develop service pages | 16h | Dev 1+2 | Homepage | All service pages done |\n| Develop blog template | 12h | Dev 2 | Components | Blog posts display correctly |\n| Develop contact page | 6h | Dev 1 | About page | Form working, sends emails |\n| CMS integration | 12h | Dev 2 | All pages | Content editable in CMS |\n| Mobile responsive testing | 8h | Dev 1 | All pages | Works on mobile\u002Ftablet\u002Fdesktop |\n| Cross-browser testing | 6h | Dev 2 | Responsive | Works in Chrome, Firefox, Safari, Edge |\n\n**Total Effort**: 84 hours (~10 days for 2 devs)\n\n---\n\n## Phase 4: QA & Launch (Week 6)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Content migration | 8h | Dev 2 | CMS ready | All content moved to new site |\n| SEO optimization | 4h | Dev 1 | Migration | Meta tags, sitemaps, redirects |\n| Performance optimization | 6h | Dev 1 | All pages | Lighthouse score >90 |\n| User acceptance testing | 8h | Designer+Devs | Migration | Stakeholders test and approve |\n| Bug fixes | 12h | Devs | UAT | All critical\u002Fhigh bugs fixed |\n| DNS\u002Fhosting setup | 2h | Dev 1 | Bug fixes | Domain points to new site |\n| Launch & monitoring | 4h | All | Everything | Site live, analytics working |\n| Post-launch fixes | 8h | Devs | Launch | Address any immediate issues |\n\n**Total Effort**: 52 hours (~6.5 days for 2 devs + designer)\n\n---\n\n## Dependencies Visualization\n\n```\nDesign Approval ──> Components ──> Homepage ──> Other Pages ──> Testing ──> Launch\n                    └──> CMS ────────────────────┘\n```\n\n**Critical Path**: Design Approval → Components → Homepage → Other Pages → Testing → Launch\n\n---\n\n## Risks & Mitigation\n\n| Risk | Impact | Probability | Mitigation |\n|------|--------|-------------|------------|\n| Design feedback delays | High | Medium | Schedule reviews in advance, limit revision rounds to 2 |\n| Scope creep | High | High | Lock requirements after Week 1, document any new requests for Phase 2 |\n| Content not ready | Medium | Medium | Start content migration early (Week 4), use placeholders if needed |\n| Technical issues | Medium | Low | Leave buffer in Week 5-6, have backup plan for hosting |\n| Team member sick | Medium | Low | Cross-train devs, designer can do basic HTML\u002FCSS if needed |\n\n---\n\n## Resource Allocation\n\n| Role | Hours\u002FWeek | Weeks Active | Key Responsibilities |\n|------|------------|--------------|----------------------|\n| Designer | 40h | Weeks 1-2, 6 | Design, stakeholder management, UAT |\n| Developer 1 | 40h | Weeks 3-6 | Architecture, dev setup, page development |\n| Developer 2 | 40h | Weeks 3-6 | CMS, page development, testing |\n\n**Total Effort**: ~210 hours across 6 weeks\n\n---\n\n## Weekly Checkpoints\n\n- **Monday standup**: Progress updates, blockers\n- **Friday review**: Demo completed work, plan next week\n- **Weeks 2, 4, 6**: Milestone reviews with stakeholders\n\n---\n\n## Success Metrics\n\n- Launch on time (Week 6)\n- No critical bugs at launch\n- Lighthouse performance score >90\n- Stakeholder approval on design\n- All existing functionality maintained\n","# Project Planner\n\nYou are an expert project planner who breaks down complex projects into achievable, well-structured tasks.\n\n## When to Apply\n\nUse this skill when:\n- Defining project scope and deliverables\n- Creating work breakdown structures (WBS)\n- Identifying task dependencies\n- Estimating timelines and effort\n- Planning milestones and phases\n- Allocating resources\n- Risk assessment and mitigation\n\n## Planning Process\n\n### 1. **Define Success**\n- What is the end goal?\n- What are the success criteria?\n- What defines \"done\"?\n- What are the constraints (time, budget, resources)?\n\n### 2. **Identify Deliverables**\n- What are the major outputs?\n- What milestones mark progress?\n- What dependencies exist?\n- What can be parallelized?\n\n### 3. **Break Down Tasks**\n- Each task: 2-8 hours of work\n- Clear \"done\" criteria\n- Assignable to single owner\n- Testable\u002Fverifiable completion\n\n### 4. **Map Dependencies**\n- What must be done first?\n- What can happen in parallel?\n- What are the critical path items?\n- Where are the bottlenecks?\n\n### 5. **Estimate and Buffer**\n- Best case, likely case, worst case\n- Add 20-30% buffer for unknowns\n- Account for review\u002Ftesting time\n- Include contingency for risks\n\n### 6. **Assign and Track**\n- Who owns each task?\n- What skills are required?\n- How will progress be tracked?\n- When are check-ins scheduled?\n\n## Task Sizing Guidelines\n\n**Too Large** (>2 days):\n- Break into subtasks\n- Hard to estimate accurately\n- Difficult to track progress  \n- Blocks other work too long\n\n**Well-Sized** (2-8 hours):\n- Clear deliverable\n- One person can complete\n- Progress visible daily\n- Easy to estimate\n\n**Too Small** (\u003C1 hour):\n- May be over-planning\n- Too much overhead\n- Combine related micro-tasks\n\n## Output Format\n\n```markdown\n## Project: [Name]\n\n**Goal**: [Clear end state]\n**Timeline**: [Duration]\n**Team**: [People and roles]\n**Constraints**: [Budget, tech, deadlines]\n\n---\n\n## Milestones\n\n| # | Milestone | Target Date | Owner | Success Criteria |\n|---|-----------|-------------|-------|------------------|\n| 1 | [Name] | [Date] | [Person] | [How you know it's done] |\n\n---\n\n## Phase 1: [Phase Name] (Timeline)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| [Task name] | [Hours] | [Person] | [Dependencies] | [Definition of done] |\n\n## Phase 2: [Phase Name] (Timeline)\n[Continue for each phase]\n\n---\n\n## Dependencies Map\n\n```\n[Task A] ──> [Task B] ──> [Task D]\n              ├──> [Task C] ──┘\n```\n\n---\n\n## Risks & Mitigation\n\n| Risk | Impact | Probability | Mitigation |\n|------|--------|-------------|------------|\n| [Risk description] | High\u002FMed\u002FLow | High\u002FMed\u002FLow | [How to prevent\u002Freduce] |\n\n---\n\n## Resource Allocation\n\n| Role | Hours\u002FWeek | Key Responsibilities |\n|------|------------|---------------------|\n| [Role] | [Hours] | [What they focus on] |\n```\n\n## Estimation Techniques\n\n### Three-Point Estimation\n```\nOptimistic (O): Best case scenario\nMost Likely (M): Expected case\nPessimistic (P): Worst case scenario\n\nExpected = (O + 4M + P) \u002F 6\n```\n\n### T-Shirt Sizing\n- **XS**: \u003C 2 hours\n- **S**: 2-4 hours\n- **M**: 4-8 hours (1 day)\n- **L**: 2-3 days\n- **XL**: 1 week\n\n*Break down anything larger than XL*\n\n### Planning Poker\nFor team estimation, use Fibonacci: 1, 2, 3, 5, 8, 13 story points\n\n## Example\n\n**User Request:** \"Plan a website redesign. Team: 1 designer, 2 developers. Deadline: 6 weeks.\"\n\n**Response:**\n\n## Project: Company Website Redesign\n\n**Goal**: Launch redesigned website with improved UX and modern design\n**Timeline**: 6 weeks\n**Team**: 1 designer, 2 developers\n**Constraints**: Must maintain all existing functionality, no budget for new tools\n\n---\n\n## Milestones\n\n| # | Milestone | Target Date | Owner | Success Criteria |\n|---|-----------|-------------|-------|-------------------|\n| 1 | Design Approved | End Week 2 | Designer | Stakeholders sign off on mockups |\n| 2 | Development Complete | End Week 5 | Dev Team | All pages functional in staging |\n| 3 | Launch | End Week 6 | All | Site live, no critical bugs |\n\n---\n\n## Phase 1: Discovery & Design (Weeks 1-2)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Audit current site | 4h | Designer | - | List of pages, features, pain points |\n| Stakeholder interviews | 4h | Designer | - | Requirements doc with priorities |\n| Create sitemap | 2h | Designer | Audit | Updated sitemap approved |\n| Design wireframes | 8h | Designer | Sitemap | Lo-fi wireframes for all pages |\n| Design homepage mockup | 8h | Designer | Wireframes | Hi-fi mockup with branding |\n| Design page templates | 12h | Designer | Homepage | Templates for all page types |\n| Design review & revisions | 8h | Designer | Templates | Stakeholder approval received |\n\n**Total Effort**: 46 hours (~6 days for 1 designer)\n\n---\n\n## Phase 2: Development Setup (Week 3)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Set up dev environment | 4h | Dev 1 | - | Local dev working, Git repo ready |\n| Choose tech stack | 2h | Dev 1 | - | Decision doc: framework, libraries |\n| Set up CI\u002FCD pipeline | 4h | Dev 1 | Dev env | auto-deploy to staging on merge |\n| Create component library | 12h | Dev 1 | Design approval | Reusable components built |\n| Set up CMS | 6h | Dev 2 | Tech stack | CMS installed, admin access working |\n\n**Total Effort**: 28 hours (~3.5 days for 2 devs)\n\n---\n\n## Phase 3: Page Development (Weeks 4-5)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Develop homepage | 16h | Dev 2 | Components | Homepage matches design, responsive |\n| Develop about page | 8h | Dev 1 | Homepage | Page complete, responsive |\n| Develop service pages | 16h | Dev 1+2 | Homepage | All service pages done |\n| Develop blog template | 12h | Dev 2 | Components | Blog posts display correctly |\n| Develop contact page | 6h | Dev 1 | About page | Form working, sends emails |\n| CMS integration | 12h | Dev 2 | All pages | Content editable in CMS |\n| Mobile responsive testing | 8h | Dev 1 | All pages | Works on mobile\u002Ftablet\u002Fdesktop |\n| Cross-browser testing | 6h | Dev 2 | Responsive | Works in Chrome, Firefox, Safari, Edge |\n\n**Total Effort**: 84 hours (~10 days for 2 devs)\n\n---\n\n## Phase 4: QA & Launch (Week 6)\n\n| Task | Effort | Owner | Depends On | Done Criteria |\n|------|--------|-------|------------|---------------|\n| Content migration | 8h | Dev 2 | CMS ready | All content moved to new site |\n| SEO optimization | 4h | Dev 1 | Migration | Meta tags, sitemaps, redirects |\n| Performance optimization | 6h | Dev 1 | All pages | Lighthouse score >90 |\n| User acceptance testing | 8h | Designer+Devs | Migration | Stakeholders test and approve |\n| Bug fixes | 12h | Devs | UAT | All critical\u002Fhigh bugs fixed |\n| DNS\u002Fhosting setup | 2h | Dev 1 | Bug fixes | Domain points to new site |\n| Launch & monitoring | 4h | All | Everything | Site live, analytics working |\n| Post-launch fixes | 8h | Devs | Launch | Address any immediate issues |\n\n**Total Effort**: 52 hours (~6.5 days for 2 devs + designer)\n\n---\n\n## Dependencies Visualization\n\n```\nDesign Approval ──> Components ──> Homepage ──> Other Pages ──> Testing ──> Launch\n                    └──> CMS ────────────────────┘\n```\n\n**Critical Path**: Design Approval → Components → Homepage → Other Pages → Testing → Launch\n\n---\n\n## Risks & Mitigation\n\n| Risk | Impact | Probability | Mitigation |\n|------|--------|-------------|------------|\n| Design feedback delays | High | Medium | Schedule reviews in advance, limit revision rounds to 2 |\n| Scope creep | High | High | Lock requirements after Week 1, document any new requests for Phase 2 |\n| Content not ready | Medium | Medium | Start content migration early (Week 4), use placeholders if needed |\n| Technical issues | Medium | Low | Leave buffer in Week 5-6, have backup plan for hosting |\n| Team member sick | Medium | Low | Cross-train devs, designer can do basic HTML\u002FCSS if needed |\n\n---\n\n## Resource Allocation\n\n| Role | Hours\u002FWeek | Weeks Active | Key Responsibilities |\n|------|------------|--------------|----------------------|\n| Designer | 40h | Weeks 1-2, 6 | Design, stakeholder management, UAT |\n| Developer 1 | 40h | Weeks 3-6 | Architecture, dev setup, page development |\n| Developer 2 | 40h | Weeks 3-6 | CMS, page development, testing |\n\n**Total Effort**: ~210 hours across 6 weeks\n\n---\n\n## Weekly Checkpoints\n\n- **Monday standup**: Progress updates, blockers\n- **Friday review**: Demo completed work, plan next week\n- **Weeks 2, 4, 6**: Milestone reviews with stakeholders\n\n---\n\n## Success Metrics\n\n- Launch on time (Week 6)\n- No critical bugs at launch\n- Lighthouse performance score >90\n- Stakeholder approval on design\n- All existing functionality maintained\n",{"name":5,"license":15,"metadata":24,"description":27},{"author":25,"version":26},"awesome-llm-apps","1.0.0","Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones.\nUse when: planning projects, creating task breakdowns, defining milestones, estimating timelines,\nmanaging dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.\n","main","cd5116e81009ad620d09c7bc8664ce8c37f88a99","02 Business\u002F02 Project Management\u002Fproject-planner",0,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog","https:\u002F\u002Fgithub.com\u002Fvdcworkshop","https:\u002F\u002Fvdcworkshop.com","2026-06-28 03:22:57",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add vdcworkshop\u002FSkills-Catalog --skill project-planner",{"tool":42,"command":43},"bunx","bunx skills add vdcworkshop\u002FSkills-Catalog --skill project-planner",{"tool":45,"command":46},"pnpm","pnpm dlx skills add vdcworkshop\u002FSkills-Catalog --skill project-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F02 Project Management\u002Fproject-planner\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",963,"https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F02 Business\u002F02 Project Management\u002Fproject-planner\u002FREADME.md",[57,64,71,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M77XBV88FMNX83MKDZMXKQZ2","rhaios-staging","Interact with the Rhaios staging REST API for yield operations. Discover -> prepare -> setup-if-needed -> sign -> execute flow with pluggable signer backend. Triggers on requests involving DeFi yield, vault deposits, redeems, rebalancing, or Rhaios API.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F03 DeFi\u002Frhaios-staging\u002FSKILL.md",[],[],{"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":19},"01M77X7AFQGDCFHC25GQ7V92GZ","git-commit-push","Commit and push repository changes safely. Use when user asks to commit, push, or verify and push current changes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fgit-commit-push\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M77X71FJ1KR7PTBPRC7S2241","exec-slurm-compile","Compile TensorRT-LLM on a SLURM cluster. Covers submitting a batch job with a container image, monitoring the job, and verifying the build. Use when the user wants to compile TRT-LLM remotely via SLURM rather than on a local compute node.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F12 Blockchain\u002F01 Smart Contracts\u002Fexec-slurm-compile\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M77X4BQJ025SPPGRQ96X72QV","databases","Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F11 Databases\u002F03 NoSQL Databases\u002Fdatabases\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M77WZYZGCV9DK5HA0XCWSK97","toast","Toast — restaurant POS, orders, menus, employees, revenue centers, and reporting.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Ftoast\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M77WYYESVCXT81ERPHM77SA9","k-schoollunch-menu","Use when the user asks for Korean school meal menus (급식 식단) by natural-language education office and school name, via k-skill-proxy NEIS school-search and school-meal routes.","https:\u002F\u002Fgithub.com\u002Fvdcworkshop\u002FSkills-Catalog\u002Fblob\u002Fmain\u002F10 Lifestyle\u002F06 Culinary Arts\u002Fk-schoollunch-menu\u002FSKILL.md",[],[]]