[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPXWYSN91EYKZWHFXJBDRM":3,"skill-same:01M6HPXWYSN91EYKZWHFXJBDRM":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":43,"install":44,"resources":56},"01M6HPXWYSN91EYKZWHFXJBDRM","estimate",null,"Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.","welflau\u002Fai-dev-system","welflau","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7010385?v=4","01M6HPTDGF18RFY07M229P8CTM","01M6HPTDMRMZCJPYBFEA9XVVYT",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Festimate\u002FSKILL.md",[],[5,18,19,20,21,22,23,24,25,26,27,28],"analyzing","risk","grep","read","complexity","task","velocity","dependencies","structured","with","true","2026-11-10 10:12:30",false,"---\nname: estimate\ndescription: \"Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.\"\nargument-hint: \"[task-description]\"\nuser-invocable: true\nallowed-tools: Read, Glob, Grep\n---\n\nWhen this skill is invoked:\n\n1. **Read the task description** from the argument. If the description is too\n   vague to estimate meaningfully, ask for clarification before proceeding.\n\n2. **Read CLAUDE.md** for project context: tech stack, coding standards,\n   architectural patterns, and any estimation guidelines.\n\n3. **Read relevant design documents** from `design\u002Fgdd\u002F` if the task relates\n   to a documented feature or system.\n\n4. **Scan the codebase** to understand the systems affected by this task:\n   - Identify files and modules that would need to change\n   - Assess the complexity of those files (size, dependency count, cyclomatic\n     complexity)\n   - Identify integration points with other systems\n   - Check for existing test coverage in the affected areas\n\n5. **Read past sprint data** from `production\u002Fsprints\u002F` if available:\n   - Look for similar completed tasks and their actual effort\n   - Calculate historical velocity (planned vs actual)\n   - Identify any estimation bias patterns (consistently over or under)\n\n6. **Analyze the following factors**:\n\n   **Code Complexity**:\n   - Lines of code in affected files\n   - Number of dependencies and coupling level\n   - Whether this touches core\u002Fengine code vs leaf\u002Ffeature code\n   - Whether existing patterns can be followed or new patterns are needed\n\n   **Scope**:\n   - Number of systems touched\n   - New code vs modification of existing code\n   - Amount of new test coverage required\n   - Data migration or configuration changes needed\n\n   **Risk**:\n   - New technology or unfamiliar libraries\n   - Unclear or ambiguous requirements\n   - Dependencies on unfinished work\n   - Cross-system integration complexity\n   - Performance sensitivity\n\n7. **Generate the estimate**:\n\n```markdown\n## Task Estimate: [Task Name]\nGenerated: [Date]\n\n### Task Description\n[Restate the task clearly in 1-2 sentences]\n\n### Complexity Assessment\n\n| Factor | Assessment | Notes |\n|--------|-----------|-------|\n| Systems affected | [List] | [Core, gameplay, UI, etc.] |\n| Files likely modified | [Count] | [Key files listed below] |\n| New code vs modification | [Ratio, e.g., 70% new \u002F 30% modification] | |\n| Integration points | [Count] | [Which systems interact] |\n| Test coverage needed | [Low \u002F Medium \u002F High] | [Unit, integration, manual] |\n| Existing patterns available | [Yes \u002F Partial \u002F No] | [Can follow existing code or new ground] |\n\n**Key files likely affected:**\n- `[path\u002Fto\u002Ffile1]` -- [what changes here]\n- `[path\u002Fto\u002Ffile2]` -- [what changes here]\n- `[path\u002Fto\u002Ffile3]` -- [what changes here]\n\n### Effort Estimate\n\n| Scenario | Days | Assumption |\n|----------|------|------------|\n| Optimistic | [X] | Everything goes right, no surprises, requirements are clear |\n| Expected | [Y] | Normal pace, minor issues, one round of review feedback |\n| Pessimistic | [Z] | Significant unknowns surface, blocked for a day, requirements change |\n\n**Recommended budget: [Y days]**\n\n[If historical data is available: \"Based on [N] similar tasks that averaged\n[X] days actual vs [Y] days estimated, a [correction factor] adjustment has\nbeen applied.\"]\n\n### Confidence: [High \u002F Medium \u002F Low]\n\n**High** -- Clear requirements, familiar systems, follows existing patterns,\nsimilar tasks completed before.\n\n**Medium** -- Some unknowns, touches moderately complex systems, partial\nprecedent from previous work.\n\n**Low** -- Significant unknowns, new technology, unclear requirements, or\ncross-cutting concerns across many systems.\n\n[Explain which factors drive the confidence level for this specific task.]\n\n### Risk Factors\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Specific risk] | [High\u002FMed\u002FLow] | [Days added if realized] | [How to reduce] |\n| [Another risk] | [Likelihood] | [Impact] | [Mitigation] |\n\n### Dependencies\n\n| Dependency | Status | Impact if Delayed |\n|-----------|--------|-------------------|\n| [What must be done first] | [Done \u002F In Progress \u002F Not Started] | [How it affects this task] |\n\n### Suggested Breakdown\n\n| # | Sub-task | Estimate | Notes |\n|---|----------|----------|-------|\n| 1 | [Research \u002F spike] | [X days] | [If unknowns need investigation first] |\n| 2 | [Core implementation] | [X days] | [The main work] |\n| 3 | [Integration with system X] | [X days] | [Connecting to existing code] |\n| 4 | [Testing and validation] | [X days] | [Writing tests, manual verification] |\n| 5 | [Code review and iteration] | [X days] | [Review feedback, fixes] |\n| | **Total** | **[Y days]** | |\n\n### Historical Comparison\n[If similar tasks exist in sprint history:]\n\n| Similar Task | Estimated | Actual | Relevant Difference |\n|-------------|-----------|--------|-------------------|\n| [Past task 1] | [X days] | [Y days] | [What makes it similar\u002Fdifferent] |\n| [Past task 2] | [X days] | [Y days] | [What makes it similar\u002Fdifferent] |\n\n### Notes and Assumptions\n- [Key assumption that affects the estimate]\n- [Another assumption]\n- [Any caveats about scope boundaries -- what is included vs excluded]\n- [Recommendations: e.g., \"Consider a spike first if requirement X is unclear\"]\n```\n\n8. **Output the estimate** to the user with a brief summary: recommended\n   budget, confidence level, and the single biggest risk factor.\n\n### Guidelines\n\n- Always give a range (optimistic \u002F expected \u002F pessimistic), never a single\n  number. Single-point estimates create false precision.\n- The recommended budget should be the expected estimate, not the optimistic\n  one. Padding is not dishonest -- it is realistic.\n- If confidence is Low, recommend a time-boxed spike or prototype before\n  committing to the full estimate.\n- Be explicit about what is included and excluded. Scope ambiguity is the\n  most common source of estimation error.\n- Round to half-day increments. Estimating in hours implies false precision\n  for tasks longer than a day.\n- If the task is too large to estimate confidently (more than 10 days\n  expected), recommend breaking it into smaller tasks and estimating those\n  individually.\n- Do not pad estimates silently. If risk exists, call it out explicitly in\n  the risk factors section so the team can decide how to handle it.\n","When this skill is invoked:\n\n1. **Read the task description** from the argument. If the description is too\n   vague to estimate meaningfully, ask for clarification before proceeding.\n\n2. **Read CLAUDE.md** for project context: tech stack, coding standards,\n   architectural patterns, and any estimation guidelines.\n\n3. **Read relevant design documents** from `design\u002Fgdd\u002F` if the task relates\n   to a documented feature or system.\n\n4. **Scan the codebase** to understand the systems affected by this task:\n   - Identify files and modules that would need to change\n   - Assess the complexity of those files (size, dependency count, cyclomatic\n     complexity)\n   - Identify integration points with other systems\n   - Check for existing test coverage in the affected areas\n\n5. **Read past sprint data** from `production\u002Fsprints\u002F` if available:\n   - Look for similar completed tasks and their actual effort\n   - Calculate historical velocity (planned vs actual)\n   - Identify any estimation bias patterns (consistently over or under)\n\n6. **Analyze the following factors**:\n\n   **Code Complexity**:\n   - Lines of code in affected files\n   - Number of dependencies and coupling level\n   - Whether this touches core\u002Fengine code vs leaf\u002Ffeature code\n   - Whether existing patterns can be followed or new patterns are needed\n\n   **Scope**:\n   - Number of systems touched\n   - New code vs modification of existing code\n   - Amount of new test coverage required\n   - Data migration or configuration changes needed\n\n   **Risk**:\n   - New technology or unfamiliar libraries\n   - Unclear or ambiguous requirements\n   - Dependencies on unfinished work\n   - Cross-system integration complexity\n   - Performance sensitivity\n\n7. **Generate the estimate**:\n\n```markdown\n## Task Estimate: [Task Name]\nGenerated: [Date]\n\n### Task Description\n[Restate the task clearly in 1-2 sentences]\n\n### Complexity Assessment\n\n| Factor | Assessment | Notes |\n|--------|-----------|-------|\n| Systems affected | [List] | [Core, gameplay, UI, etc.] |\n| Files likely modified | [Count] | [Key files listed below] |\n| New code vs modification | [Ratio, e.g., 70% new \u002F 30% modification] | |\n| Integration points | [Count] | [Which systems interact] |\n| Test coverage needed | [Low \u002F Medium \u002F High] | [Unit, integration, manual] |\n| Existing patterns available | [Yes \u002F Partial \u002F No] | [Can follow existing code or new ground] |\n\n**Key files likely affected:**\n- `[path\u002Fto\u002Ffile1]` -- [what changes here]\n- `[path\u002Fto\u002Ffile2]` -- [what changes here]\n- `[path\u002Fto\u002Ffile3]` -- [what changes here]\n\n### Effort Estimate\n\n| Scenario | Days | Assumption |\n|----------|------|------------|\n| Optimistic | [X] | Everything goes right, no surprises, requirements are clear |\n| Expected | [Y] | Normal pace, minor issues, one round of review feedback |\n| Pessimistic | [Z] | Significant unknowns surface, blocked for a day, requirements change |\n\n**Recommended budget: [Y days]**\n\n[If historical data is available: \"Based on [N] similar tasks that averaged\n[X] days actual vs [Y] days estimated, a [correction factor] adjustment has\nbeen applied.\"]\n\n### Confidence: [High \u002F Medium \u002F Low]\n\n**High** -- Clear requirements, familiar systems, follows existing patterns,\nsimilar tasks completed before.\n\n**Medium** -- Some unknowns, touches moderately complex systems, partial\nprecedent from previous work.\n\n**Low** -- Significant unknowns, new technology, unclear requirements, or\ncross-cutting concerns across many systems.\n\n[Explain which factors drive the confidence level for this specific task.]\n\n### Risk Factors\n\n| Risk | Likelihood | Impact | Mitigation |\n|------|-----------|--------|------------|\n| [Specific risk] | [High\u002FMed\u002FLow] | [Days added if realized] | [How to reduce] |\n| [Another risk] | [Likelihood] | [Impact] | [Mitigation] |\n\n### Dependencies\n\n| Dependency | Status | Impact if Delayed |\n|-----------|--------|-------------------|\n| [What must be done first] | [Done \u002F In Progress \u002F Not Started] | [How it affects this task] |\n\n### Suggested Breakdown\n\n| # | Sub-task | Estimate | Notes |\n|---|----------|----------|-------|\n| 1 | [Research \u002F spike] | [X days] | [If unknowns need investigation first] |\n| 2 | [Core implementation] | [X days] | [The main work] |\n| 3 | [Integration with system X] | [X days] | [Connecting to existing code] |\n| 4 | [Testing and validation] | [X days] | [Writing tests, manual verification] |\n| 5 | [Code review and iteration] | [X days] | [Review feedback, fixes] |\n| | **Total** | **[Y days]** | |\n\n### Historical Comparison\n[If similar tasks exist in sprint history:]\n\n| Similar Task | Estimated | Actual | Relevant Difference |\n|-------------|-----------|--------|-------------------|\n| [Past task 1] | [X days] | [Y days] | [What makes it similar\u002Fdifferent] |\n| [Past task 2] | [X days] | [Y days] | [What makes it similar\u002Fdifferent] |\n\n### Notes and Assumptions\n- [Key assumption that affects the estimate]\n- [Another assumption]\n- [Any caveats about scope boundaries -- what is included vs excluded]\n- [Recommendations: e.g., \"Consider a spike first if requirement X is unclear\"]\n```\n\n8. **Output the estimate** to the user with a brief summary: recommended\n   budget, confidence level, and the single biggest risk factor.\n\n### Guidelines\n\n- Always give a range (optimistic \u002F expected \u002F pessimistic), never a single\n  number. Single-point estimates create false precision.\n- The recommended budget should be the expected estimate, not the optimistic\n  one. Padding is not dishonest -- it is realistic.\n- If confidence is Low, recommend a time-boxed spike or prototype before\n  committing to the full estimate.\n- Be explicit about what is included and excluded. Scope ambiguity is the\n  most common source of estimation error.\n- Round to half-day increments. Estimating in hours implies false precision\n  for tasks longer than a day.\n- If the task is too large to estimate confidently (more than 10 days\n  expected), recommend breaking it into smaller tasks and estimating those\n  individually.\n- Do not pad estimates silently. If risk exists, call it out explicitly in\n  the risk factors section so the team can decide how to handle it.\n",{"name":5,"description":7,"allowed-tools":34,"argument-hint":35,"user-invocable":36},"Read, Glob, Grep","[task-description]",true,"main","18d0e63d1313ca87098f614aa7c1e2dcf6de79c7","backend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Festimate",1,"https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system","https:\u002F\u002Fgithub.com\u002Fwelflau","2026-11-10 11:14:25",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":36},[46,49,52],{"tool":47,"command":48},"npx","npx skills add welflau\u002Fai-dev-system --skill estimate",{"tool":50,"command":51},"bunx","bunx skills add welflau\u002Fai-dev-system --skill estimate",{"tool":53,"command":54},"pnpm","pnpm dlx skills add welflau\u002Fai-dev-system --skill estimate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fconfig_packs\u002Fgame-dev\u002Fshared\u002Fskills\u002Festimate\u002FSKILL.md",[],[58,93,124,149,175,199],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":63,"sourceHtmlUrl":64,"categories":65,"keywords":71,"publishedAt":29},"01M6HSTDP4M3JFXEBK91VFB4PA","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Fweb-artifacts-builder\u002FSKILL.md",[66],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92],"web artifacts builder","web","artifacts","artifacts builder","builder","frontend","css","components","react","routing","state management","state","file","Tailwind","use","single-file","simple","ui components","multi","for","single",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":109,"publishedAt":29},"01M6HSDXH0JSP8R3QTNY9XZ8HN","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Ffrontend-design\u002FSKILL.md",[100,101,104],{"categoryNo":67,"categoryName":68,"taxonomyType":69,"taxonomyTypeDesc":70},{"categoryNo":102,"categoryName":103,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[77,110,111,78,73,79,80,112,113,114,74,115,116,117,86,118,119,120,121,27,122,123],"design","frontend design","react components","create","code","examples","applications","landing","ui design","pages","aesthetics","web ui","generic","when",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":132,"publishedAt":29},"01M6HSA77QYVP7A72HREGTDN2C","algorithmic-art","Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fplugins\u002Falgorithmic-art\u002FSKILL.md",[131],{"categoryNo":102,"categoryName":103,"taxonomyType":69,"taxonomyTypeDesc":70},[133,134,135,113,114,136,137,138,139,86,140,141,142,143,27,144,145,146,147,148,123],"algorithmic art","Art","algorithmic","flow","js","work","interactive","generative art","exploration","systems","users","Existing","request","generative","copyright","fields",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":153,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":29},"01M6HS9HE0X390Y6RQKTY1YNGJ","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Ftheme-factory\u002FSKILL.md",[156],{"categoryNo":102,"categoryName":103,"taxonomyType":69,"taxonomyTypeDesc":70},[158,159,160,161,162,163,74,164,165,166,117,167,168,119,169,27,170,171,172,91,173,174],"theme factory","factory","theme","docs","toolkit","generate","SET","fly","slides","styling","artifact","themes","you","fonts","can","apply","new",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":184,"publishedAt":29},"01M6HS74GASM6FJ77F83EY679E","browsing","Use when you need direct browser control - teaches Chrome DevTools Protocol for controlling existing browser sessions, multi-tab management, form automation, and content extraction via use_browser MCP tool","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fsuperpowers-chrome\u002Fskills\u002Fbrowsing\u002FSKILL.md",[181],{"categoryNo":182,"categoryName":183,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000023","Skill与智能体开发",[177,185,186,187,188,189,190,191,192,193,194,86,195,196,197,198,90,170,91,144],"MCP","automation","chrome","sessions","protocol","browser","devtools","chrome devtools","tool","direct","browser control","control","via","form",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":62,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":212,"publishedAt":29},"01M6HS6BZT2CKDNQ6YF20DXN4T","slack-gif-creator","Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like \"make me a GIF of X doing Y for Slack.\"","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fwelflau\u002Fai-dev-system\u002Fblob\u002Fmain\u002Fbackend\u002Fskills\u002Fmarketplace\u002Fcodebuddy-plugins-official\u002Fexternal_plugins\u002Fslack-gif-creator\u002FSKILL.md",[206,209],{"categoryNo":207,"categoryName":208,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000005","邮件与沟通",{"categoryNo":210,"categoryName":211,"taxonomyType":69,"taxonomyTypeDesc":70},"01JBSEEDCAT000000000000016","图像与多媒体",[213,214,215,216,217,218,219,220,221,86,222,143,223,224,225,91,145,123],"slack gif creator","slack","gif","creator","validation","Tools","constraints","Animation","knowledge","me","make","Utilities","concepts"]