1. 433Fix TicketEricTechPro/startup-claude-skillsAutomate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.58
  2. 434Playwright QA CLIEricTechPro/startup-claude-skillsAutomated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific fea58
  3. 435Stress Testgbasin/stress-test-skillAdversarially stress-test a technical plan by verifying claims against real docs, running POC code, and updating the plan before you build.45
  4. 436Drupal Testinggrasmash/drupal-claude-skillsTest-driven development for Drupal with PHPUnit and Drupal Test Traits (DTT). Use when writing or fixing tests, deciding what is worth a test, reproducing a bug before fixing it, choosing a bootstrap level (Unit vs Kernel vs ExistingSite/functional), testing permission gates, adding Playwright visual verification, or debugging tests that silently run zero assertions. Covers the bug-fix RED-first discipline, the worth-a-test rubric, bootstrap cost tradeoffs, negative tests, the anonymous-403 permission trap, DTT gotchas, and the PHPUnit-version pin that makes Drupal tests pass vacuously.84
  5. 437Test AuditPyModel/jev-judge-mcpInvoke whenever writing, changing, reviewing, or sweeping tests in jev-judge-mcp. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only production seams they demand, under this repo's rule that a test is never deleted or weakened to make a failing build pass.49
  6. 438Olore Bunit Latestolorehq/oloreLocal bunit documentation reference (latest). bUnit Blazor testing documentation. Use for Blazor component testing, rendering, event handling, JSInterop mocking, and test assertions in .NET.119
  7. 439Olore Playwright 1.60.0olorehq/oloreLocal Playwright documentation reference (1.60.0). Playwright documentation. Use for end-to-end testing, browser automation, cross-browser testing, selectors, assertions, and test fixtures.119
  8. 440Olore Playwright 1.65.0olorehq/oloreLocal Playwright documentation reference (1.65.0). Playwright documentation. Use for end-to-end testing, browser automation, cross-browser testing, selectors, assertions, and test fixtures.119
  9. 441Olore Playwright Latestolorehq/oloreLocal playwright documentation reference (latest). Playwright documentation. Use for end-to-end testing, browser automation, cross-browser testing, selectors, assertions, and test fixtures.119
  10. 442Regex Testerolorehq/oloreValidate, test, and debug regular expressions by executing them against sample inputs. Use when asked to build, verify, or explain a regex pattern.119
  11. 443Alterlab AdaptyvAlterLab-IEU/AlterLab-Academic-SkillsPrepares and validates Adaptyv Bio Foundry protein-testing submissions with no account — optimizes and pre-screens sequences locally (NetSolP/SoluProt heuristics, SolubleMPNN, ESM), assembles the experiment payload, and validates it offline against the Foundry's own type/method/sequence rules so it is ready and correct before it costs anything. Submitting to the Foundry, browsing the target catalog, tracking status and retrieving results run through the Foundry API with the user's own ADAPTYV_API_KEY (experiments cost money and take weeks). Use when designing proteins for wet-lab validation (b87
  12. 444Alterlab Figure QAAlterLab-IEU/AlterLab-Academic-SkillsVerify publication figures with a render-then-check QA pass — data-fidelity against every underlying row, axis/label floor-and-ceiling legibility, bounding-box collision detection for overlapping text/markers, and 300-dpi print-readiness. Use when proofing or auditing a finished figure for correctness and print quality, catching mislabeled or overlapping elements, or confirming a plot faithfully represents its data before submission. For CREATING the plot prefer alterlab-matplotlib (or alterlab-seaborn / alterlab-plotly); for multi-panel publication layout prefer alterlab-scientific-viz; for s87
  13. 445Alterlab Harness CanaryAlterLab-IEU/AlterLab-Academic-SkillsTEST-ONLY canary for the behavioral eval harness (scripts/run_evals.py --behavioral --skill-dir benchmarks/harness-canary). Not a user-facing skill and not part of the catalog. Part of the AlterLab Academic Skills suite.87
  14. 446Alterlab Preregistration DisciplineAlterLab-IEU/AlterLab-Academic-SkillsEnforces pre-registration discipline with the Iron Law NO DATA ANALYSIS WITHOUT A PRE-REGISTERED ANALYSIS PLAN FIRST, a spirit-vs-letter line, an Excuse-vs-Reality rationalization table, and a Red-Flags-STOP list (HARKing, optional stopping, post-hoc covariates, outlier-dropping, test-shopping). Runs a PLAN/COLLECT/CONFIRM/EXPLORE workflow that freezes hypotheses, tests, exclusions, and stopping rules before data, then forces unplanned findings to be labeled exploratory (their p-values lose confirmatory status, per COS confirmatory/exploratory model). Orchestrates, not replaces, alterlab-open-87
  15. 447Alterlab Test Selection GuardAlterLab-IEU/AlterLab-Academic-SkillsEnforces statistical-test selection as a discipline, holding the Iron Law NO TEST CHOSEN AFTER SEEING THE P-VALUE: routes the choice through a fixed decision tree (outcome type -> groups -> paired? -> normality) terminating in named tests (t-test, Mann-Whitney U, ANOVA, Kruskal-Wallis, Wilcoxon, Friedman, chi-square, Pearson/Spearman, regression), gates interpretation behind a mandatory Shapiro-Wilk/Levene/linearity assumption check, blocks test-shopping with an Excuse-vs-Reality table and Red-Flags-STOP list, and applies a 3+-tests escalation gate forcing Bonferroni/FDR correction or an explo87
  16. 448Test Crewai ProjectcrewAIInc/skillsDeterministic, offline testing of CrewAI crews and flows with pytest: a stub BaseLLM (shipped in references/stub_llm.py) that drives text, structured output and tool calls with no API key, asserting on the prompts crewai built, testing guardrails and flow routing, what `crewai test` really does, event listeners for debugging, and the exact tracing/telemetry env var values. Use when writing tests for a crewai project, mocking or stubbing the LLM, writing a custom BaseLLM, seeing `TypeError: ... call() got an unexpected keyword argument 'from_task'`, `ValueError: OPENAI_API_KEY is required` in C49
  17. 449A B TestingLeadMagic/gtm-skillsDesign statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.79
  18. 450Lead EnrichmentLeadMagic/gtm-skillsEnrich prospect and account lists with company, contact, role, technographic, intent, funding, hiring, and confidence fields. Produces enrichment schema, waterfall order, QA thresholds, dedupe rules, and CRM-ready output. Use when turning raw lists into usable GTM data or improving data quality.79
  19. 451Lead FindingLeadMagic/gtm-skillsFind qualified prospects and decision-makers from ICP criteria using public research, company signals, role mapping, and source confidence. Produces a prospect list spec, search strategy, qualification rubric, source log, and QA checklist. Use when building target lists or finding buyers at named accounts.79
  20. 452Sequencing ToolkitLeadMagic/gtm-skillsComplete outreach sequencing toolkit — Smartlead, Instantly, Salesloft, Outreach, Lemlist setup and optimization. Covers mailbox rotation, warmup, A/B testing, deliverability monitoring, and multi-channel orchestration across all major sequencing platforms. Use when setting up or optimizing an outreach sequencing platform. Triggers on: "sequencing toolkit", "Smartlead setup", "Instantly optimization", "outreach platform comparison".79
  21. 453Test Case Xmindxiaoce-xiaoce/testing-skills-xiaoce根据产品需求文档、前端技术文档、后端技术文档、交互稿、接口说明、截图和相关项目资料生成结构化软件测试用例;校验用例格式;按“用例标题/前置条件/步骤/预期结果”模板导出 .xmind 脑图文件。适用于生成 QA 测试用例、验收用例、功能用例、回归用例、边界用例,或根据一个或多个输入文档生成 XMind 测试用例脑图。43
  22. 454Ansible Pytest Migrateleogallego/ai-skills-ansibleMigrate off, remove, deprecate, or audit the pytest-ansible plugin in an Ansible collection repository. Identifies real plugin use before editing dependencies or test commands, so ordinary Ansible variables and module mocks are never mistaken for plugin use. Use when user says "remove pytest-ansible", "migrate off pytest-ansible", "drop the pytest-ansible plugin", or "audit pytest-ansible usage". Plain pytest and ansible-test are retained; only the pytest-ansible plugin is removed. Do NOT use for general Ansible migrations such as FQCN conversion or inventory restructuring, and do NOT use for 49
  23. 455Bestow CurseHmbown/Wizards-of-the-GhostsBestow Curse saddles a target with a lasting disadvantage. The real-world version is constraint injection: deliberately adding friction, limitations, or handicaps to see how a system, process, or team adapts. This is the skill of resilience testing through artificial adversity — bandwidth throttling, feature removal, resource reduction.113
  24. 456DeceptionHmbown/Wizards-of-the-GhostsUse this skill to generate believable synthetic artifacts for testing, demos, adversarial exercises, or rehearsal environments. The goal is plausibility under inspection by software and operators, not manipulation of real users or fabrication of evidence.113
  25. 457Design DistillerYrzhe/claude-skillsScrape any website's design system into a structured Design MD + decomposed design tokens. Supports Browser Use Cloud, Playwright, Chrome headless, source code analysis. Maintains a Reference Pool of full Design MDs and a Digest Pool of cross-site design tokens for mix-and-match composition.65
  26. 458Fix Issuelllyys/vreaderEnd-to-end GitHub issue resolver — fetch, classify, branch, fix with TDD, Codex audit loop, test gate, docs-sync, version bump, PR, and post-merge close-gate finalizer. Use this skill whenever the user wants to fix a bug from a GH issue, asks 'fix issue #N', 'fix bug 115', 'work on issues #123 #456 #789', 'resolve this GH bug', or pastes a GH issue URL/number for resolution. Also handles `question`-labeled issues (inline answer + comment, no branch). REDIRECTS feature/enhancement issues to feature-workflow per rule 47. Supports both single-issue and multi-issue (worktree) pipelines.49
  27. 459Hallucinatory TerrainHmbown/Wizards-of-the-GhostsIn D&D, Hallucinatory Terrain makes natural terrain look like a different kind of terrain — a field appears as a forest, a hill appears as a valley. The underlying terrain is unchanged; only the perception shifts. The real-world version is environment staging: test environments styled to look like production, sandbox databases seeded with realistic data, training simulations that overlay a learning scenario onto real infrastructure. Hallucinatory Terrain does not change the real system. It changes how the system appears so you can test, train, or demo safely.113
  28. 460Mirage ArcaneHmbown/Wizards-of-the-GhostsIn D&D, Mirage Arcane goes beyond Hallucinatory Terrain — the illusory terrain actually has substance. You can walk on illusory bridges, feel illusory walls. The real-world version is the deep simulation: digital twins, high-fidelity synthetic environments, test harnesses so realistic that systems under test cannot distinguish them from production. Mirage Arcane is the most dangerous illusion because its power is in being indistinguishable from reality. That same power makes it the most useful for stress testing, training, and scenario planning — but it requires the strongest labeling discipli113
  29. 461Offer CardLiamrjohnston/offer-master-skillFormats a finished offer as a short paste-ready card and page section. Every number labelled (yours) or (estimate), plus a Check these list and one test to run this month.49
  30. 462Onboard Arch Precheckhw-native-sys/simplerDetect the host's actual Ascend silicon and refuse mismatched onboard hardware tests. On shared hosts, acquire a task-submit device allocation first and run the precheck and hardware test in that same job. Skip for a2a3sim and a5sim.49
  31. 463Perf Runtime Devicehw-native-sys/simplerBenchmark the hardware performance of all scene tests under a runtime (tests/st/<arch>/<runtime>/, $ARGUMENTS). Use when the user asks to benchmark all examples of a runtime on hardware.49
  32. 464Plan Auditlllyys/vreaderAudit an implementation against a plan (dev-docs/plans/*). Use when a user asks to check for gaps, logic errors, or missing tests relative to a plan or Work Items.49
  33. 465Test All Devicehw-native-sys/simplerRun the full hardware (onboard) CI pipeline (examples + tests/st) with automatic platform and device detection. Use when the user asks to run all device/hardware tests or the full onboard CI locally.49
  34. 466Test All Simhw-native-sys/simplerRun the full simulation CI pipeline (examples + tests/st) on a2a3sim/a5sim. Use when the user asks to run all sim tests or the full simulation CI locally.49
  35. 467Test Example Devicehw-native-sys/simplerRun the hardware (onboard) device test for a single example/scene-test directory ($ARGUMENTS). Use when the user asks to run or onboard one example on real hardware.49
  36. 468Test Example Simhw-native-sys/simplerRun the simulation test for a single example/scene-test directory ($ARGUMENTS). Use when the user asks to run one example in simulation.49
  37. 469Test Runtime Devicehw-native-sys/simplerRun hardware (onboard) device tests for one runtime ($ARGUMENTS — host_build_graph or tensormap_and_ringbuffer). Use when the user asks to onboard or test a single runtime on real hardware.49
  38. 470Test Runtime Simhw-native-sys/simplerRun simulation tests for one runtime ($ARGUMENTS — host_build_graph or tensormap_and_ringbuffer). Use when the user asks to test a single runtime in simulation.49
  39. 471Testinghw-native-sys/simplerTesting guide and pre-commit testing strategy for simpler. Use when running tests, adding tests, or deciding what to test before committing.49
  40. 472Game QA LeadAlterLab-IEU/AlterLab_GameForgeQA Lead (Rook Callahan). Writes risk-based test plans, triages bugs, builds regression suites and release gates, and sets up automated tests for Godot (GUT, gdUnit4), Unity, Unreal and web (Vitest, Playwright), including smoke checks for AI-built games. Use for "test plan", "bug triage", "regression", "release gate", "flaky tests". Not for player playtests (use game-playtest).57
  41. 473Game Web2d SpecialistAlterLab-IEU/AlterLab_GameForgeBuilds 2D browser games with Phaser 4 (primary), PixiJS 8, Kaplay, Excalibur or LittleJS: framework choice, Phaser scenes, Arcade or Matter physics, Tiled/LDtk tilemaps, atlases, pixel-art scaling, Phaser 3 to 4 migration and Playwright checks. Use for "Phaser", "PixiJS", "Kaplay", "2D web game", "tilemap". Not for 3D browser games (use game-threejs-specialist).57
  42. 474Bdd Orchestratormeirm/reverse-engineering-skillOrchestrates the full BDD workflow from code to trustworthy business logic — extraction, validation, gap analysis, refinement, acceptance criteria, and test generation. Use when the user requests comprehensive analysis like "understand [feature] from code", "analyze [domain] end-to-end", or "prepare [feature] for implementation or sprint planning", coordinating the other BDD skills step by step.47
  43. 475Generate Tests From Business Logicmeirm/reverse-engineering-skillGenerates scenario tests, rule tests, edge case tests, state transition tests, and billing tests from trusted business logic. Use when creating test suites from BL, ensuring BL coverage, or turning requirements into verifiable tests.47
  44. 476Vibe Testingknot0-com/vibe-testingThis skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.24
  45. 477Timovi QA Engineertheminimalcreator/timoviQA Engineer for the Timovi project. Validates framework completeness and testability with Given/When/Then criteria, edge cases, and quality risks. Use when planning tests for the framework, defining acceptance criteria for pipeline phases, analyzing edge cases in state transitions, or reviewing framework quality.49
  46. 478TDD Workflowjoneqian/claude-skills-suiteUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.32
  47. 479Access Control Testingmn-youssef/security-skillsUse when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.49
  48. 480Authentication Testingmn-youssef/security-skillsUse when testing login, sessions, password reset, OAuth/OIDC/SAML/SSO, MFA, and JWTs for weaknesses that lead to account takeover — credential attacks, session fixation, reset-token poisoning, MFA bypass, and token forgery. On apps you own or are authorized to test.49