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
SkillMedev/skills/skills/e2e-scenario-author Skill
5★ repoConverts an acceptance criterion or user story into one maintainable Playwright or Cypress end-to-end test that reads like the journey it covers. Use when turning a Given/When/Then acceptance criterion or user story into a browser test, when asked to "write an E2E test for this AC", or when a feature's critical journey (login, checkout, signup) needs a single automated scenario. Do NOT use when writing general Playwright tests, configuring the runner, or fixing existing test flakiness - use playwright-testing or flaky-test-detangler instead.
The same file is in 1 other repository
SkillMedev/skills/skills/experiment-tracking Skill
5★ repoSets up disciplined ML experiment tracking - run logging schemas, artifact versioning, naming conventions, and reproducibility standards - and produces the run-record template a team actually follows. Use when someone asks "how should we track our ML experiments", "why can't we reproduce this result", "how do I set up MLflow or W&B for the team", or is bootstrapping a new ML project. Do NOT use for analyzing product A/B tests - use ab-test-analyzer instead; for monitoring deployed models use data-drift-monitor; for judging whether a trained model is good enough to ship use model-evaluation-report.
The same file is in 1 other repository
SkillMedev/skills/skills/flaky-test-detangler Skill
5★ repoRoot-causes intermittently failing tests and eliminates the hidden dependency at its source instead of retrying around it. Use when a test passes locally but fails in CI, goes green on a CI re-run, fails roughly one run in ten, or is already tagged "flaky." Do NOT use when the task is to design the fake or stub that replaces a real dependency - use mock-stub-designer instead.
The same file is in 1 other repository
SkillMedev/skills/skills/funnel-analysis Skill
5★ repoBuilds conversion funnels from raw event data with drop-off attribution, segment comparison, and significance testing, and delivers a filled funnel table with a diagnosed bottleneck and next action. Use when someone asks "where are users dropping off", "why did checkout conversion fall this week", "build a signup-to-activation funnel", or "is mobile converting worse than desktop". Do NOT use for rewriting page copy or layout to lift a known weak step - use landing-page-cro instead; for decomposing active-user growth into new, retained, resurrected, and churned - use growth-accounting instead; for choosing which events to instrument and which product metrics to track - use product-analytics instead; for designing and reading a controlled experiment - use ab-test-analyzer instead.
The same file is in 1 other repository
SkillMedev/skills/skills/landing-page-cro Skill
5★ repoImproves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.
The same file is in 2 other repositories
SkillMedev/skills/skills/load-testing Skill
5★ repoDesigns and interprets load tests - smoke, load, stress, soak, and spike - with realistic ramp profiles, percentile-based pass/fail thresholds, and a bottleneck-reading procedure, producing a runnable test plan. Use when someone asks "how many users can we handle", "how do I write a k6 or Gatling test", "will this survive the launch", "why did the site die at 500 users", or is preparing for a traffic event. Do NOT use for diagnosing frontend page-speed or Core Web Vitals - use web-performance instead - and do NOT use for tuning database connection pools found as the bottleneck - use connection-pool-tuner instead.
SkillMedev/skills/skills/mock-stub-designer Skill
5★ repoDesigns the minimal set of test doubles for a unit or integration test and decides, per dependency, whether to stub, fake, spy, mock, or exercise the real thing. Use when someone asks "should I mock this", "how do I test code that calls Stripe or S3 or the clock", "why do our tests pass while production is broken", or when a test touches an HTTP API, payment or email/SMS SDK, database, filesystem, system clock, or randomness. Do NOT use for fabricating valid domain fixture data (a User with defaults, an Order with line items) - use test-data-builder instead; for driving a red-green implementation loop, use tdd-expert.
The same file is in 1 other repository
SkillMedev/skills/skills/mutation-test-runner Skill
5★ repoRuns mutation testing on already-covered code and turns each surviving mutant into a specific missing assertion, exposing tests that execute code but verify nothing. Use when line coverage is high yet a bug slipped through, when reviewing a critical module (pricing, permissions, auth, state machines) before release, or when you are asked to run Stryker, PIT, mutmut, or cosmic-ray. Do NOT use when the goal is to find which code paths are untested at all - use coverage-gap-finder instead.
The same file is in 1 other repository
SkillMedev/skills/skills/playwright-testing Skill
5★ repoWrites and reviews end-to-end Playwright tests that survive UI refactors and never fail on timing - resilient locators, web-first assertions, isolated state, and a flake policy with quarantine rules. Use when someone asks "write a Playwright test for this flow", "why is this e2e test flaky", "how do I wait for this element", "what selector should I use", or is setting up a Playwright suite and CI config. Do NOT use for consumer/provider contract tests of API boundaries - use contract-test-writer instead; for turning product requirements into an e2e scenario inventory before any code - use e2e-scenario-author instead; for systematically diagnosing an already-flaky suite - use flaky-test-detangler instead; for designing reusable test fixtures and factories - use test-data-builder instead.
The same file is in 1 other repository
SkillMedev/skills/skills/prospecting-metrics Skill
5★ repoUse when you need to turn outbound prospecting into a measurable, backsolvable funnel instead of guesswork - for quota planning, activity targets, funnel diagnosis, and A/B test sizing. Triggers include "how many emails do I need to send", "backsolve my quota", "what's a good reply rate", "how many meetings per 100 contacts", "my outbound isn't converting", "where is my funnel breaking", "is this A/B test significant", "how many contacts to hit pipeline target", "what activity do I need this week", and "what conversion rates should I expect for cold outbound". Workflow: define the canonical funnel, plug in your real (or benchmark) conversion rates, backsolve required weekly activity from a quota, diagnose which stage is broken, and size tests honestly. Do NOT use for writing the actual messages - use [[cold-email-craft]]; Do NOT use for designing the multi-step cadence itself - use [[outreach-sequence-designer]]; Do NOT use for fixing inbox placement - use [[cold-email-deliverability]].
The same file is in 1 other repository
SkillMedev/skills/skills/skill-tester Skill
5★ repoEmpirically tests a skill with subagent scenarios to verify it fires on the right prompts, stays silent on the wrong ones, and performs its job when loaded. Use when validating a new or modified SKILL.md before publishing - "test this skill", "does this trigger correctly", "verify the skill works". Do NOT use to statically grade or rewrite skill quality (use skill-auditor) - this runs live behavioral tests.
The same file is in 1 other repository
SkillMedev/skills/skills/tdd-expert Skill
5★ repoDrive development with strict Red-Green-Refactor discipline - write one failing test, write the minimum code to pass it, refactor on green - including test-list planning and a worked kata cycle. Use when someone asks "write this test-first", "do TDD on this feature", "help me practice red-green-refactor", "write a failing test for this bug", or wants tests to drive a new module's design. Do NOT use for adding tests to existing untested legacy code before a refactor - use characterization-test-writer instead - or for designing shared fixtures and factories - use test-data-builder instead.
The same file is in 3 other repositories
SkillMedev/skills/skills/test-data-builder Skill
5★ repoBuilds realistic domain fixtures, factories, and edge-case datasets with the builder pattern and valid defaults, so each test owns exactly the data it asserts on. Use when someone asks "how should I set up test data", "my fixtures broke half the suite", "make a factory for this model", "why is this test flaky only in CI", or a test needs domain objects, seed data, or boundary inputs. Do NOT use when a test needs to fake a network call, database client, clock, or third-party SDK - use mock-stub-designer instead; do NOT use for designing the assertions or test cases themselves - use tdd-expert instead.
The same file is in 1 other repository
SkillMedev/skills/skills/test-placeholder-data Skill
5★ repoUse when building a demo, prototype, or tutorial that needs realistic remote data - "fake products/users/todos for this app", "an API I can hit while wiring up fetch", "placeholder images", "seed this UI with something that looks real", or teaching HTTP/CRUD against a live endpoint. DummyJSON is the default (rich e-commerce-shaped data, full fake CRUD, no key); JSONPlaceholder, RandomUser, and Lorem Picsum cover the rest. Do NOT use for generating local test fixtures or factories inside a test suite - use test-data-builder instead; do NOT use when the task needs real-world data (weather, prices, countries) - route through public-data-api-picker.
The same file is in 1 other repository
SkillMedev/skills/skills/usability-test-plan Skill
5★ repoPlans a usability study - research questions, realistic task scenarios with success criteria, metrics (completion rate, time on task, SEQ, SUS), a recruiting screener, and moderated vs. unmoderated guidance. Use when someone says "plan a usability test", "write task scenarios for our prototype", "how many participants do we need", or is about to put an interface or prototype in front of users. Do NOT use for open-ended discovery interview guides - use interview-guide-builder instead; for analyzing quantitative A/B experiments, use ab-test-analyzer.
The same file is in 1 other repository
zapgun-ai/clawback/.skills/report_smoke Skill
no license5★ repoEnd-to-end smoke test for the /<admin-path>/report saved-run viewer. Boots the real clawback binary against the repo's runs/ dir and curls every report route, asserting status + content, prefix mutability, public-read exemption, and that sensitive run-dir siblings stay unreachable. Use after touching src/report.js, src/report_ui/*, or the admin/report wiring.
zapgun-ai/clawback/.skills/smoke Skill
no license5★ repoRun the clawback end-to-end smoke test. Starts a mock upstream, spawns the proxy against it, exercises path-mode and hash-mode requests, walks the admin API, and prints the persisted state. Use when verifying the proxy still works after changes.
HsuanYuLee/polaris/.claude/skills/unit-test Skill
5★ repoProject-aware unit testing guide with mock patterns, TDD discipline, and best practices. Auto-detects test framework (Jest/Vitest) and provides appropriate examples. Use when: (1) writing or fixing unit tests, (2) user says "寫測試", "write test", "補測試", "add test", (3) user encounters mock patterns or test failures, (4) user asks how to test a composable, component, or store, (5) user says "mock imports", "test store", "怎麼測", "測試怎麼寫", (6) reviewing test quality: "unit test review", "review tests", "check test quality", "測試審查", "review 測試", "測試品質", "檢查測試品質", (7) TDD workflow: "TDD", "test driven", "紅綠燈", "先寫測試", "test first", "red green refactor".
HsuanYuLee/polaris/.claude/skills/visual-regression Skill
5★ repoTransitional standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use when: "跑 visual regression", "檢查畫面", "頁面有沒有壞", "visual test", "screenshot test", "畫面測試", "截圖比對", "有沒有跑版", "畫面壞了嗎", "UI 有沒有問題", "check if pages look right", for standalone manual investigation. Engineering / verify-AC Layer C uses scripts/run-visual-snapshot.sh instead.
ramboz/jig/hosts/claude/skills/tdd-loop Skill
5★ repoDrive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.
ramboz/jig/hosts/codex/plugins/jig/skills/tdd-loop Skill
5★ repoDrive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.
ramboz/jig/skills/tdd-loop Skill
5★ repoDrive the red-green-refactor loop for any non-trivial code change. Auto-detect the project's test runner (pytest / vitest / jest / node --test), invoke it via the `tdd.py` helper, and act on the normalized exit code. Use when you write a test, TDD this feature, let me test-drive a behaviour, are about to implement [feature], want to run my tests, ask is my coverage complete, or ask are tests green. Do not use for one-off exploratory scripts, throwaway spikes, or pure-documentation edits that touch no executable code.
zeikar/hyperclaude/skills/hyper-tdd Skill
5★ repoUse when about to write or modify behavior-bearing code — functions, business logic, bug fixes — before writing any production code. Also when the user invokes /hyperclaude:hyper-tdd. Forces a failing test first so you watch it fail for the right reason.
air-gapped/skills/.claude/skills/baml-expert Skill
5★ repoBAML (Boundary ML) expert for projects defining LLM calls as typed functions in .baml files with a generated Python client. Use whenever the repo contains baml_src/, baml_client/, baml-cli commands, or imports from baml_py / baml_client. Covers .baml syntax (function, class, enum, client, test, retry_policy, attributes), Python integration (baml_client sync/async, streaming, ClientRegistry, Collector, TypeBuilder), Schema-Aligned Parsing, ctx.output_format, @@assert / @@check tests, @stream.done / @stream.not_null / @stream.with_state streaming, multimodal (image/audio/pdf), and debugging via BAML_LOG plus Boundary Studio. Triggers even unnamed — "add an LLM function", "fix a failing parse", "add a test for the prompt", "stream the response" in a project with baml_src/. Prefer over raw LLM-SDK guidance here; defer to jinja-expert for standalone chat-template / .j2 work.
fabioc-aloha/Alex_Skill_Mall/plugins/code-quality/falsifiability-test-pattern Skill
5★ repoPlans without measurable success criteria drift into wishful thinking:
fabioc-aloha/Alex_Skill_Mall/plugins/code-quality/parity-guard-test-pattern Skill
5★ repoWhen checking that all callers of a contract implement it correctly, you get false positives from wrapper delegators:
fabioc-aloha/Alex_Skill_Mall/plugins/code-quality/test-quality-analysis Skill
5★ repoAnalyze test code quality to detect coverage-only tests, test smells, and low-value assertions. Use when asked to "analyze test quality", "find coverage-only tests", "audit our tests", "are these tests valuable", "find test smells", or "which tests should we delete". Scores tests 1-5 on real value and produces prioritized improvement reports.
fabioc-aloha/Alex_Skill_Mall/plugins/code-quality/test-rename-drift Skill
5★ repo284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.
fabioc-aloha/Alex_Skill_Mall/plugins/code-quality/testing-strategies Skill
5★ repo284 curated plugins for AI assistants across 16 categories: security, Azure, documentation, code quality, cloud infrastructure, and more. Works with GitHub Copilot. Drop into .github/skills/local/ and go.
fabioc-aloha/Alex_Skill_Mall/plugins/domain-expertise/marketing-skill Skill
5★ repoWhen the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariat...
fabioc-aloha/Alex_Skill_Mall/plugins/reasoning-metacognition/hypothesis-driven-debugging Skill
5★ repoInvestigate build failures, test errors, runtime crashes, or unexpected behavior through systematic minimal reproduction, multi-hypothesis testing, and evidence-based verification. Use when asked to "debug", "investigate a failure", "find root cause", "troubleshoot", "fix a failing test", or "diagnose an issue". Always re-run builds and tests after changes.
tea-x-random/unity-game-skills/skills/unity-qa-release Skill
5★ repoVerify and release casual iOS games built in Unity. Use for playtest QA, Play Mode tests, EditMode tests, Unity Test Framework, device resolution checks, safe-area UI checks, iOS build, Xcode project generation, IL2CPP, ASTC texture compression, App Store, TestFlight (TestFlight upload), privacy manifest (PrivacyInfo.xcprivacy), ATT prompt, app icon, launch screen, orientation lock, deployment target, managed stripping / link.xml, release readiness, ship it, and release risk reports. Also covers automating the manual macOS step with fastlane: App Store Connect API key auth, code signing, sigh, provisioning profiles, build number, CocoaPods, pod install, xcworkspace, EDM4U. Drives the Editor through unity-mcp-bridge (manage_build, run_tests, get_test_job).
x3fleetsafety/skills/skills/da-follow-up-testing-schedule Skill
5★ repoUse this skill when managing post-SAP follow-up testing for a driver. Covers the testing cadence, recordkeeping, what happens if a test is missed, and how to transition the schedule to a new employer.
Da pre employment prior test exception
x3fleetsafety/skills/skills/da-pre-employment-prior-test-exception Skill
5★ repoUse this skill when hiring a driver who has a recent valid pre-employment test from a prior employer. Covers the conditions under § 382.301(c) that allow accepting it instead of testing again.
x3fleetsafety/skills/skills/da-sap-program-implementation Skill
5★ repoUse this skill when referring a driver to SAP after a positive test or refusal. Covers SAP selection, the evaluation/treatment cycle, return-to-duty test, and follow-up testing schedule.
x3fleetsafety/skills/skills/driver-onboarding-process Skill
5★ repoUse this skill when the user asks about onboarding a new CDL driver — pre-hire process, day-zero requirements, application + DQF setup, road test, drug & alcohol pre-employment, Clearinghouse Full query, MVR initial pull, PSP report, ELDT verification, sequence of activities + timing, and what NOT to do (handing keys before testing complete). Cite 49 CFR 391, 382.
x3fleetsafety/skills/skills/drug-and-alcohol-testing Skill
5★ repoUse this skill when the user asks about commercial driver drug & alcohol testing under 49 CFR 382 + 40 — the six testing reasons (pre-employment, random, post-accident, reasonable suspicion, return-to-duty, follow-up), MRO process, SAP/return-to-duty process, post-accident triggers, random selection rates, what panels are tested, refusal definitions, or testing programs and consortiums. Cite specific 49 CFR 382 or 40 subsection.
rikitrader/glaw/insurance-coverage Skill
no license5★ repoGLAW Insurance Coverage & Bad-Faith seat — first-party policyholder coverage disputes (property/CGL/auto/D&O), the claim → proof-of-loss → appraisal → litigation path, duty-to-defend vs. duty-to-indemnify analysis, exclusion/condition parsing, and first- & third-party bad-faith (Florida § 624.155 Civil Remedy Notice + the §§ 626.9541 unfair-claims framework). Built for the policyholder/insured (not the carrier); pairs with /glaw-roofer-accounting for insurance-restoration / Xactimate claims. Every position record-tied, run past an adversarial pass, for a licensed attorney to sign. Use for: 'insurance claim denial', 'coverage dispute', 'duty to defend', 'bad faith', 'civil remedy notice', 'CRN', 'proof of loss', 'appraisal clause', 'property claim', 'supplement denied', 'underpaid claim', 'policy exclusion', 'first-party bad faith', 'hurricane/storm claim', 'reservation of rights'.
build-with-dhiraj/ai-workflow-framework-portability-kit/Plugins/vercel-marketplace-source/.claude/skills/benchmark-testing Skill
5★ repoCreate and launch benchmark test projects to exercise vercel-plugin skill injection across realistic scenarios. Sets up isolated directories, installs the plugin, and spawns WezTerm panes running Claude Code with crafted prompts.
build-with-dhiraj/ai-workflow-framework-portability-kit/Plugins/vercel-marketplace-source/.claude/skills/plugin-audit Skill
5★ repoAudit vercel-plugin performance on real-world projects. Extracts tool calls from Claude Code conversation logs, tests hook matching against actual inputs, identifies pattern coverage gaps, and checks plugin cache staleness. Use when asked to audit, test, or investigate plugin skill injection on a real project.
build-with-dhiraj/ai-workflow-framework-portability-kit/Plugins/vercel-marketplace-source/skills/agent-browser/upstream Skill
5★ repoBrowser 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.
build-with-dhiraj/ai-workflow-framework-portability-kit/Skills/flutter-testing-apps Skill
5★ repoImplement unit, widget, and integration tests for a Flutter app. Use for code quality and regression prevention.
build-with-dhiraj/ai-workflow-framework-portability-kit/Skills/generate-synthetic-data Skill
5★ repoCreate diverse synthetic test inputs for LLM pipeline evaluation using dimension-based tuple generation. Use when bootstrapping an eval dataset, when real user data is sparse, or when stress-testing specific failure hypotheses. Do NOT use when you already have 100+ representative real traces (use stratified sampling instead), or when the task is collecting production logs.
build-with-dhiraj/ai-workflow-framework-portability-kit/Skills/migrate-to-shoehorn Skill
5★ repoMigrate test files from `as` type assertions to @total-typescript/shoehorn. Triggers on "shoehorn", "replace `as` in tests", or partial test data needs.
build-with-dhiraj/ai-workflow-framework-portability-kit/Skills/tdd Skill
5★ repoTest-driven development with red-green-refactor loop. Triggers on "TDD", "red-green-refactor", "test-first".
build-with-dhiraj/ai-workflow-framework-portability-kit/Skills/validate-evaluator Skill
5★ repoCalibrate an LLM judge against human labels using data splits, TPR/TNR, and bias correction. Use after writing a judge prompt (write-judge-prompt) when you need to verify alignment before trusting its outputs. Do NOT use for code-based evaluators (those are deterministic; test with standard unit tests).
lucasheriques/shipmate/skills/mom-test Skill
5★ repoPlan, conduct, and review customer discovery conversations using The Mom Test (Rob Fitzpatrick). Use when preparing user or customer interviews, validating a product/feature/business idea through conversations, writing interview questions, judging whether feedback is real signal or bad data (compliments, fluff, ideas), or deciding whether a meeting produced real commitment vs polite rejection.
lucasheriques/shipmate/skills/product-bets Skill
5★ repoChoose, construct, test, and operate product bets using Life at the Speed of Play (Mark Pincus) - instinct vs idea, Proven-Better-New, Minimum Idea State, the weekly roadmap OS. Use when deciding whether to build a product or feature, testing an idea before writing code, choosing a market or what to copy vs innovate, setting up a weekly product cadence or OKRs, picking a North-Star or leading metric, or when a team ships features that don't move any metric.
BANANASJIM/openplan-skill/skills/openplan-test Skill
5★ repoDesign, run, and report a proportional OpenPlan-style test evidence framework. Use when Codex, Claude Code, or another agent must choose test layers, prove regression tests are meaningful, separate fast checks from privileged or expensive checks, compare implementation behavior with fixtures/oracles/properties, or report tests run/skipped without treating passing tests as approval.
8Dionysus/aoa-skills/skills/core/engineering/aoa-verification Skill
5★ repoTurn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.
Far-200/think-before-code/skills/specification-coach Skill
5★ repoSocratic Agent Skills for learning problem-solving and software-engineering judgment — one question at a time.
Far-200/think-before-code/skills/test-case-coach Skill
5★ repoSocratic Agent Skills for learning problem-solving and software-engineering judgment — one question at a time.
rshade/finfocus/agent-skills/finfocus-routing Skill
5★ repoConfigure and debug FinFocus intelligent plugin routing. Use when setting up multi-plugin routing, configuring priority and fallback rules, writing pattern matching for resource types, testing route selection, or debugging why a plugin isn't receiving cost queries. Triggers on: "configure routing", "plugin priority", "fallback chain", "route test", "multi-region routing", "pattern matching", "config routes", "plugin selection", "routing config", or any task involving finfocus plugin routing configuration and debugging.
stefanoskarakasis/Product-Marketing-Skills/pmm-execution/skills/pmm-okrs Skill
5★ repoGuides Product Marketing leaders and individual PMMs through building a complete, export-ready OKR set for their quarter — including Objective, Key Results, Projects, Scorecard metrics, and Exec Summary language. Includes post-session logging for meta-synthesis pattern detection and pre-flight guardrails from prior quarters. Use when setting quarterly OKRs, reviewing existing OKRs, stress-testing KR quality, or building a measurement plan. Trigger on: "help me set our OKRs", "are my KRs measurable", "build a scorecard", "stress-test this KR", "write OKRs for my team", "present goals to exec team". Produces output paste-ready for the PMM OKR Builder spreadsheet or leadership sharing.
ondrej-merkun/skill-audit/test/fixtures/benign/test-runner Skill
no license5★ repoScan every AI agent skill on your machine for prompt injection and malicious code. Fast local rules by default, with optional local LLM review for deeper context.
BjornMelin/dev-skills/skills/pytest-dev Skill
no license5★ repoWorld-class pytest engineer for Python: write/refactor tests, fix flakiness, design fixtures/markers, add coverage, speed up suites (collection/runtime), and optimize CI (GitHub Actions sharding, xdist parallelism, caching). Use when asked about pytest best practices, pytest 9.x features (subtests, strict mode, TOML config), pytest plugins (xdist/cov/asyncio/mock/httpx), or test performance/CI tuning.
BjornMelin/dev-skills/skills/streamlit-master-architect Skill
no license5★ repoArchitect-level Streamlit development for building, refactoring, debugging, testing, and deploying Streamlit apps (single-page or multipage) with correct rerun/state/caching/fragments, AppTest-based testing, custom components v2, safe theming/CSS, security-by-default, and Playwright MCP end-to-end automation.
BjornMelin/dev-skills/skills/vitest-dev Skill
no license5★ repoWorld-class Vitest QA/test engineer for TypeScript + Next.js (local + CI performance focused)
Python fastapi ddd testing skill
iktakahiro/python-fastapi-ddd-skill/skills/python-fastapi-ddd-testing-skill Skill
no license5★ repoGuides unit testing for Python DDD + Onion Architecture apps (Domain Entities/Value Objects and UseCases) using pytest and repository mocks, based on the dddpy reference. Use when adding tests, choosing what to mock, or structuring test folders for a DDD FastAPI project.
The same file is in 4 other repositories
chinkan/RustFox/.agents/skills/tdd Skill
5★ repoTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
The same file is in 9 other repositories