Free skill

Turn a process into a skill.

Use your process notes to write instructions an AI agent can follow, with the steps, examples and checks the job needs.

Free. No email needed. Updated 12 October 2026.

Start with your process notes.

Download the file, or copy the instructions below into the AI tool you use. Add your process notes and ask it to turn them into a skill. Start with an example you can share.

A skill teaches the steps. It doesn’t connect your tools or run on a schedule. Check the result with the person who knows the job before using it on real work.

Read the skill file

---
name: process-to-skill
description: Turn a documented business process, rough notes or a walkthrough into a reusable SKILL.md file. Use when someone wants to teach an AI agent how their team does a repeated job.
---

# Turn a process into a skill

Use the user's process to write a skill for one named job. Create instructions for the job; do not carry out the job or connect any tools unless the user also asks for that.

## Find the missing rules

Read the supplied notes and examples first. Identify the trigger, inputs, expected output, decisions, exceptions and approval points. Ask only about missing details that would change the result. If those details are unavailable, name them as open questions instead of inventing business rules.

Keep facts separate from examples. Do not turn a one-off exception into a permanent rule. Preserve the user's chosen tools, format and scope.

## Write the file

Return a SKILL.md file with YAML frontmatter:

- `name`: a short name using lowercase letters, digits and hyphens.
- `description`: what the skill does and when an agent should use it.

In the body, include the instructions needed to do this particular job:

- Where inputs come from and what a finished result looks like.
- The steps and decisions that change the outcome.
- Which source controls prices, policies, dates or other facts.
- What to do when information is missing or sources disagree.
- What the agent may draft and what needs a person's approval.
- Checks that show whether the result is ready.

Keep the file short enough to review. Reference supporting files only if they exist or the user has agreed to create them. Never include passwords, tokens or private customer records. A skill describes the job; it does not grant tool access or permission to send, publish or change records.

## Try it before handing it off

Walk through one representative input supplied by the user and one relevant exception, such as a missing price or an unclear request. Compare the outputs with the user's expected result. Label any example you make up as an example. Report which checks you actually ran and which still need the user's review; do not claim that a written walkthrough proves the job works in their tools.

Example: drafting an enquiry reply.

This is a worked example, not a client result. Give the skill notes like these:

Read the enquiry and draft a short reply. Use our current service list. Ask about anything the sender hasn’t explained. Don’t quote prices or promise dates. Leave refunds and complaints for me. I review and send every reply.

The resulting skill should tell the agent to:

Read the enquiry and the supplied service list. Ask for the list if it’s missing.
Draft a short reply that addresses the request. Flag missing details.
Leave prices and delivery dates for the owner to confirm.
Flag refunds and complaints for the owner. Don’t draft a commitment.
Return the draft and any open questions. Wait for the owner to send it.

Check where it stops.

Try a normal enquiry, then a refund request. The first should produce a draft. The second should ask for the owner’s judgment. If it invents a price, a deadline or a policy, fix the instructions and try again.

Want us to set this up?

Tell us about the job and the tools you use. We’ll reply with what we’d build.

Tell us about the work