Turn your team's how-to doc into an AI skill everyone can use
Quick answer
Add two lines of front matter to the doc, a lowercase name with hyphens and a description of what it does and when to use it, and save it as SKILL.md in a folder with the same name. Rewrite the steps as orders with a result you can check, then upload it to Claude, add it in ChatGPT Business, or serve it from one link.
Free plan: no credit card, 1 published page, 10,000 page views a month, and a small Convika bar at the bottom.
On this page
Your team has a doc called "How we check a page before it goes live" or "Writing the weekly client report". People read it once. Then each of them asks Claude or ChatGPT for the work and gets something that skips half the doc. Make the doc a skill, and the AI follows it every time someone asks for that task.
The vendors' docs quoted here were read on November 4, 2026.
What a skill is
A skill is a folder with a SKILL.md file in it. The file starts with front matter between two --- lines, then the instructions in Markdown. The Agent Skills specification needs two fields:
| Field | Rule (from the specification) | What it does |
|---|---|---|
name | "Max 64 characters. Lowercase letters, numbers, and hyphens only. Must not start or end with a hyphen." | Names the skill; the folder has the same name |
description | "Max 1024 characters. Non-empty. Describes what the skill does and when to use it." | The line the AI reads to decide whether to open the skill |
Claude, ChatGPT, Claude Code, Codex, Cursor, and OpenCode read this format. The AI reads every skill's description first and the rest only when a request matches, so the description decides whether the skill is used at all.
Turn the doc into a skill in 5 steps
1. Cut the doc to one task
One skill, one job. "Our marketing playbook" is 5 skills. "Check a landing page before it goes live" is one.
2. Write the description in the words people ask with
Say what the skill does, then when to use it, using the phrases your team types: "check this page", "is this ready to publish", "review before launch".
3. Rewrite the steps as orders with a result you can check
A doc explains. A skill orders. "We usually make sure the form works" becomes "Find every form. Say where each one sends its entries. If it sends them nowhere, say so first."
4. Add the output and one example
Say what the answer looks like: a list, a table, a draft. Paste one good past result as the example.
5. Save it as SKILL.md in a folder of the same name
page-check/SKILL.md. Zip the folder for Claude.
A worked example: the pre-publish page check
Pages made by an AI often fail at the last step: a form that posts nowhere, a button that links to #, a placeholder video. A team doc on checking them becomes this skill:
---
name: page-check
description: Checks an AI-made landing page before it goes live. Use when someone asks to check, review, or finish a page, or asks whether a page is ready to publish.
---
# Page check before publishing
1. Find every form. Say where each sends its entries. A form with no working destination comes first in the answer.
2. List every button and link with where it goes. Flag `#`, `example.com`, and empty links.
3. List every image, video, and embed. Flag placeholders and stock text such as "Lorem ipsum".
4. Quote every price, date, and claim, and ask the owner to confirm each.
5. Answer with a table: item, problem, fix. Problems that lose a visitor first.
The name, page-check, is 10 characters of lowercase letters and a hyphen, and the description says what it does and when to use it, inside the specification's limits.
Give the skill to your team
| Where your team works | How the skill gets there |
|---|---|
| Claude Free, Pro, Max, Ultra | Each person uploads the ZIP: Customize → Skills, +, + Create skill, Upload a skill. Skills need code execution turned on |
| Claude Team, Enterprise | Upload once, then Share with colleagues or Publish to org |
| ChatGPT | On Business and Enterprise, add it in the Skills tab and Share it. On Plus and Pro, each person adds it in the ChatGPT desktop app, or pastes it into a Project |
| Claude Code, Codex, Cursor, OpenCode | Commit the folder to the repository's .claude/skills/ or .agents/skills/ (which tool reads which) |
| A mix of these | Serve it from one remote MCP server everyone's AI connects to (how) |
If you'd rather not write the front matter by hand, Fluxenic's free Doc to SKILL.md converter, on AI Skill Pod, takes a pasted doc, a name, and a when-to-use line, and gives you the SKILL.md or a ZIP for Claude. Its page says the text never leaves your browser. AI Skill Pod can then share that skill with your whole team, contractors on their own accounts included, from one invite link. Fluxenic is the company that runs Convika.
Check that the skill works
- Ask the way your team asks. Not "use page-check", but "is this page ready to go live?" If the AI doesn't pick the skill, rewrite the description with those words.
- Feed it a known bad case. A page with a broken form should come back with the form first.
- Ask a teammate to try it in their own app and plan.
Frequently asked questions
How do I turn a document into a Claude skill?
Put two lines of front matter on top, name (lowercase, hyphens, up to 64 characters) and description (what it does and when to use it, up to 1,024 characters), and save the file as SKILL.md in a folder with that name. Zip the folder and upload it in Claude under Customize → Skills.
What should the description of a skill say?
What the skill does, then when to use it, in the words people type when they ask for that task. The AI reads the description to decide whether to open the skill, so a vague one means the skill isn't used.
Can ChatGPT use a SKILL.md file?
Yes. OpenAI: "Standalone skills are available in the ChatGPT desktop app, Codex CLI, and IDE extension. Skills bundled in plugins are also available in Chat and Work across ChatGPT on the web, desktop, and mobile." The web Skills tab, where you share a skill, is on Business, Enterprise, Healthcare, and Edu.
How long should a skill be?
As long as one task needs. The AI reads only the name and description until a request matches, then the whole file. Split a doc that covers several jobs into several skills.
Sources
- Agent Skills specification (read November 4, 2026)
- Claude Help Center: Using skills in Claude (upload steps, code execution, sharing; read November 4, 2026)
- OpenAI's docs: Build skills (where skills run; read November 4, 2026)
- OpenAI Help: Skills in ChatGPT (the web Skills tab's plans, as search results showed it, November 4, 2026)
Next step
How to share an HTML file as a link that opens on any phone
Email and Google Drive open HTML on a phone without scripts. Compare 5 hosts (Netlify Drop, Tiiny Host, Pagelive, GitHub Pages, Convika) and follow 4 steps.
Related articles
- Share the same ChatGPT and Claude instructions with your whole team, contractors includedClaude and ChatGPT share skills only inside Team, Business, and Enterprise plans. What works on Pro and personal plans, and how to keep one copy for everyone.
- Use the same AI skill in Claude, ChatGPT, and Cursor (and Claude Code, Codex, OpenCode)One SKILL.md works in every tool that reads the Agent Skills format. Where each tool looks for it, why copies drift, and how one MCP link keeps them the same.
- Make every teammate's AI write in your brand voice, in Claude and ChatGPTFive people asking five AIs for copy get five voices. Write the voice guide from your best copy, make it a skill, and give everyone's AI the same one.
- Give a contractor your team's AI prompts without a Business planA freelancer on their own Claude Pro or ChatGPT account isn't in your Team or Business workspace. 3 ways to hand over your prompts, and to take them back.
- My ChatGPT-made website form doesn't send anything. How do I fix it?The form on a page ChatGPT or Claude made says thanks, but nothing arrives. Find the cause in 2 minutes, then fix it with a form service or on Convika.