Where can I find real SKILL.md examples?

The three complete examples on this page (commit message writer, code review checklist, README generator) are copy-paste ready. You can also browse the full public catalog for hundreds more.

How do I install one of these examples?

Create a folder named after the skill in your agent's skills directory (~/.claude/skills, ~/.agents/skills, or ~/.gemini/config/skills) and save the example as SKILL.md inside it.

Do these examples work in every agent?

Yes — they use the open SKILL.md standard, so the same file works in Claude, Codex, and Gemini CLI / Antigravity. Only the install folder differs.

Can I edit an example?

Absolutely. Change the name, description, and steps to fit your workflow, or generate a custom one with the free Skill Builder.

SKILL.md Examples You Can Copy and Paste

Complete, real SKILL.md files you can copy and drop straight into your skills folder — with the full source visible. Each one works in Claude, Codex, and Gemini CLI.

What a SKILL.md example actually is

A skill is a folder with a SKILL.md file: YAML frontmatter (name + description) and a markdown body of instructions. It is not a resume/CV "skills" section — that's an unrelated meaning of the word. The examples below are complete, working agent skills.

Example 1: Commit Message Writer

Writes clean, conventional commit messages from a staged diff.

---
name: commit-message-writer
description: Writes a conventional-commit message from the staged diff. Use when the user asks to write or improve a commit message.
---

# Commit Message Writer

1. Read the staged diff.
2. Pick the type: feat, fix, docs, refactor, test, or chore.
3. Write a concise summary line (max ~72 chars), imperative mood.
4. Add a short body only if the change needs context.

Example 2: Code Review Checklist

Reviews a diff in a fixed, repeatable order.

---
name: code-review-checklist
description: Reviews a diff for correctness, security, and style in a fixed order. Use when the user asks to review code or a PR.
---

# Code Review Checklist

1. Correctness: logic, edge cases, error handling.
2. Security: input validation, authz, secrets.
3. Tests: are the changes covered?
4. Style: naming and consistency last.
5. End with approve or request-changes and a one-line summary.

Example 3: README Generator

Drafts a README from a project's files.

---
name: readme-generator
description: Generates a README from the project structure and package metadata. Use when the user asks to write or update a README.
---

# README Generator

1. Detect the stack from manifest files (package.json, pyproject, etc.).
2. Write sections: title, what it does, install, usage, license.
3. Include a runnable quick-start command.
4. Keep it scannable — short paragraphs and code blocks.

The same skill across Claude, Codex, and Gemini CLI

Every example above is model-agnostic. Install the same file into:

Claude — ~/.claude/skills/<name>/SKILL.md
Codex — ~/.agents/skills/<name>/SKILL.md
Gemini CLI / Antigravity — ~/.gemini/config/skills/<name>/SKILL.md

See the Claude, Codex, and Gemini guides for the exact steps.

Adapt an example into your own skill

Start from any example above, or use the Skill Builder to generate one from your own inputs. Want more? Browse the full catalog of ready-made skills.