[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M714RXH8CFFC85QX4943VG3F":3,"skill-same:01M714RXH8CFFC85QX4943VG3F":62},{"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":18,"publishedAt":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":47,"install":48,"resources":61},"01M714RXH8CFFC85QX4943VG3F","tdd-workflows-tdd-red",null,"Generate failing tests for the TDD red phase to define expected behavior and edge cases.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Ftdd-workflows-tdd-red\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"workflows","tdd","tdd workflows tdd red","red","tdd workflows","2026","failing","phase","unknown","expected","for","tests","define","community","behavior","edge","generate","2026-11-10 10:12:30",false,"---\nname: tdd-workflows-tdd-red\ndescription: \"Generate failing tests for the TDD red phase to define expected behavior and edge cases.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\nWrite comprehensive failing tests following TDD red phase principles.\n\n[Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.]\n\n## Use this skill when\n\n- Starting the TDD red phase for new behavior\n- You need failing tests that capture expected behavior\n- You want edge case coverage before implementation\n\n## Do not use this skill when\n\n- You are in the green or refactor phase\n- You only need performance benchmarks\n- Tests must run against production systems\n\n## Instructions\n\n1. Identify behaviors, constraints, and edge cases.\n2. Generate failing tests that define expected outcomes.\n3. Ensure failures are due to missing behavior, not setup errors.\n4. Document how to run tests and verify failures.\n\n## Safety\n\n- Keep test data isolated and avoid production environments.\n- Avoid flaky external dependencies in the red phase.\n\n## Role\n\nGenerate failing tests using Task tool with subagent_type=\"unit-testing::test-automator\".\n\n## Prompt Template\n\n\"Generate comprehensive FAILING tests for: $ARGUMENTS\n\n## Core Requirements\n\n1. **Test Structure**\n   - Framework-appropriate setup (Jest\u002Fpytest\u002FJUnit\u002FGo\u002FRSpec)\n   - Arrange-Act-Assert pattern\n   - should_X_when_Y naming convention\n   - Isolated fixtures with no interdependencies\n\n2. **Behavior Coverage**\n   - Happy path scenarios\n   - Edge cases (empty, null, boundary values)\n   - Error handling and exceptions\n   - Concurrent access (if applicable)\n\n3. **Failure Verification**\n   - Tests MUST fail when run\n   - Failures for RIGHT reasons (not syntax\u002Fimport errors)\n   - Meaningful diagnostic error messages\n   - No cascading failures\n\n4. **Test Categories**\n   - Unit: Isolated component behavior\n   - Integration: Component interaction\n   - Contract: API\u002Finterface contracts\n   - Property: Mathematical invariants\n\n## Framework Patterns\n\n**JavaScript\u002FTypeScript (Jest\u002FVitest)**\n- Mock dependencies with `vi.fn()` or `jest.fn()`\n- Use `@testing-library` for React components\n- Property tests with `fast-check`\n\n**Python (pytest)**\n- Fixtures with appropriate scopes\n- Parametrize for multiple test cases\n- Hypothesis for property-based tests\n\n**Go**\n- Table-driven tests with subtests\n- `t.Parallel()` for parallel execution\n- Use `testify\u002Fassert` for cleaner assertions\n\n**Ruby (RSpec)**\n- `let` for lazy loading, `let!` for eager\n- Contexts for different scenarios\n- Shared examples for common behavior\n\n## Quality Checklist\n\n- Readable test names documenting intent\n- One behavior per test\n- No implementation leakage\n- Meaningful test data (not 'foo'\u002F'bar')\n- Tests serve as living documentation\n\n## Anti-Patterns to Avoid\n\n- Tests passing immediately\n- Testing implementation vs behavior\n- Complex setup code\n- Multiple responsibilities per test\n- Brittle tests tied to specifics\n\n## Edge Case Categories\n\n- **Null\u002FEmpty**: undefined, null, empty string\u002Farray\u002Fobject\n- **Boundaries**: min\u002Fmax values, single element, capacity limits\n- **Special Cases**: Unicode, whitespace, special characters\n- **State**: Invalid transitions, concurrent modifications\n- **Errors**: Network failures, timeouts, permissions\n\n## Output Requirements\n\n- Complete test files with imports\n- Documentation of test purpose\n- Commands to run and verify failures\n- Metrics: test count, coverage areas\n- Next steps for green phase\"\n\n## Validation\n\nAfter generation:\n1. Run tests - confirm they fail\n2. Verify helpful failure messages\n3. Check test independence\n4. Ensure comprehensive coverage\n\n## Example (Minimal)\n\n```typescript\n\u002F\u002F auth.service.test.ts\ndescribe('AuthService', () => {\n  let authService: AuthService;\n  let mockUserRepo: jest.Mocked\u003CUserRepository>;\n\n  beforeEach(() => {\n    mockUserRepo = { findByEmail: jest.fn() } as any;\n    authService = new AuthService(mockUserRepo);\n  });\n\n  it('should_return_token_when_valid_credentials', async () => {\n    const user = { id: '1', email: 'test@example.com', passwordHash: 'hashed' };\n    mockUserRepo.findByEmail.mockResolvedValue(user);\n\n    const result = await authService.authenticate('test@example.com', 'pass');\n\n    expect(result.success).toBe(true);\n    expect(result.token).toBeDefined();\n  });\n\n  it('should_fail_when_user_not_found', async () => {\n    mockUserRepo.findByEmail.mockResolvedValue(null);\n\n    const result = await authService.authenticate('none@example.com', 'pass');\n\n    expect(result.success).toBe(false);\n    expect(result.error).toBe('INVALID_CREDENTIALS');\n  });\n});\n```\n\nTest requirements: $ARGUMENTS\n","Write comprehensive failing tests following TDD red phase principles.\n\n[Extended thinking: Generates failing tests that properly define expected behavior using test-automator agent.]\n\n## Use this skill when\n\n- Starting the TDD red phase for new behavior\n- You need failing tests that capture expected behavior\n- You want edge case coverage before implementation\n\n## Do not use this skill when\n\n- You are in the green or refactor phase\n- You only need performance benchmarks\n- Tests must run against production systems\n\n## Instructions\n\n1. Identify behaviors, constraints, and edge cases.\n2. Generate failing tests that define expected outcomes.\n3. Ensure failures are due to missing behavior, not setup errors.\n4. Document how to run tests and verify failures.\n\n## Safety\n\n- Keep test data isolated and avoid production environments.\n- Avoid flaky external dependencies in the red phase.\n\n## Role\n\nGenerate failing tests using Task tool with subagent_type=\"unit-testing::test-automator\".\n\n## Prompt Template\n\n\"Generate comprehensive FAILING tests for: $ARGUMENTS\n\n## Core Requirements\n\n1. **Test Structure**\n   - Framework-appropriate setup (Jest\u002Fpytest\u002FJUnit\u002FGo\u002FRSpec)\n   - Arrange-Act-Assert pattern\n   - should_X_when_Y naming convention\n   - Isolated fixtures with no interdependencies\n\n2. **Behavior Coverage**\n   - Happy path scenarios\n   - Edge cases (empty, null, boundary values)\n   - Error handling and exceptions\n   - Concurrent access (if applicable)\n\n3. **Failure Verification**\n   - Tests MUST fail when run\n   - Failures for RIGHT reasons (not syntax\u002Fimport errors)\n   - Meaningful diagnostic error messages\n   - No cascading failures\n\n4. **Test Categories**\n   - Unit: Isolated component behavior\n   - Integration: Component interaction\n   - Contract: API\u002Finterface contracts\n   - Property: Mathematical invariants\n\n## Framework Patterns\n\n**JavaScript\u002FTypeScript (Jest\u002FVitest)**\n- Mock dependencies with `vi.fn()` or `jest.fn()`\n- Use `@testing-library` for React components\n- Property tests with `fast-check`\n\n**Python (pytest)**\n- Fixtures with appropriate scopes\n- Parametrize for multiple test cases\n- Hypothesis for property-based tests\n\n**Go**\n- Table-driven tests with subtests\n- `t.Parallel()` for parallel execution\n- Use `testify\u002Fassert` for cleaner assertions\n\n**Ruby (RSpec)**\n- `let` for lazy loading, `let!` for eager\n- Contexts for different scenarios\n- Shared examples for common behavior\n\n## Quality Checklist\n\n- Readable test names documenting intent\n- One behavior per test\n- No implementation leakage\n- Meaningful test data (not 'foo'\u002F'bar')\n- Tests serve as living documentation\n\n## Anti-Patterns to Avoid\n\n- Tests passing immediately\n- Testing implementation vs behavior\n- Complex setup code\n- Multiple responsibilities per test\n- Brittle tests tied to specifics\n\n## Edge Case Categories\n\n- **Null\u002FEmpty**: undefined, null, empty string\u002Farray\u002Fobject\n- **Boundaries**: min\u002Fmax values, single element, capacity limits\n- **Special Cases**: Unicode, whitespace, special characters\n- **State**: Invalid transitions, concurrent modifications\n- **Errors**: Network failures, timeouts, permissions\n\n## Output Requirements\n\n- Complete test files with imports\n- Documentation of test purpose\n- Commands to run and verify failures\n- Metrics: test count, coverage areas\n- Next steps for green phase\"\n\n## Validation\n\nAfter generation:\n1. Run tests - confirm they fail\n2. Verify helpful failure messages\n3. Check test independence\n4. Ensure comprehensive coverage\n\n## Example (Minimal)\n\n```typescript\n\u002F\u002F auth.service.test.ts\ndescribe('AuthService', () => {\n  let authService: AuthService;\n  let mockUserRepo: jest.Mocked\u003CUserRepository>;\n\n  beforeEach(() => {\n    mockUserRepo = { findByEmail: jest.fn() } as any;\n    authService = new AuthService(mockUserRepo);\n  });\n\n  it('should_return_token_when_valid_credentials', async () => {\n    const user = { id: '1', email: 'test@example.com', passwordHash: 'hashed' };\n    mockUserRepo.findByEmail.mockResolvedValue(user);\n\n    const result = await authService.authenticate('test@example.com', 'pass');\n\n    expect(result.success).toBe(true);\n    expect(result.token).toBeDefined();\n  });\n\n  it('should_fail_when_user_not_found', async () => {\n    mockUserRepo.findByEmail.mockResolvedValue(null);\n\n    const result = await authService.authenticate('none@example.com', 'pass');\n\n    expect(result.success).toBe(false);\n    expect(result.error).toBe('INVALID_CREDENTIALS');\n  });\n});\n```\n\nTest requirements: $ARGUMENTS\n",{"name":5,"risk":27,"source":32,"date_added":41,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Ftdd-workflows-tdd-red","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill tdd-workflows-tdd-red",{"tool":54,"command":55},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill tdd-workflows-tdd-red",{"tool":57,"command":58},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill tdd-workflows-tdd-red","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Ftdd-workflows-tdd-red\u002FSKILL.md",true,[],[63,87,113,123,136,155],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":74,"publishedAt":36},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":72,"taxonomyTypeDesc":73},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[75,76,77,78,79,80,81,82,83,84,85,86],"wechat search","wechat","search","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":36},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[94,95,96,97,98,99,77,100,101,102,103,104,105,106,107,108,109,110,111,112],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":36},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[120,121,94,105,106,107,108,98,77,110,122,111,112,104,102,101,100,109,99,97],"trend radar","radar","pulse",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":36},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[130,131,132,133,134,135],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":147,"publishedAt":36},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[142],{"categoryNo":143,"categoryName":144,"taxonomyType":145,"taxonomyTypeDesc":146},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[138,83,148,149,150,86,105,151,152,153,96,154,109],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":36},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[157,162,163,164,109,165,152,166,167,168,169,170],"status","play","go","latest","github","discover","control","cmd","volume"]