Loading...
Loading...
Found 3,072 Skills
pytest, data validation, Great Expectations, and quality assurance for data systems
Set up the Pica CLI and MCP server so AI agents can interact with Gmail, Slack, HubSpot, Stripe, and 200+ platforms. Handles installation, initialization, and first connection.
自动生成全面的测试套件，包括单元测试、集成测试和E2E测试，支持Jest、Vitest、pytest、xUnit等。
List all available Recur skills and how to use them. Use this when the user asks questions like "what can Recur do", "Recur skills", "what functions does Recur have", "help with Recur", "how to use Recur skills".
Validates the interoperability between skills. Ensures that output formats (JSON/Markdown) from one skill are correctly consumed by the next in a chain.
Use when implementing features or fixes - test-driven development with RED-GREEN-REFACTOR cycle and full code coverage requirement
Analyze and extract relevant patterns, best practices, and usage examples from fetched documentation for implementation guidance.
Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases.
Wiring Verification
Use this skill when you need to write, review, or debug automated tests for applications built on the Jazz framework. This skill provides the correct architectural patterns for simulating local-first synchronization and multi-user environments without resorting to invalid mocking strategies.
Write tests for Dojo models and systems using spawn_test_world, cheat codes, and assertions. Use when testing game logic, verifying state changes, or ensuring system correctness.
Go testing patterns for production-grade code: subtests, test helpers, fixtures, golden files, httptest, testcontainers, property-based testing, and fuzz testing. Covers mocking strategies, test isolation, coverage analysis, and test design philosophy. Use when writing tests, improving coverage, reviewing test quality, setting up test infrastructure, or choosing a testing approach. Trigger examples: "add tests", "improve coverage", "write tests for this", "test helpers", "mock this dependency", "integration test", "fuzz test". Do NOT use for performance benchmarking methodology (use go-performance-review), security testing (use go-security-audit), or table-driven test patterns specifically (use go-test-table-driven).