[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CYBBKAHJJ85JC2PS380TGZ":3,"skill-same:01M6CYBBKAHJJ85JC2PS380TGZ":70},{"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":22,"publishedAt":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":13,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":39,"install":40,"resources":53},"01M6CYBBKAHJJ85JC2PS380TGZ","workflows-compound",null,"Document a recently solved problem to compound your team's knowledge","The-Rabak\u002Fnaysmith","The-Rabak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44833742?v=4","01M6CY211HB58Y8JNWWEV9FGN1","01M6CY8HJW3TE1AQW1F13PHYB2",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-compound\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[23,24,25,26,27,28],"workflows","workflows compound","compound","team","knowledge","document","2026-11-10 10:12:30",false,"---\nname: workflows-compound\ndescription: Document a recently solved problem to compound your team's knowledge\n---\n\n## Arguments\n[optional: brief context about the fix]\n\n# \u002Fcompound\n\nCoordinate multiple subagents working in parallel to document a recently solved problem.\n\n## Purpose\n\nCaptures problem solutions while context is fresh, creating structured documentation in `docs\u002Fsolutions\u002F` with YAML frontmatter for searchability and future reference. Uses parallel subagents for maximum efficiency.\n\n**Why \"compound\"?** Each documented solution compounds your team's knowledge. The first time you solve a problem takes research. Document it, and the next occurrence takes minutes. Knowledge compounds.\n\n## Usage\n\n```bash\n\u002Fworkflows-compound                    # Document the most recent fix\n\u002Fworkflows-compound [brief context]    # Provide additional context hint\n```\n\n## Execution Strategy: Two-Phase Orchestration\n\n\u003Ccritical_requirement>\n**Only ONE file gets written - the final documentation.**\n\nPhase 1 subagents return TEXT DATA to the orchestrator. They must NOT use Write, Edit, or create any files. Only the orchestrator (Phase 2) writes the final documentation file.\n\u003C\u002Fcritical_requirement>\n\n### Phase 1: Parallel Research\n\n\u003Cparallel_tasks>\n\nLaunch these subagents IN PARALLEL. Each returns text data to the orchestrator.\n\n#### 1. **Context Analyzer**\n   - Extracts conversation history\n   - Identifies problem type, component, symptoms\n   - Validates against schema\n   - Returns: YAML frontmatter skeleton\n\n#### 2. **Solution Extractor**\n   - Analyzes all investigation steps\n   - Identifies root cause\n   - Extracts working solution with code examples\n   - Returns: Solution content block\n\n#### 3. **Related Docs Finder**\n   - Searches `docs\u002Fsolutions\u002F` for related documentation\n   - Identifies cross-references and links\n   - Finds related GitHub issues\n   - Returns: Links and relationships\n\n#### 4. **Prevention Strategist**\n   - Develops prevention strategies\n   - Creates best practices guidance\n   - Generates test cases if applicable\n   - Returns: Prevention\u002Ftesting content\n\n#### 5. **Category Classifier**\n   - Determines optimal `docs\u002Fsolutions\u002F` category\n   - Validates category against schema\n   - Suggests filename based on slug\n   - Returns: Final path and filename\n\n#### 6. **Execution Session Analyzer**\n   - Searches `docs\u002Fexecution-sessions\u002F` for recent session files related to the current fix\n   - Reads session files and extracts recurring patterns (e.g., same error across multiple tasks)\n   - Identifies problems that were encountered and how they were fixed during execution\n   - Cross-references with the current problem being documented\n   - Returns: Execution context and recurring patterns\n\n\u003C\u002Fparallel_tasks>\n\n### Phase 2: Assembly & Write\n\n\u003Csequential_tasks>\n\n**WAIT for all Phase 1 subagents to complete before proceeding.**\n\nThe orchestrating agent (main conversation) performs these steps:\n\n1. Collect all text results from Phase 1 subagents\n   **Include execution session learnings:** If the Execution Session Analyzer found relevant session files, incorporate execution learnings into the documentation:\n   - Add an \"## Execution Context\" section if problems were first discovered during task execution\n   - Include the progression of how the problem was encountered and resolved across multiple task attempts\n   - Reference the session file path for traceability (e.g., `docs\u002Fexecution-sessions\u002Fwork-2026-02-19-143022\u002Ftask-03-create-auth-service.md`)\n2. Assemble complete markdown file from the collected pieces\n3. Validate YAML frontmatter against schema\n4. Create directory if needed: `mkdir -p docs\u002Fsolutions\u002F[category]\u002F`\n5. Write the SINGLE final file: `docs\u002Fsolutions\u002F[category]\u002F[filename].md`\n\n\u003C\u002Fsequential_tasks>\n\n### Phase 3: Optional Enhancement\n\n**WAIT for Phase 2 to complete before proceeding.**\n\n\u003Cparallel_tasks>\n\nBased on problem type, optionally invoke specialized agents to review the documentation:\n\n- **performance_issue** → `performance-oracle`\n- **security_issue** → `security-sentinel`\n- **database_issue** → `data-integrity-guardian`\n- **test_failure** → `rabak-laravel-reviewer` + `code-simplicity-reviewer`\n- Any code-heavy issue → `rabak-laravel-reviewer` + `code-simplicity-reviewer`\n\n\u003C\u002Fparallel_tasks>\n\n## What It Captures\n\n- **Problem symptom**: Exact error messages, observable behavior\n- **Investigation steps tried**: What didn't work and why\n- **Root cause analysis**: Technical explanation\n- **Working solution**: Step-by-step fix with code examples\n- **Prevention strategies**: How to avoid in future\n- **Cross-references**: Links to related issues and docs\n- **Execution session learnings**: Patterns and fixes discovered during `\u002Fworkflows-work` task execution (from `docs\u002Fexecution-sessions\u002F`)\n\n## Preconditions\n\n\u003Cpreconditions enforcement=\"advisory\">\n  \u003Ccheck condition=\"problem_solved\">\n    Problem has been solved (not in-progress)\n  \u003C\u002Fcheck>\n  \u003Ccheck condition=\"solution_verified\">\n    Solution has been verified working\n  \u003C\u002Fcheck>\n  \u003Ccheck condition=\"non_trivial\">\n    Non-trivial problem (not simple typo or obvious error)\n  \u003C\u002Fcheck>\n\u003C\u002Fpreconditions>\n\n## What It Creates\n\n**Organized documentation:**\n\n- File: `docs\u002Fsolutions\u002F[category]\u002F[filename].md`\n\n**Categories auto-detected from problem:**\n\n- build-errors\u002F\n- test-failures\u002F\n- runtime-errors\u002F\n- performance-issues\u002F\n- database-issues\u002F\n- security-issues\u002F\n- ui-bugs\u002F\n- integration-issues\u002F\n- logic-errors\u002F\n\n## Common Mistakes to Avoid\n\n| ❌ Wrong | ✅ Correct |\n|----------|-----------|\n| Subagents write files like `context-analysis.md`, `solution-draft.md` | Subagents return text data; orchestrator writes one final file |\n| Research and assembly run in parallel | Research completes → then assembly runs |\n| Multiple files created during workflow | Single file: `docs\u002Fsolutions\u002F[category]\u002F[filename].md` |\n\n## Success Output\n\n```\n✓ Documentation complete\n\nSubagent Results:\n  ✓ Context Analyzer: Identified performance_issue in brief_system\n  ✓ Solution Extractor: 3 code fixes\n  ✓ Related Docs Finder: 2 related issues\n  ✓ Prevention Strategist: Prevention strategies, test suggestions\n  ✓ Category Classifier: `performance-issues`\n  ✓ Execution Session Analyzer: Found 2 related session files, 1 recurring pattern\n\nSpecialized Agent Reviews (Auto-Triggered):\n  ✓ performance-oracle: Validated query optimization approach\n  ✓ rabak-laravel-reviewer: Code examples meet project standards\n  ✓ code-simplicity-reviewer: Solution is appropriately minimal\n  ✓ code-simplicity-reviewer: Solution is appropriately minimal\n\nFile created:\n- docs\u002Fsolutions\u002Fperformance-issues\u002Fn-plus-one-brief-generation.md\n\nThis documentation will be searchable for future reference when similar\nissues occur in the Email Processing or Brief System modules.\n\nWhat's next?\n1. Continue workflow (recommended)\n2. Link related documentation\n3. Update other references\n4. View documentation\n5. Other\n```\n\n## The Compounding Philosophy\n\nThis creates a compounding knowledge system:\n\n1. First time you solve \"N+1 query in brief generation\" → Research (30 min)\n2. Document the solution → docs\u002Fsolutions\u002Fperformance-issues\u002Fn-plus-one-briefs.md (5 min)\n3. Next time similar issue occurs → Quick lookup (2 min)\n4. Knowledge compounds → Team gets smarter\n\nThe feedback loop:\n\n```\nBuild → Execute (session files) → Test → Find Issue → Research → Improve → Document → Validate → Deploy\n    ↑                                                                                              ↓\n    └──────────────────────────────────────────────────────────────────────────────────────────────┘\n```\n\n**Each unit of engineering work should make subsequent units of work easier—not harder.**\n\n## Auto-Invoke\n\n\u003Cauto_invoke> \u003Ctrigger_phrases> - \"that worked\" - \"it's fixed\" - \"working now\" - \"problem solved\" \u003C\u002Ftrigger_phrases>\n\n\u003Cmanual_override> Use \u002Fworkflows-compound [context] to document immediately without waiting for auto-detection. \u003C\u002Fmanual_override> \u003C\u002Fauto_invoke>\n\n## Routes To\n\n`compound-docs` skill\n\n## Applicable Specialized Agents\n\nBased on problem type, these agents can enhance documentation:\n\n### Code Quality & Review\n- **rabak-laravel-reviewer**: Reviews code examples for Laravel best practices\n- **code-simplicity-reviewer**: Ensures solution code is minimal and clear\n- **pattern-recognition-specialist**: Identifies anti-patterns or repeating issues\n\n### Specific Domain Experts\n- **performance-oracle**: Analyzes performance_issue category solutions\n- **security-sentinel**: Reviews security_issue solutions for vulnerabilities\n- **rabak-laravel-reviewer**: Reviews code examples for prevention test strategies\n- **data-integrity-guardian**: Reviews database_issue migrations and queries\n\n### Enhancement & Documentation\n- **best-practices-researcher**: Enriches solution with industry best practices\n- **rabak-vue-reviewer**: Reviews frontend code for Vue.js conventions\n- **framework-docs-researcher**: Links to Laravel\u002Fpackage documentation references\n\n### When to Invoke\n- **Auto-triggered** (optional): Agents can run post-documentation for enhancement\n- **Manual trigger**: User can invoke agents after \u002Fworkflows-compound completes for deeper review\n- **Customize agents**: Edit `compound-engineering.local.md` or invoke the `setup` skill to configure which review agents are used across all workflows\n\n## Related Commands\n\n- `\u002Fresearch [topic]` - Deep investigation (searches docs\u002Fsolutions\u002F for patterns)\n- `\u002Fworkflows-plan` - Planning workflow (references documented solutions)\n","## Arguments\n[optional: brief context about the fix]\n\n# \u002Fcompound\n\nCoordinate multiple subagents working in parallel to document a recently solved problem.\n\n## Purpose\n\nCaptures problem solutions while context is fresh, creating structured documentation in `docs\u002Fsolutions\u002F` with YAML frontmatter for searchability and future reference. Uses parallel subagents for maximum efficiency.\n\n**Why \"compound\"?** Each documented solution compounds your team's knowledge. The first time you solve a problem takes research. Document it, and the next occurrence takes minutes. Knowledge compounds.\n\n## Usage\n\n```bash\n\u002Fworkflows-compound                    # Document the most recent fix\n\u002Fworkflows-compound [brief context]    # Provide additional context hint\n```\n\n## Execution Strategy: Two-Phase Orchestration\n\n\u003Ccritical_requirement>\n**Only ONE file gets written - the final documentation.**\n\nPhase 1 subagents return TEXT DATA to the orchestrator. They must NOT use Write, Edit, or create any files. Only the orchestrator (Phase 2) writes the final documentation file.\n\u003C\u002Fcritical_requirement>\n\n### Phase 1: Parallel Research\n\n\u003Cparallel_tasks>\n\nLaunch these subagents IN PARALLEL. Each returns text data to the orchestrator.\n\n#### 1. **Context Analyzer**\n   - Extracts conversation history\n   - Identifies problem type, component, symptoms\n   - Validates against schema\n   - Returns: YAML frontmatter skeleton\n\n#### 2. **Solution Extractor**\n   - Analyzes all investigation steps\n   - Identifies root cause\n   - Extracts working solution with code examples\n   - Returns: Solution content block\n\n#### 3. **Related Docs Finder**\n   - Searches `docs\u002Fsolutions\u002F` for related documentation\n   - Identifies cross-references and links\n   - Finds related GitHub issues\n   - Returns: Links and relationships\n\n#### 4. **Prevention Strategist**\n   - Develops prevention strategies\n   - Creates best practices guidance\n   - Generates test cases if applicable\n   - Returns: Prevention\u002Ftesting content\n\n#### 5. **Category Classifier**\n   - Determines optimal `docs\u002Fsolutions\u002F` category\n   - Validates category against schema\n   - Suggests filename based on slug\n   - Returns: Final path and filename\n\n#### 6. **Execution Session Analyzer**\n   - Searches `docs\u002Fexecution-sessions\u002F` for recent session files related to the current fix\n   - Reads session files and extracts recurring patterns (e.g., same error across multiple tasks)\n   - Identifies problems that were encountered and how they were fixed during execution\n   - Cross-references with the current problem being documented\n   - Returns: Execution context and recurring patterns\n\n\u003C\u002Fparallel_tasks>\n\n### Phase 2: Assembly & Write\n\n\u003Csequential_tasks>\n\n**WAIT for all Phase 1 subagents to complete before proceeding.**\n\nThe orchestrating agent (main conversation) performs these steps:\n\n1. Collect all text results from Phase 1 subagents\n   **Include execution session learnings:** If the Execution Session Analyzer found relevant session files, incorporate execution learnings into the documentation:\n   - Add an \"## Execution Context\" section if problems were first discovered during task execution\n   - Include the progression of how the problem was encountered and resolved across multiple task attempts\n   - Reference the session file path for traceability (e.g., `docs\u002Fexecution-sessions\u002Fwork-2026-02-19-143022\u002Ftask-03-create-auth-service.md`)\n2. Assemble complete markdown file from the collected pieces\n3. Validate YAML frontmatter against schema\n4. Create directory if needed: `mkdir -p docs\u002Fsolutions\u002F[category]\u002F`\n5. Write the SINGLE final file: `docs\u002Fsolutions\u002F[category]\u002F[filename].md`\n\n\u003C\u002Fsequential_tasks>\n\n### Phase 3: Optional Enhancement\n\n**WAIT for Phase 2 to complete before proceeding.**\n\n\u003Cparallel_tasks>\n\nBased on problem type, optionally invoke specialized agents to review the documentation:\n\n- **performance_issue** → `performance-oracle`\n- **security_issue** → `security-sentinel`\n- **database_issue** → `data-integrity-guardian`\n- **test_failure** → `rabak-laravel-reviewer` + `code-simplicity-reviewer`\n- Any code-heavy issue → `rabak-laravel-reviewer` + `code-simplicity-reviewer`\n\n\u003C\u002Fparallel_tasks>\n\n## What It Captures\n\n- **Problem symptom**: Exact error messages, observable behavior\n- **Investigation steps tried**: What didn't work and why\n- **Root cause analysis**: Technical explanation\n- **Working solution**: Step-by-step fix with code examples\n- **Prevention strategies**: How to avoid in future\n- **Cross-references**: Links to related issues and docs\n- **Execution session learnings**: Patterns and fixes discovered during `\u002Fworkflows-work` task execution (from `docs\u002Fexecution-sessions\u002F`)\n\n## Preconditions\n\n\u003Cpreconditions enforcement=\"advisory\">\n  \u003Ccheck condition=\"problem_solved\">\n    Problem has been solved (not in-progress)\n  \u003C\u002Fcheck>\n  \u003Ccheck condition=\"solution_verified\">\n    Solution has been verified working\n  \u003C\u002Fcheck>\n  \u003Ccheck condition=\"non_trivial\">\n    Non-trivial problem (not simple typo or obvious error)\n  \u003C\u002Fcheck>\n\u003C\u002Fpreconditions>\n\n## What It Creates\n\n**Organized documentation:**\n\n- File: `docs\u002Fsolutions\u002F[category]\u002F[filename].md`\n\n**Categories auto-detected from problem:**\n\n- build-errors\u002F\n- test-failures\u002F\n- runtime-errors\u002F\n- performance-issues\u002F\n- database-issues\u002F\n- security-issues\u002F\n- ui-bugs\u002F\n- integration-issues\u002F\n- logic-errors\u002F\n\n## Common Mistakes to Avoid\n\n| ❌ Wrong | ✅ Correct |\n|----------|-----------|\n| Subagents write files like `context-analysis.md`, `solution-draft.md` | Subagents return text data; orchestrator writes one final file |\n| Research and assembly run in parallel | Research completes → then assembly runs |\n| Multiple files created during workflow | Single file: `docs\u002Fsolutions\u002F[category]\u002F[filename].md` |\n\n## Success Output\n\n```\n✓ Documentation complete\n\nSubagent Results:\n  ✓ Context Analyzer: Identified performance_issue in brief_system\n  ✓ Solution Extractor: 3 code fixes\n  ✓ Related Docs Finder: 2 related issues\n  ✓ Prevention Strategist: Prevention strategies, test suggestions\n  ✓ Category Classifier: `performance-issues`\n  ✓ Execution Session Analyzer: Found 2 related session files, 1 recurring pattern\n\nSpecialized Agent Reviews (Auto-Triggered):\n  ✓ performance-oracle: Validated query optimization approach\n  ✓ rabak-laravel-reviewer: Code examples meet project standards\n  ✓ code-simplicity-reviewer: Solution is appropriately minimal\n  ✓ code-simplicity-reviewer: Solution is appropriately minimal\n\nFile created:\n- docs\u002Fsolutions\u002Fperformance-issues\u002Fn-plus-one-brief-generation.md\n\nThis documentation will be searchable for future reference when similar\nissues occur in the Email Processing or Brief System modules.\n\nWhat's next?\n1. Continue workflow (recommended)\n2. Link related documentation\n3. Update other references\n4. View documentation\n5. Other\n```\n\n## The Compounding Philosophy\n\nThis creates a compounding knowledge system:\n\n1. First time you solve \"N+1 query in brief generation\" → Research (30 min)\n2. Document the solution → docs\u002Fsolutions\u002Fperformance-issues\u002Fn-plus-one-briefs.md (5 min)\n3. Next time similar issue occurs → Quick lookup (2 min)\n4. Knowledge compounds → Team gets smarter\n\nThe feedback loop:\n\n```\nBuild → Execute (session files) → Test → Find Issue → Research → Improve → Document → Validate → Deploy\n    ↑                                                                                              ↓\n    └──────────────────────────────────────────────────────────────────────────────────────────────┘\n```\n\n**Each unit of engineering work should make subsequent units of work easier—not harder.**\n\n## Auto-Invoke\n\n\u003Cauto_invoke> \u003Ctrigger_phrases> - \"that worked\" - \"it's fixed\" - \"working now\" - \"problem solved\" \u003C\u002Ftrigger_phrases>\n\n\u003Cmanual_override> Use \u002Fworkflows-compound [context] to document immediately without waiting for auto-detection. \u003C\u002Fmanual_override> \u003C\u002Fauto_invoke>\n\n## Routes To\n\n`compound-docs` skill\n\n## Applicable Specialized Agents\n\nBased on problem type, these agents can enhance documentation:\n\n### Code Quality & Review\n- **rabak-laravel-reviewer**: Reviews code examples for Laravel best practices\n- **code-simplicity-reviewer**: Ensures solution code is minimal and clear\n- **pattern-recognition-specialist**: Identifies anti-patterns or repeating issues\n\n### Specific Domain Experts\n- **performance-oracle**: Analyzes performance_issue category solutions\n- **security-sentinel**: Reviews security_issue solutions for vulnerabilities\n- **rabak-laravel-reviewer**: Reviews code examples for prevention test strategies\n- **data-integrity-guardian**: Reviews database_issue migrations and queries\n\n### Enhancement & Documentation\n- **best-practices-researcher**: Enriches solution with industry best practices\n- **rabak-vue-reviewer**: Reviews frontend code for Vue.js conventions\n- **framework-docs-researcher**: Links to Laravel\u002Fpackage documentation references\n\n### When to Invoke\n- **Auto-triggered** (optional): Agents can run post-documentation for enhancement\n- **Manual trigger**: User can invoke agents after \u002Fworkflows-compound completes for deeper review\n- **Customize agents**: Edit `compound-engineering.local.md` or invoke the `setup` skill to configure which review agents are used across all workflows\n\n## Related Commands\n\n- `\u002Fresearch [topic]` - Deep investigation (searches docs\u002Fsolutions\u002F for patterns)\n- `\u002Fworkflows-plan` - Planning workflow (references documented solutions)\n",{"name":5,"description":7},"main","b097d394a335a9ec3c8a02d64e111f1a9c96703d",".github\u002Fskills\u002Fworkflows-compound","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith","https:\u002F\u002Fgithub.com\u002FThe-Rabak","2026-03-04 03:03:05",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add The-Rabak\u002Fnaysmith --skill workflows-compound",{"tool":46,"command":47},"bunx","bunx skills add The-Rabak\u002Fnaysmith --skill workflows-compound",{"tool":49,"command":50},"pnpm","pnpm dlx skills add The-Rabak\u002Fnaysmith --skill workflows-compound","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-compound\u002FSKILL.md",true,[54,60,64],{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"agents\u002Fopenai.yaml","REFERENCE","参考文档",223,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjbaehova\u002Fpdf-monster\u002Fskills\u002Fpdf-monster\u002Fagents\u002Fopenai.yaml",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"requirements.txt",14,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjbaehova\u002Fpdf-monster\u002Fskills\u002Fpdf-monster\u002Frequirements.txt",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"scripts\u002Fanalyze_pdf.py","SCRIPT","脚本",23659,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fjbaehova\u002Fpdf-monster\u002Fskills\u002Fpdf-monster\u002Fscripts\u002Fanalyze_pdf.py",[71,82,96,109,123,134],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":29},"01M6CYBMHFVAMC4T3J8QFYN42M","workflows-work","Execute work plans efficiently while maintaining quality and finishing features","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-work\u002FSKILL.md",[],[78,79,23,80,81],"workflows work","work","execute","quality",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":29},"01M6CYBJ1KP7W3X8HEG49KST9Q","workflows-review","Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-review\u002FSKILL.md",[],[89,23,90,91,92,93,94,95],"workflows review","review","thinking","worktrees","multi-agent","analysis","code",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":29},"01M6CYBEW8DDBXW62Q2CA29BPR","workflows-plan","Transform feature descriptions into well-structured project plans following conventions","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-plan\u002FSKILL.md",[],[23,103,104,105,106,107,108],"workflows plan","plan","project","structured","following conventions","conventions",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":29},"01M6CYB9062GMP8VSA7N7PB4NW","workflows-brainstorm","Explore requirements and approaches through collaborative dialogue before planning implementation","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-brainstorm\u002FSKILL.md",[],[116,117,23,118,119,120,121,122],"workflows brainstorm","brainstorm","planning","requirements","dialogue","implementation","explore",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":29},"01M6CYB6S7GKWH62CRV3K79MHW","triage","Triage and categorize findings for the CLI todo system","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[],[125,130,131,132,133],"cli","system","categorize","todo",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":29},"01M6CYB4GDXS6AYFH7NMJRTXP7","test-browser","Run browser tests on pages affected by current PR or branch","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftest-browser\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",[144,145,146,147,148,149],"test","browser","test browser","pr","run","branch"]