How do I make a SKILL.md?

Start with a clear skill name, description, trigger phrases, non-goals, workflow steps, validation gates, and safety constraints. A usable skill often includes a full folder structure, not just one markdown file.

What should be in a skill folder?

A typical skill folder contains SKILL.md plus optional references, optional scripts, optional assets, and optional platform files such as agents/openai.yaml when needed.

Should I put secrets in a public skill?

No. Public skills should describe credential handling and approval rules at a high level. They should never contain secret values, private keys, or instructions telling users to paste credentials into public files.

Skill Generator Create a SKILL.md file and full skill folder

Create a SKILL.md file and full AI skill folder from docs, URLs, and notes.

Use this SKILL.md generator to turn documentation, pasted knowledge, and product requirements into portable skills for Codex, Claude, OpenAI Skills, and OpenClaw. It writes the core file, builds the folder structure, preserves source material as references, and adds optional scripts only when they help.

Start Building How it works

SKILL.md + folder tree core files

URLs / docs / paste input sources

Source pack + ZIP download-ready

Bundle

Create the whole skill folder

Builds `SKILL.md`, `references/`, optional `scripts/`, optional `agents/openai.yaml`, a test prompt set, and a ZIP you can hand off immediately.

Research

Grounded by real source material

Pull from a URL directly, ask for official-source research, or upload a document so the generated skill reflects real documentation instead of generic filler.

Sources

Reference files agents can use offline

Fetched URLs, uploads, and pasted material are preserved inside the bundle so the agent can read them later instead of being forced back onto the internet.

Step 1

Describe the skill

Skill title Skill slug

What should this skill do?

Category Choose an existing category or add a new one. Difficulty

Target platforms

Choose where the generated skill should work.

Trigger phrases Do-not-trigger cases

Expected outputs

Step 2

Add source material

Add docs, URLs, uploads, or notes the model should use when building the skill.

Paste raw notes, SOPs, or docs

Fetch a URL

Research official sources

Upload a document

Supported: TXT, MD, PDF, DOC, DOCX. Uploads are preserved as raw source files, then distilled into a reusable knowledge layer for generation.

Source Pack

Attached inputs

0 sources

No sources added yet. You can still generate from the brief alone, but the output will be less grounded.

Step 3

Safety and runtime rules

Required binaries or software MCP / external tools

Credential handling rules

Do not enter secret values. Public skills should describe approval and credential handling rules, not contain credentials.

Execution choices

These become safety and execution guardrails in the generated instructions.

Include scripts/ stubs when helpful Allow implicit Codex invocation Add OpenClaw gating guidance Network access required at runtime

Safety constraints OpenClaw gating / platform notes

Generation brief

What the model will receive

Structured and reviewable

This preserves raw source material, distills it into agent-readable knowledge files, then generates the final skill bundle and ZIP.

Step 4

Building the bundle

Structuring the brief, source pack, and runtime constraints.

Brief Queued

Normalizing your inputs, sources, and platform targets.

Distill Queued

Turning raw source material into structured, agent-readable knowledge files.

Generate Queued

Drafting SKILL.md, scripts, tests, and final bundle files from the knowledge layer.

Package Queued

Checking coverage and preparing the final downloadable bundle.

Step 5

Your bundle is ready

Review the knowledge layer, generated files, download the ZIP, or submit the bundle for review in the skills database.

Bundle contents 0 files

No folders yet

Knowledge layer No knowledge files

Distilled knowledge files appear here when the bundle can build a usable offline reference layer from the supplied sources.

Platform coverage Codex / Claude

Optional add-ons appear only when relevant.

skill-slug Platforms

Generated skill

SKILL.md Basics

Looking for a SKILL.md generator or wondering how to make a skill file?

A `SKILL.md` file is the instruction manifest at the root of an AI agent skill folder. A usable bundle usually also includes optional `references/`, optional `scripts/`, and platform metadata. This tool creates the whole package, not just the top file.

What is a SKILL.md file?

It is the main manifest and instruction file that helps an AI agent decide when to use a skill and what workflow to follow once the skill is active.

How do you make a skill file?

Define the mission, trigger phrases, non-goals, workflow, validation gates, and safety rules, then package them in a skill folder the agent can load progressively.

What does this generator output?

You get a `SKILL.md` file, a folder tree, optional references, optional script stubs, optional `agents/openai.yaml`, test prompts, and a ZIP bundle.

Built For Real Skills

Most agents expect a skill folder, not a single pasted prompt.

Skill Generator follows the common skill pattern used across modern agent systems: concise `SKILL.md`, progressive disclosure, optional references and scripts, and platform add-ons only when they are genuinely useful.

Capture routing and non-goals

Use the walkthrough to define trigger phrases, do-not-trigger cases, expected outputs, and validation steps instead of leaving the activation logic vague.

Ground it in source material

Fetch a URL, upload a document, paste SOPs, or research official documentation so the generated skill reflects actual source material and platform rules.

Keep public bundles safe

Public skills should describe credential handling and approval rules, not secret values. The bundle should be useful offline and should not depend on re-searching the web for facts you already supplied.