Free to read · no account needed

10 min · skills

What is a “skill”? (beginner explanation)

Goal: Explain a skill with one narrow job (messy notes → weekly update): fixed I/O plus a human gate—not “do my job.”

Best for: You keep pasting the same long instructions every week.

A skill is a reusable instruction pack you can name, test, and version—not a vague “be helpful” vibe. Start here before you build a library.

Why beginners skip this

Calling a skill a “universal macro” feels explanatory—boundaries and fixtures get skipped. Say the one job first.

Step 1 — One sentence definition

A skill is a small playbook: written steps, examples, and rules for one recurring job (e.g. “turn meeting notes into decisions”). The AI loads that playbook when the job matches — so you do not retype the playbook every time.

Many products store a skill as a folder with a file often named SKILL.md. You do not need to memorize the file format on day one — start with the idea.

Step 2 — Skill vs prompt vs Project (no slang)

Use this table to place each thing; do not shove checklists into “help me work.”

ThingUse it when…Lives where?
One promptSingle ask, maybe never againInside today’s chat
SkillSame process every weekReusable library you (or your team) install
ProjectSame files + ongoing contextA workspace with documents

Step 3 — Spot a good first skill topic

  • You did it at least three times in two weeks.
  • The steps are stable (same checklist), only the input changes.
  • Mistakes are annoying but not catastrophic if the AI slips — you still review.
Example

Filled prompt

Candidate skill: “Weekly status from bullet dump”
Input: messy bullets from Slack
Output: 5 wins / 5 risks / 3 asks for leadership
Human check: I delete anything I cannot defend in the meeting

What good output looks like

  • Skill purpose is one job for “What is a “skill”?” — not a company brain
  • Done + golden example present and tested
  • Never-send / never-delete honored
  • Pass/fail: fail-case run once (skills-what-is-a-skill #1)

Step 4 — What you will click later (preview)

Exact menus move. Look for words like Skills, Customize, Plugins, or Create. On Claude and ChatGPT, skills may sit under customize / settings / plugin directory. If you cannot find it yet, keep your playbook in a Project instruction — same habit, simpler surface.

Example

Filled prompt

Jobs: (1) apology email (2) status polish (3) one-off brainstorm.
Mark which deserve a skill vs one-off prompt. One-sentence purpose for the top skill only.

What good output looks like

  • Matches the named files/tools/constraints in the fill
  • Refuses invented facts or silent send/delete
  • Pass/fail check you can mark in one minute
  • Stops before irreversible steps without approval

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

Write one line: next time I wave “universal macro” as the explanation, I refuse to start.

Check the unknown path

What should the model do when a field is missing—null, TBD, or ask you? Write it once in Boundaries.

Example

Filled prompt

Jobs this week: (1) apology emails (2) one-off brainstorm (3) status polish twice.
Mark skill vs one-off. One-sentence purpose for the top skill only.

What good output looks like

  • Done + golden example present and tested
  • Never-send / never-delete honored
  • Pass/fail: fail-case run once (skills-what-is-a-skill #2)
  • Skill purpose is one job for “What is a “skill”?” — not a company brain

Red flag

Calling everything a skill; cannot state purpose in one sentence—split before you build.

Save this card

Card: reusable job hat · purpose sentence · split if purpose blurs. Not the company brain.

Before you start

Open the skill card (or blank one-pager). Purpose must be one job for “Understand a skill as a reusable how-to the AI.” Golden example slot cannot stay empty. Guide: skills-what-is-a-skill. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week explain one real skill to a teammate in three plain sentences: what it does, what it must not, how you test it.

Pitfalls

PitfallFix
Calling every prompt a skillSkill = reusable pack with name/tests
One mega-skill for all jobsOne job per skill
No version or changelogname-vN + one line
Example

Filled prompt

Temptation: skip the habit for skills-what-is-a-skill to save five minutes.
Job still: Understand a skill as a reusable how-to the
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to skills-what-is-a-skill)
  • Still delivers checkable output for “What is a “skill”?”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (skills-what-is-a-skill #4)

Practice now

Trigger test: say the trigger to a teammate; they must know when it fires (Asia/Shanghai).

Non-skill: write one thing that should NOT be a skill (Asia/Shanghai).

Skill-defn drill: one skill = trigger + instructions + boundaries—write all three (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight explain one real skill to a teammate in three plain sentences: what triggers it, what it does, what it must never do.

Close the loop: date one refuse-line (Asia/Shanghai) after your first live pass today.

Buffer line: name the artifact path you used (Asia/Shanghai).

One sentence takeaway

Three plain sentences: does / must not / how you test.

Next

First skill · Compare

← Back to home · Learn · Tools · Compare · Start