[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QHZ2NHAPR27VRDHEKYZ1FW":3,"skill-same:01M6QHZ2NHAPR27VRDHEKYZ1FW":87},{"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":33,"publishedAt":54,"linkOnly":55,"markdownContent":56,"markdownBody":57,"frontMatter":58,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":13,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":66,"install":67,"resources":80},"01M6QHZ2NHAPR27VRDHEKYZ1FW","frontend-code-review",null,"Comprehensive frontend code quality audit covering ESLint, robustness, side effects, and performance for React\u002FVue\u002FTaro projects. Should be used when the user needs a thorough code quality check — before committing, during PR review, after refactoring, or when inheriting someone else's code. Distinguished from staged-code-review which focuses on git staged changes pre-commit, this skill focuses on general frontend code quality auditing.","ImaginerLabs\u002Fskill-manager","ImaginerLabs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F214277308?v=4","01M6QGGDPNF15RMMT1RCFDH9FN","01M6QGGDTH5BY64DQ123NR8M33",0,"MIT","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ffrontend-code-review\u002FSKILL.md",[17,22,25,28],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53],"frontend","review","code review","frontend code review","code","effects","which","coding","projects","refactoring","code quality audit","vue","audit","code-review","git","pr","code quality","commit","react","performance","2026-11-10 10:12:30",false,"---\nname: frontend-code-review\ndescription: >-\n  Comprehensive frontend code quality audit covering ESLint, robustness, side effects, and performance for\n  React\u002FVue\u002FTaro projects. Should be used when the user needs a thorough code quality check — before\n  committing, during PR review, after refactoring, or when inheriting someone else's code.\n  Distinguished from staged-code-review which focuses on git staged changes pre-commit, this skill\n  focuses on general frontend code quality auditing.\ncategory: coding\nboundary:\n  vs_staged-code-review: \"staged-code-review focuses on pre-commit git staged changes, this skill focuses on general frontend code quality auditing\"\n---\n\n# Frontend Code Quality Review\n\n## Core Capability\n\nFull-spectrum code health check for frontend code, ensuring production-grade quality. Works with React, Vue, Taro, and other modern frontend frameworks.\n\nThe goal isn't just to find problems — it's to give the user a clear verdict: is this code safe to ship, and if not, what exactly needs fixing?\n\n## When to Use\n\n- Pre-commit self-check\n- Pre-PR-review preparation\n- Post-refactoring regression check\n- Quality assessment when inheriting code\n- Post-bug-fix verification\n\n## Related Skills\n\n| Skill                           | Relationship | Use case                                        |\n| ------------------------------- | ------------ | ----------------------------------------------- |\n| `staged-code-review`            | Upstream     | When reviewing staged changes before commit     |\n| `frontend-staged-bundle-review` | Parallel     | When also concerned about bundle size           |\n| `code-comment-writer`           | Downstream   | When review finds readability issues            |\n| `tech-stack-detection`          | Prerequisite | When project tech stack is unknown              |\n| `react-performance`             | Deeper dive  | When performance issues are found during review |\n\n---\n\n## Checklist\n\nFor the full detailed checklist with code examples, see [checklist.md](references\u002Fchecklist.md).\n\n### 1. Static Analysis (Lint & Fix)\n\nRun lint checks, prioritize fixing `no-unused-vars`, `no-undef`, `exhaustive-deps`. Only fix errors introduced by the current change — don't expand the diff.\n\n### 2. Robustness & Defensive Programming\n\nKey areas:\n\n- **TypeScript**: Complete interfaces, proper optional marking, default values\n- **Null safety**: Optional chaining `?.` and nullish coalescing `??`\n- **Boundary handling**: Empty arrays, division by zero, negative indices\n- **Async safety**: try-catch around awaits, loading\u002Ferror states\n- **Race conditions**: AbortController, cancellation flags, disabled buttons during loading\n\n### 3. Context & Side Effects\n\n- **Upstream impact**: When modifying shared components, check all consumers\n- **Effect cleanup**: Every `useEffect` subscription must have a cleanup function\n- **State pollution**: Never mutate props or global state objects directly\n- **Closure traps**: Ensure event callbacks reference the latest state values\n\n### 4. Performance\n\n- Render control: `React.memo`, `useMemo`, `useCallback` where needed\n- Frequency control: debounce\u002Fthrottle for search, scroll, resize\n- List rendering: stable, unique `key`\n- Code splitting: `React.lazy` for heavy components\n\n### 5. Framework-Specific Checks\n\n- **Vue**: Reactive traps, lifecycle cleanup, computed side effects, v-for + v-if\n- **Taro**: API compatibility, subpackage config, setData optimization, lifecycle hooks\n\n---\n\n## Workflow\n\n```\n1. Receive code (specified file or current context)\n       ↓\n2. Run ESLint check → auto-fix basic errors\n       ↓\n3. Deep analysis: robustness → side effects → performance\n       ↓\n4. Generate report with scoring\n       ↓\n5. Action recommendation: pass \u002F warn \u002F block\n```\n\n---\n\n## Output Format\n\n```markdown\n## Code Quality Review Report\n\n### Overview\n\n- **File**: `[filename]`\n- **Tech stack**: React \u002F Vue \u002F Taro\n- **Overall score**: ? Excellent (90+) \u002F ? Good (70-89) \u002F ? Needs work (\u003C70)\n\n---\n\n### 1. ESLint Check\n\n| Status  | Rule | Location | Description |\n| ------- | ---- | -------- | ----------- |\n| ✅ PASS | -    | -        | No errors   |\n\n**Fixes applied:**\n\n- [List auto-fixed issues]\n\n---\n\n### 2. Robustness Assessment\n\n#### Risk Items\n\n| Severity  | Location    | Issue   | Fix suggestion |\n| --------- | ----------- | ------- | -------------- |\n| ? High   | `file:line` | [issue] | [suggestion]   |\n| ? Medium | `file:line` | [issue] | [suggestion]   |\n\n---\n\n### 3. Side Effects & Context\n\n- **Upstream impact**: [analysis]\n- **Downstream impact**: [analysis]\n- **Global impact**: [analysis]\n\n---\n\n### 4. Performance Suggestions\n\n| Priority | Location    | Issue   | Suggestion   | Expected gain |\n| -------- | ----------- | ------- | ------------ | ------------- |\n| ? High  | `file:line` | [issue] | [suggestion] | [gain]        |\n\n---\n\n### Summary\n\n- **Blockers**: X (must fix)\n- **Warnings**: X (should fix)\n- **Suggestions**: X (nice to have)\n\n#### Action\n\n- [ ] ✅ Safe to commit (no blockers)\n- [ ] ⚠️ Fix warnings before commit\n- [ ] ❌ Must fix blockers before commit\n```\n\n---\n\n## Quick Reference\n\n| Problem         | Typical scenario                         | Solution                           |\n| --------------- | ---------------------------------------- | ---------------------------------- |\n| Null error      | `Cannot read property of undefined`      | Use `?.` optional chaining         |\n| Race condition  | Fast page switching causes data mismatch | AbortController to cancel requests |\n| Memory leak     | setState after unmount                   | useEffect cleanup function         |\n| Infinite render | useEffect dependency array error         | Check dependency completeness      |\n| Performance     | List rendering lag                       | Use key + React.memo               |\n\n### React\u002FVue Comparison\n\n| Check            | React                       | Vue                              |\n| ---------------- | --------------------------- | -------------------------------- |\n| Effect cleanup   | `useEffect` return function | `onUnmounted`                    |\n| Computed caching | `useMemo`                   | `computed`                       |\n| Callback caching | `useCallback`               | Not needed manually              |\n| State update     | `setState` \u002F `useState`     | `ref` \u002F `reactive`               |\n| Props validation | TypeScript interface        | `props` definition + `validator` |\n","# Frontend Code Quality Review\n\n## Core Capability\n\nFull-spectrum code health check for frontend code, ensuring production-grade quality. Works with React, Vue, Taro, and other modern frontend frameworks.\n\nThe goal isn't just to find problems — it's to give the user a clear verdict: is this code safe to ship, and if not, what exactly needs fixing?\n\n## When to Use\n\n- Pre-commit self-check\n- Pre-PR-review preparation\n- Post-refactoring regression check\n- Quality assessment when inheriting code\n- Post-bug-fix verification\n\n## Related Skills\n\n| Skill                           | Relationship | Use case                                        |\n| ------------------------------- | ------------ | ----------------------------------------------- |\n| `staged-code-review`            | Upstream     | When reviewing staged changes before commit     |\n| `frontend-staged-bundle-review` | Parallel     | When also concerned about bundle size           |\n| `code-comment-writer`           | Downstream   | When review finds readability issues            |\n| `tech-stack-detection`          | Prerequisite | When project tech stack is unknown              |\n| `react-performance`             | Deeper dive  | When performance issues are found during review |\n\n---\n\n## Checklist\n\nFor the full detailed checklist with code examples, see [checklist.md](references\u002Fchecklist.md).\n\n### 1. Static Analysis (Lint & Fix)\n\nRun lint checks, prioritize fixing `no-unused-vars`, `no-undef`, `exhaustive-deps`. Only fix errors introduced by the current change — don't expand the diff.\n\n### 2. Robustness & Defensive Programming\n\nKey areas:\n\n- **TypeScript**: Complete interfaces, proper optional marking, default values\n- **Null safety**: Optional chaining `?.` and nullish coalescing `??`\n- **Boundary handling**: Empty arrays, division by zero, negative indices\n- **Async safety**: try-catch around awaits, loading\u002Ferror states\n- **Race conditions**: AbortController, cancellation flags, disabled buttons during loading\n\n### 3. Context & Side Effects\n\n- **Upstream impact**: When modifying shared components, check all consumers\n- **Effect cleanup**: Every `useEffect` subscription must have a cleanup function\n- **State pollution**: Never mutate props or global state objects directly\n- **Closure traps**: Ensure event callbacks reference the latest state values\n\n### 4. Performance\n\n- Render control: `React.memo`, `useMemo`, `useCallback` where needed\n- Frequency control: debounce\u002Fthrottle for search, scroll, resize\n- List rendering: stable, unique `key`\n- Code splitting: `React.lazy` for heavy components\n\n### 5. Framework-Specific Checks\n\n- **Vue**: Reactive traps, lifecycle cleanup, computed side effects, v-for + v-if\n- **Taro**: API compatibility, subpackage config, setData optimization, lifecycle hooks\n\n---\n\n## Workflow\n\n```\n1. Receive code (specified file or current context)\n       ↓\n2. Run ESLint check → auto-fix basic errors\n       ↓\n3. Deep analysis: robustness → side effects → performance\n       ↓\n4. Generate report with scoring\n       ↓\n5. Action recommendation: pass \u002F warn \u002F block\n```\n\n---\n\n## Output Format\n\n```markdown\n## Code Quality Review Report\n\n### Overview\n\n- **File**: `[filename]`\n- **Tech stack**: React \u002F Vue \u002F Taro\n- **Overall score**: ? Excellent (90+) \u002F ? Good (70-89) \u002F ? Needs work (\u003C70)\n\n---\n\n### 1. ESLint Check\n\n| Status  | Rule | Location | Description |\n| ------- | ---- | -------- | ----------- |\n| ✅ PASS | -    | -        | No errors   |\n\n**Fixes applied:**\n\n- [List auto-fixed issues]\n\n---\n\n### 2. Robustness Assessment\n\n#### Risk Items\n\n| Severity  | Location    | Issue   | Fix suggestion |\n| --------- | ----------- | ------- | -------------- |\n| ? High   | `file:line` | [issue] | [suggestion]   |\n| ? Medium | `file:line` | [issue] | [suggestion]   |\n\n---\n\n### 3. Side Effects & Context\n\n- **Upstream impact**: [analysis]\n- **Downstream impact**: [analysis]\n- **Global impact**: [analysis]\n\n---\n\n### 4. Performance Suggestions\n\n| Priority | Location    | Issue   | Suggestion   | Expected gain |\n| -------- | ----------- | ------- | ------------ | ------------- |\n| ? High  | `file:line` | [issue] | [suggestion] | [gain]        |\n\n---\n\n### Summary\n\n- **Blockers**: X (must fix)\n- **Warnings**: X (should fix)\n- **Suggestions**: X (nice to have)\n\n#### Action\n\n- [ ] ✅ Safe to commit (no blockers)\n- [ ] ⚠️ Fix warnings before commit\n- [ ] ❌ Must fix blockers before commit\n```\n\n---\n\n## Quick Reference\n\n| Problem         | Typical scenario                         | Solution                           |\n| --------------- | ---------------------------------------- | ---------------------------------- |\n| Null error      | `Cannot read property of undefined`      | Use `?.` optional chaining         |\n| Race condition  | Fast page switching causes data mismatch | AbortController to cancel requests |\n| Memory leak     | setState after unmount                   | useEffect cleanup function         |\n| Infinite render | useEffect dependency array error         | Check dependency completeness      |\n| Performance     | List rendering lag                       | Use key + React.memo               |\n\n### React\u002FVue Comparison\n\n| Check            | React                       | Vue                              |\n| ---------------- | --------------------------- | -------------------------------- |\n| Effect cleanup   | `useEffect` return function | `onUnmounted`                    |\n| Computed caching | `useMemo`                   | `computed`                       |\n| Callback caching | `useCallback`               | Not needed manually              |\n| State update     | `setState` \u002F `useState`     | `ref` \u002F `reactive`               |\n| Props validation | TypeScript interface        | `props` definition + `validator` |\n",{"name":5,"boundary":59,"category":41,"description":7},{"vs_staged-code-review":60},"staged-code-review focuses on pre-commit git staged changes, this skill focuses on general frontend code quality auditing","main","b9a52d8e27455bdad953d64928696d028223ea1b","skills\u002Fcoding\u002Ffrontend-code-review","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FImaginerLabs","2026-04-18 16:27:13",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add ImaginerLabs\u002Fskill-manager --skill frontend-code-review",{"tool":73,"command":74},"bunx","bunx skills add ImaginerLabs\u002Fskill-manager --skill frontend-code-review",{"tool":76,"command":77},"pnpm","pnpm dlx skills add ImaginerLabs\u002Fskill-manager --skill frontend-code-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ffrontend-code-review\u002FSKILL.md",true,[81],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fchecklist.md","REFERENCE","参考文档",4677,"https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fcoding\u002Ffrontend-code-review\u002Freferences\u002Fchecklist.md",[88,117,138,166,192,216],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":98,"publishedAt":54},"01M6QJCB2SD5KHC41ZDQC0GA1T","meeting-minutes","Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fmeeting-minutes\u002FSKILL.md",[94,95],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":96,"categoryName":97,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000034","行政与办公人员",[99,100,101,102,103,104,105,106,107,108,90,61,109,110,111,112,113,114,115,116],"meeting minutes","meeting","minutes","writing","github","copilot","generate","decisions","meetings","up","agenda","actionable","concise","follow-up","tree","true","action","for",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":54},"01M6QJC71RRGTGNNFEHJG6S20G","documentation-writer","Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdocumentation-writer\u002FSKILL.md",[],[124,125,126,102,103,104,127,128,129,130,131,132,61,133,134,135,136,113,114,137],"documentation","documentation writer","writer","https","quality","technical","technical writer","expert","documentation expert","structure","authoring","software","principles","high",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":151,"publishedAt":54},"01M6QJC0V3C7C4R9768J1AJYWY","doc-coauthoring","Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fwriting\u002Fdoc-coauthoring\u002FSKILL.md",[144,147,148],{"categoryNo":145,"categoryName":146,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":149,"categoryName":150,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000036","内容创作者",[152,153,102,154,155,124,156,157,158,159,160,161,61,162,163,134,164,165,113,116],"doc coauthoring","doc","workflow","official","tasks","decision","write","context","proposals","guide","refine","iteration","trigger","co",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":178,"publishedAt":54},"01M6QJBJ0YPVEWGEXZH3PJRRTT","code-review-workflow","Executes comprehensive 4-phase code review: basic review, quality check, bundle analysis, and test coverage. Should be used when the user mentions comprehensive code review, checking code quality, or reviewing staged changes with multi-phase analysis. This is the comprehensive review workflow, distinct from focused skills like frontend-code-review, staged-code-review, or code-change-test-designer.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-review-workflow\u002FSKILL.md",[172,173,176,177],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":174,"categoryName":175,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},[36,35,154,38,179,180,34,181,182,50,47,183,184,185,186,187,188,189,190,191],"code review workflow","testing","test","change","analysis","check","coverage","quality check","basic","multi","comprehensive code review","with","phase",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":207,"publishedAt":54},"01M6QJB7XNHV3VEEQF4W7FMWF6","code-change-test-designer","Analyzes code changes and designs comprehensive test cases. Reads diffs, summarizes capability changes, and designs test cases covering main flows and edge cases. Should be used when the user mentions test coverage, designing tests for code changes, or analyzing diff\u002Fcommit for testing purposes. Distinguished from code-review-workflow which provides comprehensive review, this skill focuses on test case design for code changes.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Ftesting\u002Fcode-change-test-designer\u002FSKILL.md",[198,199,202,203,204],{"categoryNo":174,"categoryName":175,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":200,"categoryName":201,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},{"categoryNo":205,"categoryName":206,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000032","设计师",[181,182,38,208,209,180,210,211,154,51,47,212,185,213,61,214,215,40,116,191],"designer","code change test designer","design","diffs","edge","diff","tests","flows",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":54},"01M6QJB195WD7DCJWDMKWKB29S","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","https:\u002F\u002Fgithub.com\u002FImaginerLabs\u002Fskill-manager\u002Fblob\u002Fmain\u002Fskills\u002Fmeta-skills\u002Fskill-creator\u002FSKILL.md",[222],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},[224,225,53,226,155,227,228,229,230,231,183,232,233,234,61,235,236,113,116,218],"skill creator","creator","run evals","variance analysis","create","run","benchmark","Meta","improve","edit","evals","optimize","existing skill"]