Sign inGet started
Skills

What's in a skill

View as MarkdownOpen in ChatGPTOpen in Claude
Connect your agent
Add to CursorAdd to VS Code

A skill's parts: a name, when to use it and the instructions, as one SKILL.md you can write yourself.

Updated

A skill is one SKILL.md: a name, a line on when to use it and the instructions. That's all of it. Our built-in skills and your own are the same thing.

SKILL.md
---
name: Pricing page watch
description: Every Monday, says whether visits to /pricing turned into trials, by channel.
---
Compare last week's visits to /pricing with trial starts, by channel, against the week before.
Name the channel that changed most, with the numbers.
If nothing moved more than 10%, report nothing.

What are the parts and their limits?

PartLimitTips
Name64 charactersWhat it does, in a few words.
Description300 charactersWhen to use it. Your agent reads it to pick the skill.
Instructions20,000 charactersWhat to read, what counts as worth reporting and how to say it.

What makes instructions good?

  • Name the metric, the period and the comparison: "last 7 closed days against the 7 before".
  • Say when to stay quiet: "If nothing moved more than 10%, report nothing." If you add one line, add this one.
  • Ask for the fix, with where and what: "the exact text now and the text to use".
  • Never ask a skill to change the site; it can't, and runs never do.

Make one

In Skills, click Write a skill, or ask your agent: "Write a skill that checks /pricing every Monday." Give it a schedule on its page, then test it: "Run my pricing page watch now."

Next step

Insights

Related
  • How a run works: A scheduled run, step by step: it starts, reads context and numbers, reports a finding or stays quiet and finishes.
  • Anatomy of a finding: One finding from start to fix, told as a story: our rule notices wasted ad spend, a skill runs and explains it, and a person decides what to change.
  • Project knowledge: The team's instructions, goals and memory your agent reads before every answer and every run, who writes them, the limits and how agents add to them.
  • Steer skills: Shape what skills look at and how they report, with team instructions, a skill's own text and feedback.
  • Built-in skills: The built-in analytics skills every nextanalytica project starts with: what each one does, the schedule it gets when added and what it needs.
  • Insights: Signals from our rules and findings from your skills, newest first, with the numbers that prove them.
Still have questions?
Was this page useful?