Explore skills
Showing 19021–19050 of 71536 skills
Use when creating or updating a Makefile for a project, especially when standard targets (build, test, lint, format, etc.) are missing or when modifying targets that may already be wired into other tooling. Not for debugging why a build fails.
Ovid/paad
Stars: 154Claude CodeCodexUse when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing a spec, PRD, requirements doc, or design plan before implementation begins — especially when the doc feels too big, bundles unrelated features, may contradict the current codebase, or seems vague, infeasible, or thin on security and error handling. Not for cross-checking a spec against a plan — that's /alignment.
Ovid/paad
Stars: 154Claude CodeCodexUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is /pushback.
Ovid/paad
Stars: 154Claude CodeCodexAnalyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.
Ovid/paad
Stars: 154Claude CodeCodexUse when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same module
Ovid/paad
Stars: 154Claude CodeCodexUse when auditing a user-facing app — web, mobile (iOS/Android/React Native/Flutter), desktop, CLI, or games — for accessibility barriers or WCAG 2.2 conformance, before shipping UI changes, or in response to concerns about screen-reader, keyboard, low-vision, motor, cognitive, or photosensitive users. Not for general bug hunting or code correctness.
Ovid/paad
Stars: 154Claude CodeCodexUse when assessing the architectural health of a codebase — before a major refactor, when onboarding to an unfamiliar repo, after rapid growth, when planning a redesign, or to surface structural strengths and risks before they become expensive. Not for fixing what it finds, and not for reviewing a branch diff.
Ovid/paad
Stars: 154Claude CodeCodexUse when verifying that requirements/specs/PRDs and their implementation plans match — before starting work, after a spec or plan update, or when suspecting coverage gaps, scope creep, or design drift between intent and action documents. Needs both documents; not for checking code against a spec.
Ovid/paad
Stars: 154Claude CodeCodexEXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md and paad/security/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
Ovid/paad
Stars: 154Claude CodeCodexUse when working through architectural flaws documented in a paad/architecture-reviews/ report — selecting which flaws to fix, resuming a partial fix session across multiple sittings, or applying structural changes that need to be tracked back to a report. Not for producing that report — run /agentic-architecture first if there isn't one.
Ovid/paad
Stars: 154Claude CodeCodexUse when a session is running out of context and the work needs to continue in a fresh one, or when starting a session meant to pick up where an earlier one stopped. Not for compacting in place — that is /compact — and not for specifying work that has not started, which is a plan.
Ovid/paad
Stars: 154Claude CodeCodexUse when creating or updating a Makefile for a project, especially when standard targets (build, test, lint, format, etc.) are missing or when modifying targets that may already be wired into other tooling. Not for debugging why a build fails.
Ovid/paad
Stars: 154Claude CodeCodexUse when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill
Ovid/paad
Stars: 154Claude CodeCodexUse when reviewing a spec, PRD, requirements doc, or design plan before implementation begins — especially when the doc feels too big, bundles unrelated features, may contradict the current codebase, or seems vague, infeasible, or thin on security and error handling. Not for cross-checking a spec against a plan — that's /alignment.
Ovid/paad
Stars: 154Claude CodeCodexUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is /pushback.
Ovid/paad
Stars: 154Claude CodeCodexAnalyzes a repository and any existing test suite, grades existing tests for weakness, classifies mocks, emits a phased roadmap for building a test suite that catches real regressions, then executes those phases one at a time. Use when planning or building a test suite, assessing whether existing tests are worth anything, adding tests to a legacy codebase, or when the user mentions test coverage, test strategy, or weak tests. Not for reviewing a branch for bugs, and not for fixing the bugs it logs.
Ovid/paad
Stars: 154Claude CodeCodexUse when making a small, quick change — a bug fix, typo, minor feature, tweak, or anything the user calls "vibe coding" — that looks like 1-3 files in the same module
Ovid/paad
Stars: 154Claude CodeCodex对多 Sheet Excel 进行智能清洗、跨表核对与可视化分析。。
OpenSenseNova/SenseNova-Skills
Stars: 6kClaude CodeCodexReview code changes using Hyperlane monorepo coding standards. Use when reviewing PRs, checking your own changes, or doing self-review before committing.
hyperlane-xyz/hyperlane-monorepo
Stars: 77Claude CodeCodexThe alphabetical-sort invariants the hyperlane-registry CI / CodeRabbit enforces on warp route YAML (deploy.yaml and config.yaml) — top-level chain entries sorted by chain name, and keys within each entry in strict alphabetical order — plus the canonical per-file key orderings and a verification pass. Referenced by any warp deploy/update skill that writes or edits a registry YAML file.
hyperlane-xyz/hyperlane-monorepo
Stars: 77Claude CodeCodexCanonical legend for expanding a `less than KEY_PROTOCOL_VALUEgreater than ` placeholder into a shell substitution based on the key-context artifact's `source` field, plus the mandatory `pnpm --silent` rule that keeps the resolved key out of logs and the display-the-key-name-before-CONFIRM disclosure. Referenced by every warp deploy/update skill that passes a `--key.protocol` flag.
hyperlane-xyz/hyperlane-monorepo
Stars: 77Claude CodeCodexAutomate browser interactions, test web pages and work with Playwright tests.
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Stars: 406Claude CodeCodexShows available skills, common workflows, and quick reference for the plugin. Use when the user asks for help, what skills are available, or how to do something.
bitwize-music-studio/claude-ai-music-skills
Stars: 672Claude CodeCodexCheckpoint durable decisions, fixes, constraints, results, and open next steps from the current Codex task into scoped Waggle project memory.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodexPrime a Codex task with the most relevant Waggle project history before starting or resuming substantial work.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodexRecall project-scoped Waggle history about a topic, component, decision, bug, experiment, or implementation attempt.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodexUse when the user asks how clueless works, what its commands or levels are, or types /clueless-help.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodexИспользуй только внутри активного Codex Project Autopilot-проекта для automation-задач по его плану; не включай для обычных скриптов вне автопилота.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodexИспользуй только внутри активного Codex Project Autopilot-проекта, когда data-layer уже относится к плану автопилота.
hashgraph-online/awesome-codex-plugins
Stars: 1.5kClaude CodeCodex