Skip to main content

Skills

A skill is the approach zv1 brings to one tool: when to reach for it, how to use it well, and what a good result looks like. There's one per tool, and they're why zv1 doesn't need to be told how Caliper works every time you ask it something.

Open Skills at chat.zerowidth.ai to see the list, and any skill to read it in full.

Your additions

Under each skill's built-in strategy is a box for your additions — the things that are true about how you work rather than how the tool works. House formats, naming you keep to, the thing you always want mentioned, the thing you never do.

What you write there loads with that skill in every conversation you have with zv1, in any tool. It's the difference between telling zv1 your conventions once and repeating them every session.

Additions are yours alone. A teammate reading the same skill sees their own box, not yours — so one person's shorthand never becomes everyone's.

What to put in one

Write the things a new colleague would need told:

  • "Datasets get named <team>-<surface>-<date>."
  • "We score on a 1–5 scale, never 1–10, even when a rubric offers it."
  • "When you draft a flow, leave the model on whatever's already on the canvas."

Keep it to what you'd actually correct someone for. A long list of preferences is harder for zv1 to honor than a short list of rules that matter.

2 min read