---
name: skill-creator
description: Your process for building a brand-new skill WITH the owner when they want to save a repeatable workflow, procedure, or capability so you can reuse it later. Load this BEFORE you create a skill — then interview, write it well, and save it with create_skill.
version: 1.0.0
metadata: {"bizer":{"name":"Skill Creator"}}
---

SKILL CREATOR — your process for authoring a NEW skill with the owner and
saving it with the create_skill tool. A skill is a reusable how-to (a name, a
trigger description, and an instruction body) that you load and follow later.
You are the author; the owner is the expert on their business — interview them,
then write the skill in clear language. Don't make them fill out a form.

WHEN TO USE THIS: the owner asks to save/remember a workflow as a skill, or you
notice you've walked them through the same multi-step procedure more than once and
it's worth capturing. Don't invent skills they didn't ask for.

STEP 1 — CAPTURE THE INTENT (interview first; don't assume). In a short back-and-
forth, get clear on:
- WHAT it should do — the job, start to finish.
- WHEN it should kick in — the exact moments, situations, and phrases that should
  trigger it. This is the most important thing to pin down.
- The STEPS the way they actually do it, including edge cases and what 'done right'
  looks like. Ask for a real example if it helps.
Ask only what you genuinely need — a few sharp questions, not an interrogation.

STEP 2 — WRITE THE DESCRIPTION (the trigger). This one line is what makes the
skill fire at the right time later, so make it count:
- Third person, and pack in BOTH what it does AND when to use it.
- Name the concrete triggers. Be a little pushy — a vague description never fires.
- e.g. "Drafts a friendly payment reminder. Use when an invoice is 7+ days overdue
  or the owner asks to chase a customer for payment."

STEP 3 — WRITE THE INSTRUCTIONS (the how-to body, in markdown):
- Lead with a one-line overview, then a 'When to use this' note, then the steps.
- Be specific and concrete — write the steps you'd actually follow.
- Keep it tight (well under ~500 lines). Explain WHY a step matters rather than
  shouting ALWAYS in caps. Push rare, deep detail to the end, not the top
  (progressive disclosure — the short body does the work).

STEP 4 — TOOLS & CODE (only if needed). If the skill needs you to use specific
tools (e.g. gmail_send), name them in `tools` — unknown names are ignored, never
granted. Keep it INSTRUCTIONS-ONLY unless the task needs real computation you've
already proven with run_code; only then bundle a tested Python script.

STEP 5 — SAVE IT with create_skill (name, description, instructions, optional icon
and tools). It's turned on immediately. Then read back what you built in one or two
sentences and offer ONE refinement round — tweak the trigger, tighten a step, add a
tool. Treat the first version as a draft, the way the skill-creator does.

Tip: the owner can also build a skill by hand in the app (Skills → Create your own
skill). If they'd rather author it themselves, point them there; otherwise just
build it with them here.
