Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
OpenAISkillopenai/codex/codex-rs/skills/src/assets/samples/review-agent/SKILL.md
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
Steady14 mentions in 2 weeks
12 projects use a version of this
OpenAISkillopenai/codex/codex-rs/skills/src/assets/samples/skill-creator/SKILL.md
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
Steady14 mentions in 2 weeks
189 projects use a version of this
Often used withtaskflow-inbox-triagemermaid-diagram-generatorecosystem-reference
OpenAIReads credentialsSkillopenai/codex/codex-rs/skills/src/assets/samples/skill-installer/SKILL.md
Install 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).
Steady14 mentions in 2 weeks
46 projects use a version of this
MicrosoftReads credentialsSkillmicrosoft/generative-ai-for-beginners/.github/skills/azure-openai-to-responses/SKILL.md
Migrate Python apps from Azure OpenAI Chat Completions to the Responses API. Covers AzureOpenAI/AsyncAzureOpenAI client migration to the v1 endpoint, streaming, tools, structured output, multi-turn, EntraID auth, and model compatibility checks. Python-focused, Azure OpenAI-specific. USE FOR: migrate to responses API, switch from chat completions, openai responses, upgrade openai SDK, responses API migration, move from completions to responses, gpt-5 migration, azure openai python migration, chat completions to responses, AzureOpenAI to OpenAI client, python azure openai upgrade. DO NOT USE FOR: building new apps from scratch (start with responses directly), Node/TypeScript/C#/Java/Go migrations (this skill is Python-only), Azure infrastructure setup (use azure-prepare), deploying models (use microsoft-foundry).
Steady15 mentions in 2 weeks
1 project uses a version of this
SupabaseSkillsupabase/supabase/.agents/skills/api-types/SKILL.md
Maintain Supabase API types. Use when changing generated API type declarations, OpenAPI schemas, or investigating API type deployment drift.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/ask-the-docs/SKILL.md
Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding minimalism) when proposing or critiquing changes. Use when the user asks "how does X work in the docs app?", "where does Y live?", "is this approach OK for the docs app?", or before writing non-trivial changes under apps/docs/ — especially anything touching the MDX pipeline, markdown generation, content components, federated docs, or contributor-facing authoring patterns, or feature flags and experiments. Can answer architecture questions with Mermaid diagrams when helpful.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/clickhouse-logs-queries/SKILL.md
Write, review, and migrate Supabase logs queries against the ClickHouse-backed `logs` table (the `logs.all.otel` analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the `log_attributes` map, querying a log `source` (edge_logs, postgres_logs, auth_logs, etc.), translating an old BigQuery `cross join unnest(metadata)` logs query to ClickHouse, or wiring analytics log SQL in `apps/studio/data/logs` and `apps/studio/components/interfaces/Settings/Logs`. Reach for it even when the user just says "logs query", "Logs Explorer", or pastes a BigQuery logs query to convert, not only when they name ClickHouse.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/code-review/SKILL.md
Review repository changes for correctness, type boundaries, structural quality, and meaningful test coverage. Use for read-only code or PR assessments and development-task readiness checks.
Often used withclose-specadd-new-modelcompare-screenshots
SupabaseSkillsupabase/supabase/.agents/skills/copywriting/SKILL.md
Write or audit UI copy (buttons, labels, empty states, error messages, tooltips, form text) anywhere in the monorepo. Load it before shipping or reviewing any user-facing text — including when copy is incidental to the task, like a new feature that adds buttons, toasts, dialogs, or validation messages.
188 projects use a version of this
SupabaseReads credentialsSkillsupabase/supabase/.agents/skills/dev-toolbar-review/SKILL.md
Safety rules for the dev toolbar, PostHog client, and feature flags. Use
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/edit-the-docs/SKILL.md
Restructure, reorder, and improve existing Supabase docs pages under apps/docs: clarity, connective text, section grouping, and brevity. Use when asked to edit, reorganize, restructure, tighten prose, add glue between sections, or split a page edit into stacked PRs. Not for net-new feature drafts, which belong to write-the-docs, and not for PR triage or verification, which belong to review-the-docs.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/pm-the-docs/SKILL.md
Docs-PM decision support for the "Write the docs" authoring process — makes audience, stage, and cross-cutting scope calls during the Frame and Shape stages (including cross-repo product lookup via universe when accessible, else the public OSS path), and helps decide when a docs question needs to self-serve vs. escalate to a docs PM. Use when framing a new docs page or launch, deciding what product stage or audience a feature targets, judging whether a docs question needs PM sign-off, or confirming which product repos a launch spans.
SupabaseSkillsupabase/supabase/.agents/skills/react-hook-form/SKILL.md
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
8 projects use a version of this
SupabaseReads credentialsSkillsupabase/supabase/.agents/skills/review-the-docs/SKILL.md
Review Supabase docs changes locally in your `supabase/supabase` checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review). Covers markdown pipeline, MDX content, tutorials, examples, Studio links, and docs tooling. Use when asked to review docs PRs, self-review a draft branch, check who has approved, verify build output, or evaluate supabase/supabase documentation changes.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/safe-sql-execution/SKILL.md
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint that builds/returns SQL for database objects (tables, views, functions, DB triggers, indexes, RLS policies); interpolating a schema/table/column/search/route-param value into SQL text; storing, fetching, or re-running SQL that round-trips from the database (a policy's definition, a function/view definition, a snippet's saved content); and any "Run"/"Apply"/"Execute" action that sends SQL to a project's database (SQL editor run-selection, policy editor apply, snippet runner). Load this BEFORE writing such code, not only when reviewing a finished diff. Skip only for changes that never touch SQL text or execution — styling, unrelated data hooks, non-SQL form validation, or UI layout work.
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/studio-e2e-tests/SKILL.md
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
No other project uses it yet
SupabaseSkillsupabase/supabase/.agents/skills/studio-error-handling/SKILL.md
Error display and troubleshooting pattern for Supabase Studio. Use when
SupabaseReads credentialsSkillsupabase/supabase/.agents/skills/studio-mock-api-tests/SKILL.md
Component tests for Supabase Studio that mock API requests at the
SupabaseSkillsupabase/supabase/.agents/skills/studio-queries/SKILL.md
React Query conventions for data fetching in Supabase Studio. Use when
SupabaseSkillsupabase/supabase/.agents/skills/studio-shortcuts/SKILL.md
Keyboard shortcut conventions for Supabase Studio. Use when adding a
No other project uses it yet
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.
