Browse, filter, and compare Agent Skills
Search 5,000 source-traceable Agent Skills. Review fit, compatibility, provenance, maintenance, and risk signals before installing.
- Catalog entities
- 5,000
- Page status
- Indexable hub
- Default order
- Evidence + freshness
Repository stars indicate source attention, not individual Skill quality. Automated source guides, editorial content, and test evidence are labeled separately.
Start with a workflow
5,000 matching Skills
obra/superpowers
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
obra/superpowers
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
obra/superpowers
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
obra/superpowers
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
obra/superpowers
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
obra/superpowers
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
obra/superpowers
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
obra/superpowers
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
obra/superpowers
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
obra/superpowers
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
obra/superpowers
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
obra/superpowers
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
affaan-m/ECC
agent-payment-x402
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.
affaan-m/ECC
codehealth-mcp
Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.
affaan-m/ECC
vite-patterns
Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.
affaan-m/ECC
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
affaan-m/ECC
cpp-coding-standards
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
affaan-m/ECC
hexagonal-architecture
Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services. Use when introducing or refactoring toward Ports and Adapters, or when domain logic has become entangled with I/O.
affaan-m/ECC
plan-orchestrate
Read a plan document, decompose it into steps, design a per-step agent chain from the ECC catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.
affaan-m/ECC
quarkus-tdd
Test-driven development for Quarkus 3.x LTS using JUnit 5, Mockito, REST Assured, Camel testing, and JaCoCo. Use when adding features, fixing bugs, or refactoring event-driven services.
affaan-m/ECC
prompt-optimizer
Use it for engineering and operations tasks; the detail page covers purpose, installation, and practical steps.
affaan-m/ECC
continuous-learning-v2
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination. Use when capturing lessons from a session, managing instincts, or promoting them into skills, commands, or agents.
affaan-m/ECC
ito-baskets
Read-only Itô basket and prediction-market data skill. Index the live basket catalog, compare a basket against user-supplied research or a watchlist, build a source-grounded market brief, or draft a non-executable planning worksheet. Use when a user asks to browse or index Itô baskets, compare a basket against notes or a thesis, research prediction-market events/venues/liquidity, or plan a basket or market idea without trading. Never advises, orders, trades, reserves, or executes.