[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M799TCXCSF5CDPZAT91WYG46":3,"skill-same:01M799TCXCSF5CDPZAT91WYG46":50},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M799TCXCSF5CDPZAT91WYG46","test-cases",null,"This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.","ahang1598\u002Fdoubao-workbuddy-qwenwork-skills","ahang1598","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29569469?v=4","01M787BTDDPJN7G0C9TC9SQ85J","01M787BTE3YMSPS4EBYF2MCE1Z",98,"MIT","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fofficial_experts\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: test-cases\ndescription: This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.\nlicense: MIT\n---\n\n# Test Cases Generator\n\nThis skill generates comprehensive, requirement-driven test cases from PRD documents or user requirements.\n\n## Purpose\n\nTransform product requirements into structured test cases that ensure complete coverage of functionality, edge cases, error scenarios, and state transitions. The skill follows a pragmatic testing philosophy: test what matters, ensure every requirement has corresponding test coverage, and maintain test quality over quantity.\n\n## When to Use\n\nTrigger this skill when:\n- User provides a PRD or requirements document and requests test cases\n- User asks to \"generate test cases\", \"create test scenarios\", or \"plan QA\"\n- User mentions testing coverage for a feature or requirement\n- User needs structured test documentation in markdown format\n\n## Core Testing Principles\n\nFollow these principles when generating test cases:\n\n1. **Requirement-driven, not implementation-driven** - Test cases must map directly to requirements, not implementation details\n2. **Complete coverage** - Every requirement must have at least one test case covering:\n   - Happy path (normal use cases)\n   - Edge cases (boundary values, empty inputs, max limits)\n   - Error handling (invalid inputs, failure scenarios, permission errors)\n   - State transitions (if stateful, cover all valid state changes)\n3. **Clear and actionable** - Each test case must be executable by a QA engineer without ambiguity\n4. **Traceable** - Maintain clear mapping between requirements and test cases\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nFirst, identify the source of requirements:\n\n1. If user provides a file path to a PRD, read it using the Read tool\n2. If user describes requirements verbally, capture them\n3. If requirements are unclear or incomplete, use AskUserQuestion to clarify:\n   - What are the core user flows?\n   - What are the acceptance criteria?\n   - What are the edge cases or error scenarios to consider?\n   - Are there any state transitions or workflows?\n   - What platforms or environments need testing?\n\n### Step 2: Extract Test Scenarios\n\nAnalyze requirements and extract test scenarios:\n\n1. **Functional scenarios** - Normal use cases from requirements\n2. **Edge case scenarios** - Boundary conditions, empty states, maximum limits\n3. **Error scenarios** - Invalid inputs, permission failures, network errors\n4. **State transition scenarios** - If the feature involves state, map all transitions\n\nFor each requirement, identify:\n- Preconditions (what must be true before testing)\n- Test steps (actions to perform)\n- Expected results (what should happen)\n- Postconditions (state after test completes)\n\n### Step 3: Structure Test Cases\n\nOrganize test cases using this structure:\n\n```markdown\n# Test Cases: [Feature Name]\n\n## Overview\n- **Feature**: [Feature name]\n- **Requirements Source**: [PRD file path or description]\n- **Test Coverage**: [Summary of what's covered]\n- **Last Updated**: [Date]\n\n## Test Case Categories\n\n### 1. Functional Tests\nTest cases covering normal user flows and core functionality.\n\n#### TC-F-001: [Test Case Title]\n- **Requirement**: [Link to specific requirement]\n- **Priority**: [High\u002FMedium\u002FLow]\n- **Preconditions**:\n  - [Condition 1]\n  - [Condition 2]\n- **Test Steps**:\n  1. [Step 1]\n  2. [Step 2]\n  3. [Step 3]\n- **Expected Results**:\n  - [Expected result 1]\n  - [Expected result 2]\n- **Postconditions**: [State after test]\n\n### 2. Edge Case Tests\nTest cases covering boundary conditions and unusual inputs.\n\n#### TC-E-001: [Test Case Title]\n[Same structure as above]\n\n### 3. Error Handling Tests\nTest cases covering error scenarios and failure modes.\n\n#### TC-ERR-001: [Test Case Title]\n[Same structure as above]\n\n### 4. State Transition Tests\nTest cases covering state changes and workflows (if applicable).\n\n#### TC-ST-001: [Test Case Title]\n[Same structure as above]\n\n## Test Coverage Matrix\n\n| Requirement ID | Test Cases | Coverage Status |\n|---------------|------------|-----------------|\n| REQ-001 | TC-F-001, TC-E-001 | ✓ Complete |\n| REQ-002 | TC-F-002 | ⚠ Partial |\n\n## Notes\n- [Any additional testing considerations]\n- [Known limitations or assumptions]\n```\n\n### Step 4: Generate Test Cases\n\nFor each identified scenario, create a detailed test case following the structure above. Ensure:\n\n1. **Unique IDs** - Use prefixes: TC-F (functional), TC-E (edge), TC-ERR (error), TC-ST (state)\n2. **Clear titles** - Descriptive titles that explain what's being tested\n3. **Requirement traceability** - Link each test case to specific requirements\n4. **Priority assignment** - Mark critical paths as High priority\n5. **Executable steps** - Steps must be clear enough for any QA engineer to execute\n6. **Measurable results** - Expected results must be verifiable\n\n### Step 5: Validate Coverage\n\nBefore finalizing, verify:\n\n1. Every requirement has at least one test case\n2. Happy path is covered for all user flows\n3. Edge cases are identified for boundary conditions\n4. Error scenarios are covered for failure modes\n5. State transitions are tested if feature is stateful\n\nIf coverage gaps exist, generate additional test cases.\n\n### Step 6: Output Test Cases\n\nWrite the test cases to `tests\u002F\u003Cname>-test-cases.md` where `\u003Cname>` is derived from:\n- The feature name from the PRD\n- The user's specified name\n- A sanitized version of the requirement title\n\nUse the Write tool to create the file with the structured test cases.\n\n### Step 7: Summary\n\nAfter generating test cases, provide a brief summary in Chinese:\n- Total number of test cases generated\n- Coverage breakdown (functional, edge, error, state)\n- Any assumptions made or areas needing clarification\n- File path where test cases were saved\n\n## Quality Checklist\n\nBefore finalizing test cases, verify:\n\n- [ ] Every requirement has corresponding test cases\n- [ ] Happy path scenarios are covered\n- [ ] Edge cases include boundary values, empty inputs, max limits\n- [ ] Error handling covers invalid inputs and failure scenarios\n- [ ] State transitions are tested if applicable\n- [ ] Test case IDs are unique and follow naming convention\n- [ ] Test steps are clear and executable\n- [ ] Expected results are measurable and verifiable\n- [ ] Coverage matrix shows complete coverage\n- [ ] File is written to tests\u002F\u003Cname>-test-cases.md\n\n## Example Usage\n\n**User**: \"Generate test cases for the user authentication feature in docs\u002Fauth-prd.md\"\n\n**Process**:\n1. Read docs\u002Fauth-prd.md\n2. Extract requirements: login, logout, password reset, session management\n3. Identify scenarios: successful login, invalid credentials, expired session, etc.\n4. Generate test cases covering all scenarios\n5. Write to tests\u002Fauth-test-cases.md\n6. Summarize coverage in Chinese\n\n## References\n\nFor detailed testing methodologies and best practices, see:\n- `references\u002Ftesting-principles.md` - Core testing principles and patterns\n","# Test Cases Generator\n\nThis skill generates comprehensive, requirement-driven test cases from PRD documents or user requirements.\n\n## Purpose\n\nTransform product requirements into structured test cases that ensure complete coverage of functionality, edge cases, error scenarios, and state transitions. The skill follows a pragmatic testing philosophy: test what matters, ensure every requirement has corresponding test coverage, and maintain test quality over quantity.\n\n## When to Use\n\nTrigger this skill when:\n- User provides a PRD or requirements document and requests test cases\n- User asks to \"generate test cases\", \"create test scenarios\", or \"plan QA\"\n- User mentions testing coverage for a feature or requirement\n- User needs structured test documentation in markdown format\n\n## Core Testing Principles\n\nFollow these principles when generating test cases:\n\n1. **Requirement-driven, not implementation-driven** - Test cases must map directly to requirements, not implementation details\n2. **Complete coverage** - Every requirement must have at least one test case covering:\n   - Happy path (normal use cases)\n   - Edge cases (boundary values, empty inputs, max limits)\n   - Error handling (invalid inputs, failure scenarios, permission errors)\n   - State transitions (if stateful, cover all valid state changes)\n3. **Clear and actionable** - Each test case must be executable by a QA engineer without ambiguity\n4. **Traceable** - Maintain clear mapping between requirements and test cases\n\n## Workflow\n\n### Step 1: Gather Requirements\n\nFirst, identify the source of requirements:\n\n1. If user provides a file path to a PRD, read it using the Read tool\n2. If user describes requirements verbally, capture them\n3. If requirements are unclear or incomplete, use AskUserQuestion to clarify:\n   - What are the core user flows?\n   - What are the acceptance criteria?\n   - What are the edge cases or error scenarios to consider?\n   - Are there any state transitions or workflows?\n   - What platforms or environments need testing?\n\n### Step 2: Extract Test Scenarios\n\nAnalyze requirements and extract test scenarios:\n\n1. **Functional scenarios** - Normal use cases from requirements\n2. **Edge case scenarios** - Boundary conditions, empty states, maximum limits\n3. **Error scenarios** - Invalid inputs, permission failures, network errors\n4. **State transition scenarios** - If the feature involves state, map all transitions\n\nFor each requirement, identify:\n- Preconditions (what must be true before testing)\n- Test steps (actions to perform)\n- Expected results (what should happen)\n- Postconditions (state after test completes)\n\n### Step 3: Structure Test Cases\n\nOrganize test cases using this structure:\n\n```markdown\n# Test Cases: [Feature Name]\n\n## Overview\n- **Feature**: [Feature name]\n- **Requirements Source**: [PRD file path or description]\n- **Test Coverage**: [Summary of what's covered]\n- **Last Updated**: [Date]\n\n## Test Case Categories\n\n### 1. Functional Tests\nTest cases covering normal user flows and core functionality.\n\n#### TC-F-001: [Test Case Title]\n- **Requirement**: [Link to specific requirement]\n- **Priority**: [High\u002FMedium\u002FLow]\n- **Preconditions**:\n  - [Condition 1]\n  - [Condition 2]\n- **Test Steps**:\n  1. [Step 1]\n  2. [Step 2]\n  3. [Step 3]\n- **Expected Results**:\n  - [Expected result 1]\n  - [Expected result 2]\n- **Postconditions**: [State after test]\n\n### 2. Edge Case Tests\nTest cases covering boundary conditions and unusual inputs.\n\n#### TC-E-001: [Test Case Title]\n[Same structure as above]\n\n### 3. Error Handling Tests\nTest cases covering error scenarios and failure modes.\n\n#### TC-ERR-001: [Test Case Title]\n[Same structure as above]\n\n### 4. State Transition Tests\nTest cases covering state changes and workflows (if applicable).\n\n#### TC-ST-001: [Test Case Title]\n[Same structure as above]\n\n## Test Coverage Matrix\n\n| Requirement ID | Test Cases | Coverage Status |\n|---------------|------------|-----------------|\n| REQ-001 | TC-F-001, TC-E-001 | ✓ Complete |\n| REQ-002 | TC-F-002 | ⚠ Partial |\n\n## Notes\n- [Any additional testing considerations]\n- [Known limitations or assumptions]\n```\n\n### Step 4: Generate Test Cases\n\nFor each identified scenario, create a detailed test case following the structure above. Ensure:\n\n1. **Unique IDs** - Use prefixes: TC-F (functional), TC-E (edge), TC-ERR (error), TC-ST (state)\n2. **Clear titles** - Descriptive titles that explain what's being tested\n3. **Requirement traceability** - Link each test case to specific requirements\n4. **Priority assignment** - Mark critical paths as High priority\n5. **Executable steps** - Steps must be clear enough for any QA engineer to execute\n6. **Measurable results** - Expected results must be verifiable\n\n### Step 5: Validate Coverage\n\nBefore finalizing, verify:\n\n1. Every requirement has at least one test case\n2. Happy path is covered for all user flows\n3. Edge cases are identified for boundary conditions\n4. Error scenarios are covered for failure modes\n5. State transitions are tested if feature is stateful\n\nIf coverage gaps exist, generate additional test cases.\n\n### Step 6: Output Test Cases\n\nWrite the test cases to `tests\u002F\u003Cname>-test-cases.md` where `\u003Cname>` is derived from:\n- The feature name from the PRD\n- The user's specified name\n- A sanitized version of the requirement title\n\nUse the Write tool to create the file with the structured test cases.\n\n### Step 7: Summary\n\nAfter generating test cases, provide a brief summary in Chinese:\n- Total number of test cases generated\n- Coverage breakdown (functional, edge, error, state)\n- Any assumptions made or areas needing clarification\n- File path where test cases were saved\n\n## Quality Checklist\n\nBefore finalizing test cases, verify:\n\n- [ ] Every requirement has corresponding test cases\n- [ ] Happy path scenarios are covered\n- [ ] Edge cases include boundary values, empty inputs, max limits\n- [ ] Error handling covers invalid inputs and failure scenarios\n- [ ] State transitions are tested if applicable\n- [ ] Test case IDs are unique and follow naming convention\n- [ ] Test steps are clear and executable\n- [ ] Expected results are measurable and verifiable\n- [ ] Coverage matrix shows complete coverage\n- [ ] File is written to tests\u002F\u003Cname>-test-cases.md\n\n## Example Usage\n\n**User**: \"Generate test cases for the user authentication feature in docs\u002Fauth-prd.md\"\n\n**Process**:\n1. Read docs\u002Fauth-prd.md\n2. Extract requirements: login, logout, password reset, session management\n3. Identify scenarios: successful login, invalid credentials, expired session, etc.\n4. Generate test cases covering all scenarios\n5. Write to tests\u002Fauth-test-cases.md\n6. Summarize coverage in Chinese\n\n## References\n\nFor detailed testing methodologies and best practices, see:\n- `references\u002Ftesting-principles.md` - Core testing principles and patterns\n",{"name":5,"license":14,"description":7},"main","5e45653f59a2e4a2a65f575e8aaf7637165674d5","workbuddy\u002Fofficial_experts\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases",39,"https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills","https:\u002F\u002Fgithub.com\u002Fahang1598","2026-11-06 15:01:27",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add ahang1598\u002Fdoubao-workbuddy-qwenwork-skills --skill test-cases",{"tool":36,"command":37},"bunx","bunx skills add ahang1598\u002Fdoubao-workbuddy-qwenwork-skills --skill test-cases",{"tool":39,"command":40},"pnpm","pnpm dlx skills add ahang1598\u002Fdoubao-workbuddy-qwenwork-skills --skill test-cases","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fofficial_experts\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002FSKILL.md",true,[44],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"references\u002Ftesting-principles.md","REFERENCE","参考文档",7977,"https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fofficial_experts\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002Freferences\u002Ftesting-principles.md",[51,59,68,75,83,91],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":55,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79AD9QRFFSMWE9ZHAV6049W","xiaoyi-pdf-win","PDF 综合处理技能，处理文档生成、编辑、安全与解析。 适用情形： 1. 创建与排版：从零生成报告、提案、简历等 PDF，或对现有文档重新排版美化； 2. 表单与水印：自动填写 PDF 表单字段，或添加文字\u002F图片水印（如打水印、标机密）； 3. 页面管理：合并多个 PDF，或拆分、提取指定页码； 4. 安全控制：为 PDF 添加密码（加密）或移除密码（解密）； 5. 内容提取：从 PDF 中提取纯文本或导出表格数据。 只要用户诉求涉及生成、排版、美化、转换、拼接、拆分 PDF，或处理水印、表单、密码，必须触发本技能。","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fskills\u002Fxiaoyi-pdf-win\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fskills\u002Fxiaoyi-pdf-win\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":63,"licenseFileUrl":64,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79A6AXW44V3H0DVPHXE32YE","skill-creator-win","Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fskills\u002Fskill-creator-win\u002Flicense.txt","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fskills\u002Fskill-creator-win\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79A5DRYQNS61T7W9TA1ZNPY","markitdown-win","Convert files and office documents to Markdown. Supports PDF, DOCX, PPTX, XLSX, images (with OCR), audio (with transcription), HTML, CSV, JSON, XML, ZIP, YouTube URLs, EPubs and more.","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fskills\u002Fmarkitdown-win\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M79A35XSZGH60W5XQE6CR0Q5","minimax-docx","Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill\u002Fedit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say \"write a report\", \"draft a proposal\", \"make a contract\", \"fill in this form\", \"reformat to match this template\", or any task whose final output is a .docx file. Even if the user doesn't mention \"docx\" explicitly, if the task implies a printable\u002Fformal document, use this skill.","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fexperts\u002Fdocument-generation-expert\u002Fskills\u002Fminimax-docx\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fxiaoyiwork\u002Fexperts\u002Fdocument-generation-expert\u002Fskills\u002Fminimax-docx\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M79A1WEZ6HQWMH6KDE32Q928","skillhub-daily","SkillHub 每日推荐 - 扫描 skillhub.cn 全站 Top100 + 7 大分类各 Top20（共 240 个 Skill），\n基于用户痛点精准推荐高价值 Skill，支持 IMA\u002F飞书\u002FObsidian 多通道存储。\n触发词：每日推荐、SkillHub 日报、潜力Skill、帮我推荐技能。\n支持两种使用模式：常规 Skills 模式（对话触发）\u002F Cron 定时任务模式。","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fskills\u002Fskillhub-daily\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fskills\u002Fskillhub-daily\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M799ZCAYFF5A73KRC4G4VMWX","deep-research","Structured deep research workflow with human-in-the-loop control. Use \u002Fresearch to generate research outline, \u002Fresearch-deep for parallel web search across items, \u002Fresearch-report to compile markdown reports. Supports academic research, benchmark research, technology selection, market analysis, and due diligence. Triggers: 'deep research', 'research topic', 'benchmark comparison', 'technology survey', 'market analysis'. Requires: WebSearch capability.","https:\u002F\u002Fgithub.com\u002Fahang1598\u002Fdoubao-workbuddy-qwenwork-skills\u002Fblob\u002Fmain\u002Fworkbuddy\u002Fskills\u002Fdeep-research\u002FSKILL.md",[],[]]