How to create a skill

Write an agent skill I can publish, packaged as a folder I can zip.

A skill is a procedure another AI agent follows — commands to run, checks to make, and the shape of
the output — not an essay about a topic. Pick one job it does well.

Create this structure:

  <skill-name>/
    SKILL.md              (required)
    references/*.md       (optional: rules, checklists, playbooks it should consult)
    scripts/*             (optional: scripts it can run)
    templates/*           (optional: output templates it can fill in)

SKILL.md must start with YAML frontmatter and nothing above it:

  ---
  name: <kebab-case-name>
  description: One sentence saying what it does AND when the agent should use it.
  license: MIT
  version: 1.0.0
  ---

Then the body, in this order:

  # <Title>

  ## When to use
  The situations that should trigger it, and when NOT to use it.

  ## Procedure
  Numbered, concrete steps. Real commands in code fences. No hand-waving.

  ## Checklist
  - [ ] Verifiable conditions that must hold before it declares success.

  ## Output format
  Exactly what it should produce, with a short example.

Rules — a skill that breaks these gets rejected by the security scan:

1. No piping remote content into a shell (no `curl … | bash`, no `wget … | sh`).
2. No base64-decoded or otherwise encoded commands, and no `eval` of remote content.
3. No reading or transmitting secrets: no .env contents, SSH keys, cloud credentials,
   keychain entries, or browser cookie/credential stores.
4. No literal API keys or tokens anywhere in the files.
5. No instruction to hide, conceal or omit anything from the user, and no attempt to
   override the agent's system instructions or skip confirmation for risky actions.
6. Do not request blanket tool permissions. Never write `allowed-tools: Bash(*)` or
   anything equivalent to bypassing permissions. If a step needs a command, name the
   specific command in the procedure instead.
7. Network calls only to well-known, named hosts, and say why each one is needed.
8. No zero-width or bidirectional-override characters, and no instructions hidden in
   HTML comments.

Write it as original work. Keep SKILL.md focused — a few hundred to a couple of thousand words is
usually right; push detail into references/ rather than padding the main file.

When you are done, tell me the folder path and give me the exact command to zip it.