Skills

A

agents-consilium

codealive-ai / ai-driven-development

Run external coding agents (Codex, Claude Code, OpenCode, native Grok Build, Gemini) as independent reviewers, stateful repository researchers, or single-agent implementers. Use for multi-model opinions and code review, steerable Grok research, full-access delegation, long-running work, or reattaching to delegated runs. Not for simple questions answerable directly from docs or the current codebase.

No description yet

A

anti-ui-slop

discountry / ritmex-skills

Detect, review, prevent, and remove AI-generated UI convergence patterns ("AI slop") in frontend code. Use whenever building or styling a UI, reviewing frontend changes, refining visual design, or when the user asks to remove the AI look, make an interface feel human-designed, polish a page, audit UI quality, or explain why a design feels generic. Covers HTML, CSS, JSX/TSX, Vue, Svelte, and Tailwind; audits 46 catalogued patterns plus composition-level checks, separates source-confirmed, rendered, and judgment-based evidence, and rewrites authorized code toward a product-specific design direction without requiring external dependencies.

A

api-tests

laurigates / claude-plugins

API contract testing with Pact, OpenAPI validation, and Zod/AJV schemas. Use when setting up contract tests, validating OpenAPI compliance, or adding breaking-change CI checks.

A

architecture-refiner

gravito-framework / gravito

Expert in Gravito architecture and clean code. Trigger this for refactoring, design pattern implementation, or architectural audits.

A

assess-milestone

jayden-dang / skills

Produces a verdict on whether a milestone delivered what it promised, read fresh from the specs, the tests, and git. Run it with /assess-milestone.

A

awesome-dependency-audit

khasky / awesome-agent-skills

Read-only supply-chain audit of packages and agent extensions: lockfiles, typosquats, dependency confusion, install scripts, licenses, CVEs. Use when asked if a package, manifest change or bot bump is safe.

A

awesome-regression-sweep

khasky / awesome-agent-skills

Read-only sweep for regressions against a recorded baseline: typecheck, lint, test suites, wire contracts, generated-file drift, downstream builds, deploy drift. Use to verify everything before or after a deploy.

B

best-practices-guidelines

oimiragieo / agent-studio

Specifies best practices, including following RESTful API design principles, implementing responsive design, using Zod for data validation, and regularly updating dependencies. This skill promotes modern coding standards and helps developers write consistent, maintainable code.

B

big-review

martin2844 / skills

Deep, evidence-first code review for local diffs and GitHub PRs. Use for "big review", "deep review", "review my code", "pre-PR review", "review-proof this", "rabbit review", "fast review", "triage this PR", semantic correctness review, failure-path review, and high-signal PR review.

B

blitz-reviewer

api-blitz / skills

Reviews a Blitz API integration against the live Blitz docs before you run it. Confirms the Blitz MCP is installed (and pushes to add it), checks the blitz-api SDK and the Blitz skills are on the latest version, scans your project for wrong SDK methods, malformed request bodies, and case-sensitive enum typos by validating each call against the MCP's OpenAPI specs and normalization pages, and reads your API key's per-endpoint rate limits and credits to flag throughput left on the table. Reports a pass/warn/fail checklist and applies each fix only after you confirm. Use when the user says "review my Blitz integration", "audit my Blitz code", "check my Blitz setup", "is my Blitz usage correct", "preflight my Blitz job", or before running a Blitz job at scale.

B

but-for-real

shpigford / skills

Force a skeptical second pass on your own work. Because 'it should work' has never once been true.

C

cirrus-labs

membranedev / application-skills

Cirrus Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cirrus Labs data.

C

clj-refactor

humorless / clj-native-agent

Scan files for mechanism/policy separation opportunities

C

code-review

csark0812 / toolbox

Use when the user asks to review a branch, PR, diff or change before merging, or for a focused risk or quality check. Read-only unless fixes are asked for. Not hunch settlement or document critique

C

code-review

microsoft / vscode

Review code changes for correctness, regressions, and unintended scope. Use when reviewing a pull request, branch, commit, patch, or local diff, including when invoked with /code-review.

C

code-upgrade

robinebers / skills

Engineering-discipline toolkit for non-technical users working with AI coders. Wields KISS, DRY, YAGNI, fail-fast, and idempotency as commands. Use when the user asks to audit, simplify, clean up, dedupe, or harden code; or says "make this simpler", "any duplicates?", "is this safe to run twice", "explain this app", "find dead code", "simplify the plan", or "find silent failures".

C

codemagic

membranedev / application-skills

Codemagic integration. Manage data, records, and automate workflows. Use when the user wants to interact with Codemagic data.

C

conda-recipe

delphine-l / claude_global

Expert in building and testing conda/bioconda recipes, including recipe creation, linting, dependency management, and debugging common build errors

C

confess

b-open-io / prompts

Proactive self-audit covering incomplete changes, untested assumptions, pattern violations, buried concerns, and cleanup debt. Invoke before ending a session, marking a task done, or saying "complete", and when the user asks "are you sure?", "did you miss anything?", "anything else?", or "audit your work". Do not wait to be asked.

C

configure-metrics

coval-ai / coval-external-skills

Select and configure a Coval metric for a concrete product criterion, choosing transcript, audio, trace or deterministic evidence and testing the result. Use for metric creation or scoring design, not for final human calibration.

Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file. Covers crit comment, crit share, crit unpublish, crit pull, crit push, review file format, and resolution workflow. Not for invoking an interactive review loop — that's the `/crit` command.

D

design-review

aa-on-ai / agentic-design-system

Judge visual and frontend work for product fit, information architecture, reference fidelity, craft, and verified behavior. Scope review to the requested surface and change.

D

design-ship

yonatangross / orchestkit

One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to disk, run /ork:design-import instead.

D

design-sync

chmouel / lazyworktree

Check DESIGN.md synchronization with codebase architecture

D

desloppify

fasalzein / desloppify

Code quality scanner. Detects AI-introduced anti-patterns across many categories. Run the CLI, triage results, fix on isolated git worktrees. Trigger: desloppify, clean up code, remove slop, code quality, dead code.

D

dotnet-testing-unit-test-fundamentals

kevintsengtw / dotnet-testing-agent-skills

A specialized skill for .NET unit testing fundamentals and the FIRST principles. Use when you need to create unit tests, understand testing fundamentals, learn the 3A Pattern, or master testing best practices. Covers the FIRST principles, the AAA Pattern, Fact/Theory, the test pyramid, and more. Make sure to use this skill whenever the user mentions unit testing fundamentals, FIRST principles, AAA/3A pattern, or wants to learn how to write basic .NET tests, even if they don't explicitly ask for fundamentals guidance. Keywords: unit test, 單元測試, unit testing, test fundamentals, 測試基礎, FIRST principle, FIRST 原則, 3A pattern, AAA pattern, Arrange Act Assert, Fact, Theory, InlineData, 如何寫測試, testing best practices, 建立單元測試

F

filing-bug-reports

matlab / simulink-agentic-toolkit

Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.

F

flutter-mcp

arenukvern / mcp_flutter

Use this skill whenever inspecting, interacting with, or live-editing a running Flutter app via the Flutter MCP toolkit server (`mcpServers` key **`flutter-mcp-toolkit`**, or legacy **`flutter-inspector`**). Covers preflight, snapshot/tap/enter/scroll loop, hot-reload validation, and error envelope parsing.

F

flutter-mcp-toolkit-inspect

arenukvern / mcp_flutter

Read state from a running Flutter app — semantic snapshot, view details, errors, screenshots, VM info. Use when you need to understand what the app is showing.

G

game-studio-harness

akillness / jeo-skills

Five-role game production studio harness: director, numeric-balance designer, revenue-band PM, verification-strict programmer, archetype-rotation QA. Runs the 3-stage operating cycle (concept/presentation/core build → balance/core-loop/novelty → ops stability/play impact) behind 8 numeric quality gates with survey-grounded trends, signed designer↔PM negotiation records, and QA broadcast discipline. Writes the repository rule file (CLAUDE.md/AGENTS.md) so the contract outlives the session, and keeps one live `_workspace/current/` beside a read-only archive.

G

go-testing

o-marsters-1997 / my-claude-code

How Go tests are written in these repos: assertions, tables, test doubles, helpers, async waits, golden files, fuzzing, benchmarks, and integration tests against a real Postgres via the bundled pgtest helper (one shared testcontainer, a fresh database per test). TRIGGER — load BEFORE writing, editing, or reviewing any *_test.go file, testdata/ golden file, fuzz target, or benchmark, or when the task mentions go test, test helper, fake, mock, stub, table test, testcontainers, TestMain, test database, flaky test, or coverage in a Go repo. Plain requests count: “write the tests,” “add a test for this,” “fix the failing test,” or a feature task whose last step is testing it. Load alongside go-idiomatic and tdd, not instead of them. SKIP when no Go test code is written or judged

G

groundlight

membranedev / application-skills

Groundlight integration. Manage data, records, and automate workflows. Use when the user wants to interact with Groundlight data.

H

ha-validate

laurigates / claude-plugins

Validate Home Assistant YAML for syntax errors, undefined secrets, and duplicate keys. Use when validating HA config, diagnosing YAML errors, or running hass check_config.

I

implement

toy-crane / skills

Implement or resume settled work from a selected spec folder as one handoff bundle. Use when the user provides a `docs/specs/SLUG/` folder and wants its settled spec or approved tasks completed in the current checkout with verification, one completed and triaged automated code review, and a runnable product handoff when the repository exposes one through a local server.

L

laravel-testing

leeovery / agentic-skills

Comprehensive testing patterns with Pest. Use when writing or modifying tests, mocking, factories, or test patterns.

L

ln-23-test-suite-auditor

levnikolaevich / claude-code-skills

Audits existing tests for meaningful coverage, trustworthy oracles, and maintenance value. Not for test implementation or a single delivery review.

L

logic-diff

hyhmrright / logic-lens

Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user shares a refactor, rewrite, migration, or A/B implementation and wants to confirm behavior is unchanged — "did I break anything", "is this equivalent", "are these equivalent", "semantically equivalent", "are these two implementations semantically equivalent", "check my refactor", "same behavior after the change?", "does my rewrite produce the same output", "switched from X to Y — same results?". SCOPE HARD RULE: requires two code versions (A and B). A single version for bug-finding uses logic-review; one version + a failing test uses logic-locate; explaining what one piece of code does uses logic-explain; codebase audit uses logic-health. Do NOT trigger for: single-version review, performance comparison, design-quality comparison, or "which is better-written" questions.

M

maintainable-tests

jpcaparas / skills

Guide maintainable tests as behavior documentation with isolated side effects, compatibility coverage, and reliable assertions. Use for tests, fixtures, mocks, regressions, reviews, and testability changes. Skip disposable work.

M

meta-reviewing-reviewing

agents-inc / skills

Code review patterns, feedback principles. Use when reviewing PRs, implementations, or making approval/rejection decisions. Covers self-correction, progress tracking, feedback principles, severity levels.

M

migrate-to-testomatio

testomatio / skills

Migrate tests to Testomat.io from TestRail, XRay, Testmo, QMetry, Allure TestOps, TestCaseLabs, Qase, Zephyr, QTest, CSV/XLSX, or an unsupported TMS needing a custom converter or API script. Use when user wants to import tests from another TMS, move test suites to Testomat.io, or convert an export file to Testomat.io format.

O

oh-precommit-codecheck

openharmonyinsight / openharmony-skills

Run local code quality checks covering a subset of OpenHarmony gate CI (copyright, CodeArts C/C++) plus additional local checks (pylint/flake8, shellcheck/bashate, gn format). Use before committing to reduce gate failures. Triggers on: /oh-precommit-codecheck, "门禁检查", "门禁预检", "检查代码", "run codecheck", "check code quality", "lint my code", "代码检查", or after completing code implementation. WHEN to use: before git commit, before creating PR, after modifying C/C++/Python/Shell/GN files, when gate CI fails with codecheck defects, or when you want to preview what gate will flag.

O

oxidizer-workflow

rysweet / amplihack

Automated Python-to-Rust migration via iterative convergence loops. Treats the Python codebase as the living specification and produces a fully-tested Rust equivalent with zero-tolerance parity validation. Use when migrating Python modules, libraries, or CLIs to Rust. Activates for: migration, oxidize, python to rust, port to rust, rewrite in rust.

P

planning-validate

drillan / speckit-gates

Validates planning artifacts (spec.md, plan.md, data-model.md, contracts/) for quality, completeness, and consistency. Checks for mandatory sections, cross-artifact consistency, and constitution compliance. Always run after /speckit.plan completes.

P

point

nmnmcc / skills

Use for one local cause-and-effect change with a focused proof.

P

pr-review

onekeyhq / app-monorepo

Security-first PR review checklist for this repo. Use when reviewing diffs/PRs, especially changes involving auth, networking, sensitive data, or dependency/lockfile updates. Focus on secret/PII leakage risk, supply-chain risk (npm + node_modules inspection), cross-platform architecture (extension/mobile/desktop/web), and React performance (hooks + re-render hotspots). Avoid UI style nitpicks. PR Review.

P

premortem

boshu2 / agentops

Find how a rollout plan could fail before committing to it. Use when: asked what could go wrong or to poke holes in a plan.

P

profile-dart-code

kevmoo / dash_skills

Profile Dart command-line applications using the VM Service protocol to capture CPU samples and identify performance bottlenecks. Helps agents automate CPU profiling, generate function call breakdown summaries, and export JSON profiles without a browser or DevTools.

P

project-audit

fearovex-labs / agent-config

Deep diagnostic of Claude/SDD configuration. Read-only. Produces audit-report.md consumed by /project-fix. Trigger: /project-audit, audit project, review claude config, project health check.

P

python-tdd-with-uv

revitalb-port / skills-registry-demo

Test-driven development in Python using uv as the package manager. Covers the red-green-refactor cycle, vertical slicing, and uv project setup.

P

python-testing

paldom / python-skills

Builds pytest infrastructure for a Python package — layout and config, coverage gates with fail_under, Hypothesis property-based tests, mutation testing to catch weak or agent-gamed tests, multi-version runs via tox, nox, or uv. Use for 'set up pytest', 'add coverage', 'test on multiple Python versions'. Not for writing tests for one file, fixing a single failing test, or CI workflow YAML.

Use when testing or verifying one activity end to end from an act_id, requirements, configuration, code, and real business evidence, including automated QA, 活动测试, 自动化测试, 测试活动, or 验证活动.

Q

qa-automation

fikyanggra / skills

Portable QA automation agent for creating or updating automation scripts from qa-planner contracts, qa-executor signals, approved test cases, manual requests, Notion pages/databases/data sources, Plane.so work items/cards/sub-work-items, or Notion/Plane MCP payloads. Use when asked to generate or update Playwright/Cypress/other repo-native automation, update flaky or selector-broken scripts, validate automation patches, update Notion Automation Status, comment/update Plane descriptions or states, prepare automation_change_set.json, perform managed Notion/Plane sync, bridge Notion and Plane refs, produce script review or promotion review packages, or hand automation status updates back to QA agents.

No description yet

Q

qa-gate

marcioaltoe / skills

Execute the self-contained final QA gate as a Spec's authored terminal `qa` Task — derive a resumable QA matrix from the PRD and task evidence, execute real user flows through every declared surface, probe high-risk user behavior, capture auditable evidence, classify findings by user impact, and write the spec-local dated QA report. Do not use as a substitute for implementation tests or a broad standalone QA knowledge base.

No description yet

Q

qt-unittest-make

re2zero / deepin-skills

Use when users request generating unit tests for Qt modules or classes, completing test cases, or creating test files. Supports module batch generation and incremental completion.

Q

quick-eval

coval-ai / coval-external-skills

Execute a bounded Coval evaluation on explicit test cases, then audit conversation, recording and metric evidence. Use when the user requests a run; does not automatically rerun, tune an agent or schedule evaluations.

R

refactoring-guide

terrylica / cc-skills

SOTA refactoring and modularization principles that LLMs systematically miss. Covers language-agnostic principles plus.

R

review-go

existential-birds / beagle

Comprehensive Go backend code review with optional parallel review areas. Use when reviewing changed Go files; detects BubbleTea, Wish SSH, and Prometheus and loads the matching review skills.