SKILL.md Template: Copy-Paste, Generate and Download

The minimal SKILL.md template

Start from this copy-paste skeleton. Replace the placeholders and you have a valid skill:

---
name: my-skill
description: What this skill does and when the agent should use it.
---

# My Skill

Step-by-step instructions the agent should follow:

1. ...
2. ...
3. ...

SKILL.md frontmatter fields explained

Required (to run in any agent)

• name — Lowercase, kebab-case, and it must match the skill's folder name. Max 64 characters.
• description — One or two sentences: what the skill does and when to trigger it. Agents use this to decide whether to load the skill, so make it specific.

To publish on ProfessorGPT, also add version — a semantic version like 1.0.0.

Optional

• category — one of ProfessorGPT's categories (coding, devops, security, writing, productivity, …).
• tags — a YAML list of 3–6 kebab-case tags, e.g. [code-review, security].
• author — your name or handle.
• license — an SPDX identifier such as MIT or Apache-2.0.
• allowed-tools — a YAML list of tools the skill may use, e.g. [Read, Edit, Bash].
• metadata — a free-form map for anything extra.

The body below the frontmatter holds the instructions. Optional bundled files (scripts, references) can sit in the same folder.

A fuller, publishable SKILL.md

The same skeleton with the optional fields filled in — ready to publish:

---
name: code-reviewer
description: Reviews a diff for bugs, security issues, and style. Use when the user asks to review code or a pull request.
version: 1.0.0
category: coding
tags: [code-review, security]
author: your-handle
license: MIT
allowed-tools: [Read, Grep]
---

# Code Reviewer

1. Read the diff and note the intent of the change.
2. Flag correctness bugs first, then security, then style.
3. Give each finding a severity and a file:line reference.
4. Suggest a concrete fix for anything blocking.

Generate and download your SKILL.md

Fill the fields below to build a valid SKILL.md live, then copy it or download the file:

Domain-specific templates

Generic skeletons are everywhere; these vertical starters are what most people actually need.

Security review

---
name: security-review
description: Audits a code change for injection, auth, secrets, and unsafe defaults. Use when reviewing a diff or PR for security.
---

# Security Review

1. Check inputs for injection (SQL, shell, path, template).
2. Verify authz on every new endpoint and mutation.
3. Flag hardcoded secrets and unsafe default configs.
4. Report each finding with severity and a file:line reference.

Customer support reply

---
name: support-reply
description: Drafts an on-brand support reply from a ticket. Use when answering a customer message.
---

# Support Reply

1. Restate the customer's issue in one sentence.
2. Give the fix or next step in plain language.
3. Keep the tone warm, concise, and free of jargon.
4. End with a clear call to action.

E-commerce product description

---
name: product-description-writer
description: Writes SEO-friendly e-commerce product descriptions from a spec sheet. Use when drafting or rewriting a product listing.
---

# Product Description Writer

1. Read the product's attributes, materials, and key benefits.
2. Write a one-line hook, then 2–3 benefit sentences, then a bulleted spec list.
3. Use the target keyword naturally in the first sentence; no keyword stuffing.
4. Keep the tone on-brand and end with a short call to action.

SaaS onboarding

---
name: saas-onboarding-guide
description: Drafts a step-by-step onboarding message for a new SaaS user. Use when welcoming a signup or explaining first setup.
---

# SaaS Onboarding Guide

1. Identify the user's plan and primary use case.
2. Give the three highest-value first actions, in order.
3. Link each step to the relevant setting or doc.
4. Close with the tip that drives the "aha" moment and an offer to help.

Multi-model compatibility

The template above is model-agnostic. The same file installs into Claude (~/.claude/skills), Codex (~/.agents/skills), and Gemini CLI (~/.gemini/config/skills) — see the Claude and Codex guides for the exact install path per tool.

Common frontmatter mistakes

• name not matching the folder, or using spaces/uppercase.
• A vague description ("helps with code") — agents can't tell when to trigger it. State what and when.
• Body over ~500 lines — move long references into separate files.

Prefer a wizard?

The Skill Builder walks you through the same fields with validation, or browse real skills to adapt one.