Explore skills
Showing 10021–10050 of 77079 skills
Install, instrument and verify a web app end to end without pausing for a human. Use in an autonomous or goal-mode agent, in CI, or in any client that asks for approval on every command: it never says "restart your client" or "open a browser", because it takes a route that needs neither. Prefer the normal reticle skill when a human is present and can answer.
reticlehq/reticle
Stars: 1.2kClaude CodeCodexInstall Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexUse when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexUse when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to official OpenAI domains.
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexPerform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexRepository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexUse only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
foryourhealth111-pixel/Vibe-Skills
Stars: 3.8kClaude CodeCodexUse when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse at the start of new project onboarding, PR lifecycle work including PR checks, or any change to what the product does — a feature, a behavior change, or a bug fix. Not for continuing work already routed to a workflow, non-PR questions, checks, explanations, or edits that change no behavior.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when finished work needs to ship as a pull request, or when creating, syncing, updating metadata, checking status, monitoring CI, or addressing review comments on a PR. Not for reviewing a PR you are not shipping.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexUse when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or architecture decision.
JetBrains/thinkrail
Stars: 8.3kClaude CodeCodexStop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".
github/awesome-copilot
Stars: 41kClaude CodeCodexAddress PR reviewer feedback by evaluating comments, proposing fixes, and executing after user approval. Use when the user wants to handle review comments on an existing PR, address PR feedback, fix PR comments, respond to reviewer suggestions, or process code review feedback. Triggers on "address PR feedback", "handle review comments", "fix PR comments", "respond to PR review", "process reviewer feedback", or when given a PR number/URL with intent to address its comments.
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexReview code changes against project architecture, style, and conventions
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexProvision a disposable Jurassic Ninja store for the Maestro smoke suite, connect Jetpack to the developer's own WordPress.com test account, create WooCommerce API keys, and write .maestro/.env.local. Use when Maestro setup is missing, when .env.local points at an expired store, or when a clean store is wanted.
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexPrepare the local environment for the Maestro smoke-test suite — verify tooling, select a device, collect the APK if needed, validate the .env file by variable name only, then hand the user the exact lab-store CLI command to run or run it on request.
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexGenerate screenshot coverage for screen-level Compose previews from the current diff or a specific target, check required visual and data variations, and produce a compact visual report
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexBuild, install, and visually verify the app on an Android emulator or device. Uses the Android CLI for agents (android) when available with a full mobile-mcp/adb fallback.
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexRun the Android AI Assistant headless smoke regression harness without launching UI.
woocommerce/woocommerce-android
Stars: 320Claude CodeCodexCreate or update a pull request
AllYourBot/hostedgpt
Stars: 513Claude CodeCodexRead one conversation window and return every independently mutable claim it states, one record each, with who or what it is about, whether it happened or stands, and the words that carry its time. Used by the memory extraction model on every conversation window; the engine resolves dates, validates keys, and repairs format.
sno-ai/sno-station
Stars: 1kClaude CodeCodexReact-specific code shape in the Grida editor. Hooks cannot be tested or benchmarked and silently break tuned UX under layered composition, so they are barred from the engine and main system — load-bearing logic lives in classes and namespaces, hooks only as thin edge wires. `data-testid` follows component-root discipline: one per significant component, not scattered. Use when authoring React in `editor/grida-canvas-react/`, `editor/components/`, `editor/scaffolds/`, or `editor/app/*`.
gridaco/grida
Stars: 2.7kClaude CodeCodexTypeScript code shape inside a well-named module — taste, not lint. Prefer one class or namespace per file (the unit a test targets) over scattered free exports; consolidate related code, don't fragment. The unit of code should be the unit of spec. Use when authoring TS in `editor/grida-canvas*`, `editor/lib/`, or `packages/*`. Sibling to the `naming` skill; React-specific shape lives in `code-react`.
gridaco/grida
Stars: 2.7kClaude CodeCodexUse BEFORE editing any file in `supabase/migrations/` or `supabase/schemas/`, OR when the user runs a `/database` subcommand (`compact local migration`, `rls scenarios`, `align`). Encodes the three contracts that protect the Grida database layer: applied migrations are immutable, RLS implementation mirrors tests (never the reverse), `schemas/*.sql` is the human-readable end-state. Companion to `supabase/AGENTS.md` (RLS, grants, security boundaries).
gridaco/grida
Stars: 2.7kClaude CodeCodexDecide which family a doc belongs to before drafting — SDK/developer, user/product, or working-group (WG) — since family sets the audience, home, and tone. Use when creating, moving, or restructuring docs, when unsure which directory a doc belongs in, or when a request says "document this" / "write docs for X" without naming the kind. Routes to the specialized skill for each family.
gridaco/grida
Stars: 2.7kClaude CodeCodex