1. 481Business Logic Testingmn-youssef/security-skillsUse when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.49
  2. 482File Upload and Ssrfmn-youssef/security-skillsUse when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. On apps you own or are authorized to test.49
  3. 483Injection Testingmn-youssef/security-skillsUse when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.49
  4. 484Spec Driven TestLoveforwa/spec-test.skillUse specification-based testing methodology for end-to-end testing of web applications. Use this skill when users request "test this feature", "check this feature completeness", "do E2E testing on this project", "test this web app with an agent", or directly mention spec-driven-test / specification-based testing. This skill also applies to scenarios where users want to automatically generate test specs and test cases from code, then execute tests through browser automation. Even if users don't explicitly mention "spec" or "test case", if they want to systematically and automatically test a spe32
  5. 485Spec Driven TestLoveforwa/spec-test.skill用规约驱动测试(specification-based testing)的方法对 web 应用做端到端测试。当用户说要"测试一下这个功能"、"检查一下这个功能的完整性"、"对这个项目做 E2E 测试"、"用 agent 测这个 web 应用"或者直接提到 spec-driven-test / specification-based testing 时使用这个 skill。也适用于用户希望基于代码自动生成测试规约和测试用例,然后通过浏览器自动化执行测试的场景。即使用户没有明确说"规约"或"测试用例"这些词,只要他想系统地、自动化地测试一个 web 项目的某个功能,都应该使用这个 skill。32
  6. 486Uw Unity Feature Scaffolddevdavv/unity-ai-workflowCreate a complete feature module with folder structure, Assembly Definition (.asmdef), test assembly, and namespace. Use when adding a new feature, system, or module to a Unity project. Triggers on requests like "create a new feature", "scaffold a module", "add a combat system", "I need a health system", "set up inventory", "create a new module for X", "add a new system", "new feature folder", or any task requiring new folders, assemblies, or namespaces for a gameplay feature — even when the user just names a system they want to build from scratch. Reads ProjectConfig.yaml for folder_strategy 47
  7. 487Uw Unity Test Runnerdevdavv/unity-ai-workflowGenerates EditMode and PlayMode tests using NUnit, mapped from GDD Gherkin scenarios. Use when writing tests, validating features, ensuring code quality, or verifying behavior after changes. Triggers on requests like "write tests for this", "test the health system", "add unit tests", "verify this works", "add PlayMode tests", "test this feature", "write integration tests", "make sure this doesn't break", "add test coverage", "TDD this feature", or any task involving test creation, test-driven development, or quality assurance. Maps Given/When/Then scenarios directly to test methods using NUnit47
  8. 488Testing and Qualitydynamics365ninja/d365fo-cliWrite and run D365FO tests — SysTestCase unit tests, the ATL acceptance library, and the offline gates (`validate xpp`, `validate references`, `lint`) that catch defects before a build. Invoke when the user asks how to test X++, add a unit test, assert on behaviour, or check code quality without a VM.49
  9. 489Condition Based Waitingobra/clankReplace arbitrary timeouts with condition polling for reliable async tests43
  10. 490Creating Skillsobra/clankTDD for process documentation - test with subagents before writing, iterate until bulletproof43
  11. 491Fan OutElliotJLT/Claude-Skill-PotionsOrchestration pattern for parallelizable tasks. When facing work that can be split into independent subtasks (research multiple topics, analyze multiple files, test multiple scenarios), spawn parallel agents and aggregate results. Use when subtasks have no dependencies on each other.62
  12. 492Loose EndsElliotJLT/Claude-Skill-PotionsBefore declaring work complete, checks for loose ends: unused imports, TODO comments created, missing tests, stale references, incomplete error handling. Activates after implementing features or fixes. The cleanup that always gets skipped.62
  13. 493PipelineElliotJLT/Claude-Skill-PotionsOrchestration pattern for sequential, dependent tasks. When work must flow through stages where each stage depends on the previous (design → implement → test → review), structure as a pipeline with explicit handoffs. Each stage completes before the next begins.62
  14. 494Power Calculationsdariia-m/my_claude_skillsPower, minimum detectable effect (MDE) and sample-size calculations in R for randomized experiments and survey experiments - two-arm and multi-arm designs with a shared control, ANCOVA vs change-score vs post-only, binary outcomes, within-subject differences, interactions/heterogeneity, clustered assignment, attrition and exclusions, and multiple-testing adjustment (per-test, Bonferroni bound, Holm/Romano-Wolf). Combines closed-form MDEs with Monte Carlo simulation of the exact pre-registered regression, including size checks. Use whenever the user asks for power calculations, an MDE table, "h36
  15. 495Prove ItElliotJLT/Claude-Skill-PotionsBefore declaring any task complete, actually verify the outcome. Run the code. Test the fix. Check the output. Claude's training optimizes for plausible-looking output, not verified-correct output. This skill forces the verification step that doesn't come naturally. No victory laps without proof.62
  16. 496Test Driven Development (TDD)obra/clankWrite the test first, watch it fail, write minimal code to pass43
  17. 497Testing Anti Patternsobra/clankNever test mock behavior. Never add test-only methods to production classes. Understand dependencies before mocking.43
  18. 498Testing Skills with Subagentsobra/clankRED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes43
  19. 499Acceptance Designokgrit/done-is-a-claimDefine executable acceptance for a bounded task before work or dispatch. Use when writing a worker brief, selecting success checks, or repairing an acceptance contract that cannot test the intended outcome.33
  20. 500Analyze Experiment Consolidatedamplitude/mcp-marketplaceDesigns A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.48
  21. 501Analyze Experimentsamplitude/mcp-marketplaceDesigns A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.48
  22. 502Implementing with Testsokgrit/done-is-a-claimImplement runtime behavior changes and bug fixes with meaningful before-and-after checks, preserved behavior and relevant regression evidence. Use while editing code; prose-only changes do not need a failing test.33
  23. 503Reading Measurementsokgrit/done-is-a-claimRead a number without being fooled by it: an exit code, a passing result file, a test count, a list size, a control run, a red or a green. Use before reporting any figure, before turning a test run into a verdict, before acting on 'N items are broken', and whenever two outputs or two counts of the same thing disagree.33
  24. 504Render QA and Surgical Changessaranambiar/hyperframes-video-agent-skillsVerify final video renders and make tiny safe edits without breaking approved sync, including proof frames, contact sheets, media probing, stale theme scans, exact timestamp checks, carryover-frame refreshes, and re-render-only-affected-scenes workflows. Use when a user asks for final QA, HD/render verification, a small text/audio/color change, or regression checks after approved timing.48
  25. 505Scene Continuity and Transitionssaranambiar/hyperframes-video-agent-skillsPreserve visual continuity across video scenes with previous-final-frame starts, camera swipes, carryover frames, transition QA, and boundary proofing. Use when a scene must begin from the exact last frame of a previous scene, when adding camera-move transitions, when replacing scene endings, or when debugging stale starting frames.48
  26. 506Test Enginekorchard333/claude-power-platform-communityPower Apps Test Engine + Playwright. Use when: E2E testing of Canvas Apps, Model-Driven Apps, or Power Pages; automated UI verification; regression testing in CI/CD pipelines; visual QA of deployed solutions.52
  27. 507Testingkorchard333/claude-power-platform-communityPower Platform Testing Strategy. Use when: writing unit tests, E2E tests, Vitest/Jest setup, Playwright, Canvas App testing, plugin testing with FakeXrmEasy, Solution Checker, accessibility testing with axe-core, CI/CD test integration.52
  28. 508Uat Coordinatorkorchard333/claude-power-platform-communityPower Platform Solution Consultant and UAT Coordinator (Ava). Use when: writing UAT scripts from acceptance criteria, coordinating test cycles, tracking defects, confirming UAT sign-off, bridging requirements and implementation review, demo preparation, user training documentation, change management. Trigger when user says "UAT", "test scripts", "user acceptance", "defect tracking", "demo prep", "training guide", or "sign-off".52
  29. 509Jwt Encodejsonwebtoken/jwt-skillsCreate and sign JSON Web Tokens (JWTs) for testing and development. Use when the user wants to generate, create, build, or sign a JWT — e.g. "create a JWT", "generate a test token", "sign this payload", "make a JWT with these claims", "build an access token". Supports HMAC, RSA, and ECDSA algorithms.23
  30. 510Run Simulationsratacat/claude-skillsUse BEFORE and AFTER running trading engine simulations. Helps with: (1) SETUP - choosing configs, selecting segments via segment collections, batch sizing (recommend 2,000-3,000 runs); (2) EXECUTION - running batch simulations with --collection; (3) ANALYSIS - comprehensive diagnostics after runs. Triggers on: 'run simulations', 'test configs', 'batch simulation', 'analyze sim results', 'which configs to test', 'how many segments', 'simulation setup'.59
  31. 511Test Browserratacat/claude-skillsRun browser tests on pages affected by current PR or branch59
  32. 512Xcode Testratacat/claude-skillsBuild and test iOS apps on simulator using XcodeBuildMCP59
  33. 513Macos Swiftpmrobinebers/skillsBuild, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.49
  34. 514Macos Test Triagerobinebers/skillsTriage macOS tests across Xcode and SwiftPM. Use when narrowing failures, explaining assertions or crashes, or separating setup from regressions.49
  35. 515Meshtastic Device Opsmeshtastic/meshtastic-mcpDiscover, connect to, drive, configure, observe, and flash Meshtastic devices through the Meshtastic MCP server. Use when an agent needs to bring up a radio (serial or TCP), read or change device/channel config, send messages, inspect the node DB, watch live packets/telemetry/logs via the recorder, recover a bricked device, or build/flash firmware. Covers the non-e2e MCP tool surface; for cross-plane device↔app testing use the `meshtastic-e2e` skill.23
  36. 516Meshtastic E2Emeshtastic/meshtastic-mcpClosed-loop end-to-end testing of a Meshtastic device and a Meshtastic app (Android, Apple, or the Compose desktop app) together. Use when validating that an action on the radio (send a text, change config, a node beacon, a power-cycle) surfaces correctly in the app UI, or that an action in the app produces the correct on-air/on-device result. Drives the firmware device via the Meshtastic MCP server and the app via the Android CLI (`android` + `adb`), the Apple toolchain (`xcrun simctl` + `idb`), or the Compose Hot Reload MCP server for desktop, then cross-asserts one plane against the other.23
  37. 517Trellis Delivery Controller Zhcoldwateryi/trellis-skillsTrellis 需求交付总入口和流程控制器。用于用户希望只调用一个 Trellis skill 自动判断当前阶段,并在需求分析、MVP 任务规划、MVP 后差距审计、交付 loop、TDD 实现、系统调试、双阶段评审和最终验收之间进行路由、推进和安全门控制的场景。适合基于 trellis-zero-to-mvp-zh、trellis-mvp-to-delivery-zh、trellis-implement-tdd-zh、trellis-debug-systematic-zh 和 trellis-review-twostage-zh 形成端到端交付闭环。44
  38. 518Trellis Implement TDDcoldwateryi/trellis-skillsImplement a Trellis subtask using strict TDD (RED→GREEN→REFACTOR), turning acceptance criteria into code one by one. Used when Codex / Claude Code drives a small-parameter model like qwen3.6 35b—transforms "understand and implement requirements" into a mechanical "make this failing test green" loop with objective signals at every step.44
  39. 519Trellis Implement TDD Zhcoldwateryi/trellis-skills在 Trellis 子任务进入实现阶段时,用严格 TDD(红→绿→重构)逐条把验收标准落成代码。用于 Codex / Claude Code 等在 trellis-zero-to-mvp-zh 或 trellis-mvp-to-delivery-zh 生成主子任务后,按依赖顺序实现某个子任务,尤其当执行模型是 qwen3.6 35b 这类小参数本地模型时——把"理解并实现需求"转成"让这条失败测试变绿"的机械循环,每步都有客观信号。44
  40. 520Trellis Mvp to Deliverycoldwateryi/trellis-skillsAudit an existing MVP against a source requirements document and run a sustainable Trellis delivery loop. Use when Codex is asked to continue after an MVP, complete remaining requirements, perform a first full gap audit, maintain a Requirements Traceability Matrix, classify DONE/PARTIAL/MISSING/UNTESTED/UNCLEAR items, initialize or update .trellis/delivery-state.md, choose full/delta/early-exit audit scope, plan bounded gap-closing batches, require worktree + verifier gates, design automated test coverage, classify discovered bugs, or run final acceptance before delivery.44
  41. 521Engineering Grillrohitg00/agentbrainUse when an engineering plan needs pressure-testing for architecture, complexity, data, risk, and operability.43
  42. 522Godot Test Debuggerhhhh124hhhh/godot-mcpGodot 测试与调试工作流专家,支持自然语言描述自动完成单元测试、集成测试、错误诊断、性能调试等测试工作44
  43. 523Market Grillrohitg00/agentbrainUse when a product idea needs pressure-testing against alternatives, category, urgency, and distribution.43
  44. 524Problem Grillrohitg00/agentbrainUse when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing.43
  45. 525QA Evidencerohitg00/agentbrainUse when behavior needs concrete proof before review, merge, or shipment.43
  46. 526Executive MentorArogyaReddy/alirezarezvani-claude-skillsAdversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.40
  47. 527Lfe BuilderStChiotis/Library-First-EngineeringAct as the Builder for an LFE-compliant project. Use when implementing an approved plan, writing code in src/**, or running unit tests.44
  48. 528Lfe Mutation VerifyStChiotis/Library-First-EngineeringInspector sub-skill. Prompt-based mutation testing — reasons about whether existing tests would catch hypothetical code mutations. No test runner required. Writes .plans/checks/mutation_findings.md. Called by lfe-inspector when enabled in inspector-config.md. Enable only for critical or safety-sensitive modules.44