agentsclimarketplace

Test

10,627 rows, by stacks then stars

1,559 of these skill files have been read, by 1,201 distinct authors, and what they tell an agent counted. What Test authors agree on, and what they forbid

  • Webapp visual testing

    yeaight7/agent-powerups/skills/webapp-visual-testing Skill

    6★ repo

    Use when a browser-facing UI needs visual verification, a layout bug or visual regression is reported, accessibility of an interactive component needs checking, or a browser workflow must be exercised end-to-end.

  • Test driven development

    DYAI2025/Plumbline/config/claude/skills/test-driven-development Skill

    no license6★ repo

    Use when implementing a code task so the test is written or updated before production code and proves the requested behavior.

  • Testing anti patterns

    DYAI2025/Plumbline/config/claude/skills/testing-anti-patterns Skill

    no license6★ repo

    Use when reviewing tests for fragility, over-mocking, false positives, missing production wiring, or assertions that do not prove the requirement.

  • Counter experiment

    Wondermonger-daydreaming/claude-skills-library/skills/counter-experiment Skill

    6★ repo

    Design the experiments that would break or confirm a claim. Not critique (what's wrong) but generative opposition (what would you need to see). Given any empirical claim, hypothesis, or finding, generate 3-5 specific, feasible experiments that would distinguish between the proposed interpretation and simpler alternatives. Triggers on: 'what experiment would test this,' 'how would you break this,' 'design the falsification,' 'counter-experiment,' 'what would Reviewer 2 want to see,' 'what control is missing,' 'the experiment they didn't run,' or any moment when a claim needs empirical testing rather than rhetorical critique. Also triggers when a paper's interpretation could be distinguished from a simpler alternative by a specific experimental design.

  • Curie

    satsilem/claude-skills-pantheon/skills/curie Skill

    no license6★ repo

    Hypothesis-driven experimenter. Designs controlled tests to validate or invalidate ideas before committing to them. Use when an assumption, feature, or strategy should be tested rather than assumed — A/B tests, proofs of concept, feature flag rollouts, market validation, or any decision where evidence beats opinion. Triggers on: "Curie", "test this idea", "design an experiment", "how do I validate this", "should we prototype", "A/B test for", "MVP test", "prove this works", or whenever a user is about to commit to something they could test first. Do not invoke when speed is critical or the decision is already made.

  • Nietzsche

    satsilem/claude-skills-pantheon/skills/nietzsche Skill

    no license6★ repo

    Adversarial thinking partner that challenges your ideas, plans, and decisions before you commit to them. Default mode is constructive disagreement, not validation. Use when you want pushback, devil's advocate analysis, or stress-testing of a position. Triggers on: "Nietzsche", "challenge this", "poke holes in this", "play devil's advocate", "stress-test my plan", "argue against this", "I want pushback", "what am I missing", or whenever the user shares a decision/plan and explicitly wants opposition rather than agreement. Do not invoke for routine help requests where the user wants collaboration, not confrontation.

  • Seneca

    satsilem/claude-skills-pantheon/skills/seneca Skill

    no license6★ repo

    Risk and resilience preparation. Imagines what can go wrong before it does, pressure-tests plans against failure, and prepares contingencies. Practices "premeditatio malorum" — premeditation of evils. Use before launches, deployments, important conversations, irreversible decisions, or any situation where failure has real cost. Triggers on: "Seneca", "what could go wrong", "pre-mortem", "stress-test for risk", "prepare for failure", "what's the worst case", "before we launch", "pre-launch check", "risk analysis", or whenever the user is about to commit to something with meaningful downside. Do not invoke for low-stakes decisions or when the user is already over-worrying.

  • Create playwright page objects

    jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Playwright/skills/create-playwright-page-objects Skill

    6★ repo

    Create BO page object classes in the ui-testing-library for a new migrated page. Follows the Page Object Model pattern: encapsulate selectors and interactions, never assert. Trigger: "create page objects for {Domain}".

  • Create playwright test data

    jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Playwright/skills/create-playwright-test-data Skill

    6★ repo

    Create Faker data classes and predefined data objects for a new entity in the ui-testing-library. These are imported by campaigns for consistent test data generation. Trigger: "create test data for {Domain}".

  • Write playwright campaigns

    jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Playwright/skills/write-playwright-campaigns Skill

    6★ repo

    Write Playwright test campaigns for a migrated entity: CRUD lifecycle, bulk actions, filter/sort, position reorder, and per-tab field verification. Campaigns live in the core repo and import page objects from ui-testing-library. Trigger: "write Playwright tests for {Domain}".

  • Insurance coverage gap premortem

    deciqAI/knowledge-skills/insurance-coverage-gap-premortem Skill

    6★ repo

    Activate when: an insurance agent should stress-test a client's coverage before a claim exposes a gap; 'is this client actually covered', policy review, exclusions/limits/underinsurance; E&O risk. Do NOT activate when: no coverage is being placed or reviewed. More: deciqai.com/s/insurance-coverage-gap-premortem

  • Lean startup

    deciqAI/knowledge-skills/lean-startup Skill

    6★ repo

    Activate when: user says 'lean startup', 'build-measure-learn', 'MVP', 'validated learning', 'pivot or persevere', 'should we just build it?', 'we need to test this idea before building', or 'how do we know if anyone wants this?'; team is about to build something significant before testing demand; a pivot decision is on the table after early data. Do NOT activate when: operating a known business model in known conditions (use execution frameworks instead); decision is below business-model level (button color, which CRM). More: deciqai.com/s/lean-startup

  • Mvp

    deciqAI/knowledge-skills/mvp Skill

    6★ repo

    Activate when: someone says 'MVP', 'minimum viable product', 'smoke test', 'concierge MVP', or 'Wizard of Oz'; a team is scoping a build and hasn't named the assumption they're testing; engineers are about to build for months on an unvalidated idea; someone asks 'what's the smallest thing we can ship?'. Do NOT activate when: the product already has validated PMF and the question is scaling or polishing; the deliverable is a contractual obligation already sold. More: deciqai.com/s/mvp

  • Seven questions test

    deciqAI/knowledge-skills/seven-questions-test Skill

    6★ repo

    Activate when: user says 'seven questions,' 'Zero to One test,' 'Thiel checklist,' 'should I start this business,' 'is this startup idea any good,' or 'stress-test my startup idea'; a business idea, pivot, product line, or funding decision is about to proceed on enthusiasm rather than evidence; a pitch or plan is strong on one dimension (usually technology or market size) and silent on the others; the user wants a structured go/no-go gate before committing capital, time, or reputation to a venture. Do NOT activate when: the venture is already running and the question is a single-dimension diagnosis (pricing, one channel, one hire) — use the specific skill for that dimension instead; the decision is a small reversible experiment where a full seven-question gate is heavier than the bet itself; the user asked only to polish pitch wording, not to test whether the underlying business should exist. More: deciqai.com/s/seven-questions-test

  • The mom test

    deciqAI/knowledge-skills/the-mom-test Skill

    6★ repo

    Activate when: a founder is about to talk to customers/users to validate an idea; 'I asked people and they loved it', 'how do I run customer interviews', 'is there demand for this?', pre-PMF discovery. Do NOT activate when: the question is quantitative A/B testing on an existing product (use analytics), or the decision needs no customer input. More: deciqai.com/s/the-mom-test

  • Hexaco personality test

    l4ci/latticework/skills/hexaco-personality-test Skill

    6★ repo

    Use when the user wants a HEXACO personality assessment, or a Big Five test that also measures Honesty-Humility. Administers the public-domain 240-item IPIP-HEXACO questionnaire conversationally across six factors (Honesty-Humility, Emotionality, eXtraversion, Agreeableness, Conscientiousness, Openness) and their 24 facets, scores it, and writes a detailed markdown report. Triggers include "HEXACO test", "HEXACO personality", "Honesty-Humility", "Big Five plus honesty", "six-factor personality assessment".

  • Key assumptions check

    l4ci/latticework/skills/key-assumptions-check Skill

    6★ repo

    Use when an analysis, plan, estimate, or forecast rests on things being taken for granted, and the user wants to find the load-bearing assumptions before one of them breaks. Runs the Key Assumptions Check (KAC), a core structured analytic technique: surfaces the full set of assumptions in parallel from several stances, restates each as an explicit testable proposition, stress-tests each one for confidence and the conditions under which it fails, classifies them as solid, caveated, or unsupported, and names the few linchpin assumptions that would collapse the conclusion if wrong. Triggers include "key assumptions check", "what are we assuming", "what is this resting on", "check our assumptions", "what if we're wrong about", "pressure-test this plan's premises".

  • Ocean personality test

    l4ci/latticework/skills/ocean-personality-test Skill

    6★ repo

    Use when the user wants to take a Big Five (OCEAN) personality test or asks to assess their personality across Openness, Conscientiousness, Extraversion, Agreeableness, and Neuroticism. Administers the public-domain 50-item IPIP questionnaire conversationally, scores it, and writes a detailed markdown report. Triggers include "OCEAN test", "Big Five", "personality assessment", "what's my personality type".

  • Android device testing

    GuillemRoca/agent-skills-android/skills/android-device-testing Skill

    6★ repo

    Use when writing or debugging instrumented tests (Espresso, UI Automator, Compose test rules), using ADB, managing emulators, or inspecting UI with Layout Inspector.

  • Android e2e verification

    GuillemRoca/agent-skills-android/skills/android-e2e-verification Skill

    6★ repo

    Use when a feature slice needs proof it works end-to-end on a device, or when closing the implement → run → assert loop for any UI-facing change. Maestro YAML flows turn acceptance criteria into executable checks that run against release builds locally, in CI, and via MCP from the agent.

  • Test driven development

    GuillemRoca/agent-skills-android/skills/test-driven-development Skill

    6★ repo

    Use when implementing new features or fixing bugs. Write tests before implementation following Red-Green-Refactor. Covers JUnit5, MockK, Compose test rules, and the Prove-It pattern for bugs.

  • Socratic

    Shogo1222/socratic/skills/socratic Skill

    6★ repo

    Orchestrate the complete human-confirmed intent-testing workflow by using Maieutic to expose uncertainty, confirm intent, and propose missing tests (applied only on explicit request), then using Elenchus to challenge those tests with risk-directed mutations, and deliver the canonical review surface (Review This / We Verified / Still at Risk / Copy-ready Comments). Use for Feature Review or Refactor Guard of pull requests, local diffs, or AI-generated changes, or requests such as「変更の意図確認からMutation検証までやって」「人間の判断だけ聞いてテストを強化して」「AI生成PRをレビューして」「Socraticワークフローを実行して」.

  • Ccdawn bdd tdd development

    CCDawn/codex-skills/skills/engineering/ccdawn-bdd-tdd-development Skill

    6★ repo

    Use when an already-defined new behavior or high-risk implementation contract needs a failing test before implementation, or the user explicitly requests TDD; diagnosed bugs stay with ccdawn-bug-review, while simple or mechanical work uses targeted verification.

  • Ccdawn code structure guard

    CCDawn/codex-skills/skills/engineering/ccdawn-code-structure-guard Skill

    6★ repo

    Use when active development or explicit refactoring has concrete code-structure risk: a source file is accumulating independently changing responsibilities, a class/component/function is hard to navigate or test, repeated changes touch distant sections, or the user asks to split a giant file; do not use for line count alone, generated/vendor/migration/schema/fixture files, or cohesive modules that remain easier to maintain together.

  • Ccdawn project review

    CCDawn/codex-skills/skills/engineering/ccdawn-project-review Skill

    6★ repo

    Use when CCDawn workflow needs a Chinese-first review of an entire repository, codebase, architecture, technical debt, test coverage, risk modules, maintainability, onboarding state, or project health before planning, refactoring, takeover, or prioritization.

  • Arimunandar ios testing

    JordanCoin/ios-skills-collection/skills/arimunandar--ios-testing Skill

    no license6★ repo

    Unit testing, UI testing, TDD patterns, mocking, and test doubles for VIP+W architecture

    The same file is in 1 other repository

  • Avdlee swift testing expert

    JordanCoin/ios-skills-collection/skills/avdlee--swift-testing-expert Skill

    no license6★ repo

    Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects.

    The same file is in 28 other repositories

  • Bocato swift testing

    JordanCoin/ios-skills-collection/skills/bocato--swift-testing Skill

    no license6★ repo

    Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot tests, (5) migrating from XCTest to Swift Testing, (6) TDD, Arrange-Act-Assert, or F.I.R.S.T. principles, (7) parameterized tests or test organization.

    The same file is in 9 other repositories

  • Dimillian review swarm

    JordanCoin/ios-skills-collection/skills/dimillian--review-swarm Skill

    no license6★ repo

    Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.

  • Dpearson2699 swift testing

    JordanCoin/ios-skills-collection/skills/dpearson2699--swift-testing Skill

    no license6★ repo

    Write and migrate tests using the Swift Testing framework with @Test, @Suite, #expect, #require, confirmation, parameterized tests, test tags, traits, withKnownIssue, XCTest UI testing, XCUITest, test plan, mocking, test doubles, testable architecture, snapshot testing, async test patterns, test organization, and test-driven development in Swift. Use when writing or migrating tests with Swift Testing framework, implementing parameterized tests, working with test traits, converting XCTest to Swift Testing, or setting up test organization and mocking patterns.

  • Eronred ab test store listing

    JordanCoin/ios-skills-collection/skills/eronred--ab-test-store-listing Skill

    no license6★ repo

    When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

    The same file is in 2 other repositories

  • Eronred app analytics

    JordanCoin/ios-skills-collection/skills/eronred--app-analytics Skill

    no license6★ repo

    When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

    The same file is in 3 other repositories

  • Eronred app icon optimization

    JordanCoin/ios-skills-collection/skills/eronred--app-icon-optimization Skill

    no license6★ repo

    When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

    The same file is in 1 other repository

  • Eronred screenshot optimization

    JordanCoin/ios-skills-collection/skills/eronred--screenshot-optimization Skill

    no license6★ repo

    When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

    The same file is in 2 other repositories

  • Twostraws swift testing pro

    JordanCoin/ios-skills-collection/skills/twostraws--swift-testing-pro Skill

    no license6★ repo

    Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

    The same file is in 1 other repository

  • Test engineer

    rafaelghif/antigravity-agents/.agents/skills/test-engineer Skill

    6★ repo

    Enterprise-Grade Guardrails, Zero-Assumption Execution, and Quality Gates for Autonomous AI Coding Agents.

  • Bug investigation

    ldilov/harness-forge/skills/bug-investigation Skill

    6★ repo

    Use for defects, regressions, outages, flaky tests, and unexpected behavior. Guides the agent through triage, containment, reproduction, hypotheses, root-cause evidence, fix verification, and recurrence prevention. Do not use as the primary workflow for new features; use double-diamond-feature instead.

  • Double diamond feature

    ldilov/harness-forge/skills/double-diamond-feature Skill

    6★ repo

    Use for meaningful feature development before coding. Guides the agent through Discover, Define, Develop, and Deliver with evidence, options, validation, and rollback notes. Do not use for bugs, regressions, outages, or flaky tests; use bug-investigation instead.

  • Test strategy and coverage

    ldilov/harness-forge/skills/test-strategy-and-coverage Skill

    6★ repo

    Define right-sized test layers and coverage priorities for a change.

  • Playwright cli

    valkryhx/google_adk_agent/skills/playwright-cli Skill

    no license6★ repo

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

  • Playwright

    valkryhx/google_adk_agent/skills/playwright Skill

    no license6★ repo

    Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

  • Playwright camera mask testing

    simiancraft/simiancraft-skills/skills/playwright-camera-mask-testing Skill

    6★ repo

    Specialization of playwright-harness for CAMERA / segmentation testing in the browser: put a real PERSON in front of getUserMedia so MediaPipe / selfie segmentation produces an actual mask, then verify background-replacement / blur / shader effects by vision. Use when the task is "test the mask on web", "verify segmentation in the browser", "feed the camera a person fixture", "check a camera/background effect in Chrome", or any time a web app must SEE a human through the webcam without physical hardware. Read playwright-harness FIRST for script conventions and execution; this skill only adds the camera-feed pieces. The web analog of android-emulator-mask-testing. Validated on Linux/WSL, headless Chromium, against MediaPipe Selfie Segmentation.

  • Playwright gif capture

    simiancraft/simiancraft-skills/skills/playwright-gif-capture Skill

    6★ repo

    Specialization of playwright-harness for capturing an ANIMATED GIF of web content: drive a page/canvas/WebGL animation, grab a sequence of frames, and encode a looping GIF. Use when the task is "make a gif of this", "grab a gif of the demo/animation/shader", "record the canvas as a gif", or "capture a looping clip for a PR/README/issue"; any time a still screenshot is not enough. Read playwright-harness FIRST for script conventions and execution. For the quality/size dials (preventing deep-fried color, janky frame rate, or oversized files) read references/gif-optimization.md rather than guessing. Validated on Linux/WSL, headless Chromium + ANGLE, against WebGL canvas content.

  • Playwright harness

    simiancraft/simiancraft-skills/skills/playwright-harness Skill

    6★ repo

    Drive a real browser with Playwright on any OS and gate on what you observe: write a script, launch Chromium (headless by default; a shared headed window when a human must watch or drive), drive the page, and assert on screenshots plus collected page errors. The operational trunk for browser work; specializations layer on top. Use for ANY web task: "drive the UI headlessly", "smoke-test a screen", "screenshot a component or canvas", "reproduce a console error", "fill and submit a form", "test a login flow", "check responsive layout", "find broken links", "open a browser I can watch/drive", or "automate a browser flow". Open references/interactions.md and references/flows.md for the element vocabulary and multi-step recipes; switch to playwright-camera-mask-testing for a camera or person feed, or playwright-gif-capture for an animated GIF. Validated on Linux/WSL (headless, ANGLE GPU path for WebGL) and macOS (headless + interactive headed mode).

  • Test github project skills

    yu-iskw/github-project-skills/.cursor/skills/test-github-project-skills Skill

    no license6★ repo

    Comprehensive testing suite for GitHub agent skills and subagents. Executes 17 workflows and generates a detailed report.

  • Ab testing

    sendx/email-skills/skills/ab-testing Skill

    6★ repo

    Run email A/B tests that produce measurable results and guide future campaign decisions.

  • Mobile testing

    northseadl/norix-skills/mobile-testing Skill

    no license6★ repo

    'Android/iOS automated testing: device management, app install, performance profiling,

  • Gh pr review

    Unique-Divine/jiyuu/ai-skills/gh-pr-review Skill

    6★ repo

    Review GitHub pull requests for correctness, design quality, test coverage, security, performance, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".

  • Agent browser

    HK-hub/AgentSkills/agent-browser Skill

    6★ repo

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

  • Python pro

    HK-hub/AgentSkills/python-pro Skill

    6★ repo

    Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

    The same file is in 3 other repositories

  • Webapp testing

    HK-hub/AgentSkills/webapp-testing Skill

    6★ repo

    Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

    The same file is in 45 other repositories

  • Implement approved slice

    Mozurok/fhorja.dev/.claude/skills/implement-approved-slice Skill

    6★ repo

    Implement only the approved slice with minimal, explicit, review-friendly changes, then persist execution evidence in slice notes and TASK_STATE.md. The single official execution path of the workflow. Supports an opt-in test-first (TDD) mode, enabled per slice or via --tdd, that writes the failing test before the code (ADR-0063). Use when the task has a valid IMPLEMENTATION_PLAN.md, the current slice is explicitly defined and approved, correctness-critical ambiguity is already resolved, and the files in scope are known well enough to edit safely. Do not use when the task is still in discovery or contract refinement or planning, when unresolved ambiguity still affects correctness, when the slice boundary is still unclear, when the next step is only to sync task memory or close the slice (use sync-task-state or slice-closure), or when the remaining work is a narrow micro-delta anchored to an already-executed slice with the same intent (use implement-slice-complement).

  • Performance budget

    Mozurok/fhorja.dev/.claude/skills/performance-budget Skill

    6★ repo

    Senior performance-budget auditor that declares the numeric non-functional budgets a change must hold (Core Web Vitals, backend latency percentiles, payload and bundle size, key-operation cost) and the action when a metric regresses. Produces PERFORMANCE_BUDGET.md, a per-metric table of threshold, percentile, measurement source, and regression action. Activates when a task changes a performance-sensitive surface (page, endpoint, list, query, bundle) without a numeric budget, when DECISIONS.md or PROJECT_CHARTER.md names a performance target without per-metric thresholds, or before delivery of a latency- or size-sensitive change. Do not use when the task has no performance surface (docs, internal CRUD with no scale concern), for functional test selection (use test-strategy), or for post-deploy live-signal verification (use post-deploy-verifier). Spec-only; never runs load tests itself. Also covers mobile surfaces: React Native and a Godot 2D-mobile surface (frame budget, draw calls).

  • Test strategy

    Mozurok/fhorja.dev/.claude/skills/test-strategy Skill

    6★ repo

    Define the smallest set of meaningful tests that protects behavior and reduces regression risk for the active task, then persist as TEST_STRATEGY.md plus a TASK_STATE.md update. Avoids forcing a strategy artifact when it adds no material signal. Detects a Godot 2D-mobile target and routes to GUT or gdUnit4 headless, treating the godot-runtime-verify press-play gate as complementary to the headless suite. Use when the task has a valid implementation plan or a clearly understood behavior under change, the change affects important behavior or contracts or data flow or runtime risk or regression risk, or test choices should be decided before or alongside implementation. Use when scope is tagged or reads as auth, biometric, or runtime-risk with no TEST_STRATEGY.md, even if small. Do not use when the task is still too unclear to know what behavior is changing, the current need is broad discovery or contract resolution, or the task is too small to justify a dedicated test strategy artifact.

  • Performance budget

    Mozurok/fhorja.dev/commands/performance-budget Skill

    6★ repo

    Senior performance-budget auditor that declares the numeric non-functional budgets a change must hold (Core Web Vitals, backend latency percentiles, payload and bundle size, key-operation cost) and the action when a metric regresses. Produces PERFORMANCE_BUDGET.md, a per-metric table of threshold, percentile, measurement source, and regression action. Activates when a task changes a performance-sensitive surface (page, endpoint, list, query, bundle) without a numeric budget, when DECISIONS.md or PROJECT_CHARTER.md names a performance target without per-metric thresholds, or before delivery of a latency- or size-sensitive change. Do not use when the task has no performance surface (docs, internal CRUD with no scale concern), for functional test selection (use test-strategy), or for post-deploy live-signal verification (use post-deploy-verifier). Spec-only; never runs load tests itself. Also covers mobile surfaces: React Native and a Godot 2D-mobile surface (frame budget, draw calls).

  • Swift testing

    sarveshsea/design-skills/skills/swift-testing Skill

    6★ repo

    Build an Apple-platform test strategy with Swift Testing for unit and integration coverage, XCTest for UI automation, deterministic fixtures, and concise agent-readable results.

  • Usability testing

    sarveshsea/design-skills/skills/usability-testing Skill

    6★ repo

    Usability testing frameworks — test planning, task scenarios, moderated and unmoderated protocols, analysis frameworks, and insight synthesis for Mémoire research pipeline

  • Moonbit toolchain

    hyfdev/moonbit-agent-skills/skills/moonbit-toolchain Skill

    6★ repo

    Agent Skills for MoonBit. Help coding agents work with MoonBit and write better MoonBit code.

  • Tdd

    chipfighter/coding-discipline/plugins/coding-discipline/skills/tdd Skill

    6★ repo

    Use before implementation when behavior can be verified by automated tests and regression coverage has clear value. For bugs with an unknown root cause, use systematic-debugging first, then return for red-green. Follow red-green-refactor—write a failing test first, add only enough code to pass it, then refactor. Do not trigger for documentation, configuration, copy-only, or styling changes with no testable behavior.

  • Swift testing pro

    laxrajpurohit/swift-skills-pro/swift-testing-pro/skills/swift-testing-pro Skill

    6★ repo

    Use when writing tests with the Swift Testing framework (@Test, #expect, #require, traits, parameterized tests, @Suite) or migrating tests from XCTest.