[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KB3C2R2KX6HSAKYG12XP7A":3,"skill-same:01M6KB3C2R2KX6HSAKYG12XP7A":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6KB3C2R2KX6HSAKYG12XP7A","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.","zhizhunbao\u002Fworkbuddy","zhizhunbao","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7111063?v=4","01M6K6S4GJ0HA544MFAKAB913B","王鹏","01M6K6S4MEC7KW1Z6SCQ3FA876",9,"MIT","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketplaces\u002Fcodebuddy-plugins-official\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"test cases","test","generation","request","functional","error","case","users","triggers","scenario","creation","requirements","prd","edge","qa","state","error handling","planning","documents","documentation","2026-11-10 10:12:30",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":15,"description":7},"main","469e430d8b1f61ccc1bf502e5448161944831c41","plugins\u002Fmarketplaces\u002Fcodebuddy-plugins-official\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases",4,"https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy","https:\u002F\u002Fgithub.com\u002Fzhizhunbao","2026-04-01 01:41:45",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add zhizhunbao\u002Fworkbuddy --skill test-cases",{"tool":62,"command":63},"bunx","bunx skills add zhizhunbao\u002Fworkbuddy --skill test-cases",{"tool":65,"command":66},"pnpm","pnpm dlx skills add zhizhunbao\u002Fworkbuddy --skill test-cases","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketplaces\u002Fcodebuddy-plugins-official\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Ftesting-principles.md","REFERENCE","参考文档",7977,"https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fplugins\u002Fmarketplaces\u002Fcodebuddy-plugins-official\u002Fplugins\u002Foh-my-codebuddy\u002Fskills\u002Ftest-cases\u002Freferences\u002Ftesting-principles.md",[77,107,133,161,195,220],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":86,"publishedAt":44},"01M6KBS51KPHYV6GXA7KEH7MMX","skill-scanner","Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Fskill-scanner\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"skill scanner","scanner","security scanner","debugging","code","analysis","credentials","vulnerability","analyze","only","windsurf","local","project","chain","skill audit","tencent","you","inspect","static","skill security",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":44},"01M6KBRQP7C41T5SQ72SJXZWP6","shader-dev","Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Fshader-dev\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,26,123,124,125,126,127,128,129,130,131,132],"dev","shader","shader dev","graphics","fluid","Ray","simulation","lighting","visual","modeling","post","processing","GLSL","procedural","post-processing","more","techniques","for","effects",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":143,"publishedAt":44},"01M6KBRAQBPFT9HRKNPCC7EJZP","react-native-dev","React Native and Expo development guide covering components, styling, animations, navigation,\nstate management, forms, networking, performance optimization, testing, native capabilities,\nand engineering (project structure, deployment, SDK upgrades, CI\u002FCD).\nUse when: building React Native or Expo apps, implementing animations or native UI, managing\nstate, fetching data, writing tests, optimizing performance, deploying to App Store\u002FPlay Store,\nsetting up CI\u002FCD, upgrading Expo SDK, or configuring Tailwind\u002FNativeWind.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Freact-native-dev\u002FSKILL.md",[139,140],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":141,"categoryName":142,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[144,114,145,146,147,148,149,150,151,43,152,153,154,155,156,99,157,158,159,160],"react","react native","native","react native dev","testing","writing","performance","components","capabilities","ci","Tailwind","up","structure","app","apps","implementing","app store",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":175,"publishedAt":44},"01M6KBQM1S3B60WHYE0JN5ZFGB","pptx-generator","Generate, edit, and read PowerPoint presentations. Create from scratch with PptxGenJS (cover, TOC, content, section divider, summary slides), edit existing PPTX via XML workflows, or extract text with markitdown. Triggers: PPT, PPTX, PowerPoint, presentation, slide, deck, slides.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Fpptx-generator\u002FSKILL.md",[167,170],{"categoryNo":168,"categoryName":169,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,32,192,193,194],"pptx","generator","pptx generator","workflows","presentations","powerpoint","create","generate","slides","生成","text","演示","read","edit","toc","deck","io","presentation","cover",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":205,"publishedAt":44},"01M6KBP6H9EGBC7P4N0ZF2NPDZ","minimax-xlsx","Open, create, read, analyze, edit, or validate Excel\u002Fspreadsheet files (.xlsx, .xlsm, .csv, .tsv). Use when the user asks to create, build, modify, analyze, read, validate, or format any Excel spreadsheet, financial model, pivot table, or tabular data file. Covers: creating new xlsx from scratch, reading and analyzing existing files, editing existing xlsx with zero format loss, formula recalculation and validation, and applying professional financial formatting standards. Triggers on 'spreadsheet', 'Excel', '.xlsx', '.csv', 'pivot table', 'financial model', 'formula', or any request to produce tabular data in Excel format.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Fminimax-xlsx\u002FSKILL.md",[201,204],{"categoryNo":202,"categoryName":203,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000004","电子表格",{"categoryNo":171,"categoryName":172,"taxonomyType":173,"taxonomyTypeDesc":174},[206,207,208,43,209,182,210,211,212,213,95,214,188,189,215,216,217,218,219,27],"xlsx","minimax","minimax xlsx","spreadsheets","analyzing","data","spreadsheet","open","model","files","formula","excel spreadsheets","professional","reading",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":235,"publishedAt":44},"01M6KBP08N725KPCCF3BWRV47Y","minimax-pdf","Use this skill when visual quality and design identity matter for a PDF. CREATE (generate from scratch): \"make a PDF\", \"generate a report\", \"write a proposal\", \"create a resume\", \"beautiful PDF\", \"professional document\", \"cover page\", \"polished PDF\", \"client-ready document\". FILL (complete form fields): \"fill in the form\", \"fill out this PDF\", \"complete the form fields\", \"write values into PDF\", \"what fields does this PDF have\". REFORMAT (apply design to an existing doc): \"reformat this document\", \"apply our style\", \"convert this Markdown\u002Ftext to PDF\", \"make this doc look good\", \"re-style this PDF\". This skill uses a token-based design system: color, typography, and spacing are derived from the document type and flow through every page. The output is print-ready. Prefer this skill when appearance matters, not just when any PDF output is needed.","https:\u002F\u002Fgithub.com\u002Fzhizhunbao\u002Fworkbuddy\u002Fblob\u002Fmain\u002Fskills-marketplace\u002Fskills\u002Fminimax-pdf\u002FSKILL.md",[226,229,232],{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":230,"categoryName":231,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":233,"categoryName":234,"taxonomyType":173,"taxonomyTypeDesc":174},"01JBSEEDCAT000000000000032","设计师",[236,207,237,238,42,182,183,239,240,241,186,242,243,244,245,246,218,247,248,249],"PDF","minimax pdf","design","flow","doc","markdown","write","good","ready","token","proposal","re","spacing","document-generation"]