Sign inGet started
Skills

Skills

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

Skills are instructions your agent follows on demand or on a schedule. They tell you what changed and what to fix, and stay quiet otherwise.

Updated

A skill is a short set of instructions your agent follows for one job: "compare this week with last week and name the three biggest changes". Run it when you ask, or put it on a schedule and it writes to you only when it finds something.

It's the question you'd ask every Monday, asked for you, with the numbers attached. If you only read one thing here: a run reads one project and never changes your site, code or tools. A person always makes the change.

How does it work?

  1. Your data: the tag's visits, your sources and your team's project knowledge.
  2. Rules and skills watch it: our rules run on our side without a model; each person's skills run on their own Claude.
  3. A finding reaches you: the numbers and the query that proves them, in your agent and by email. See Findings.
  4. You decide: your agent proposes the change; you approve it in your code, or it acts through a connector your team added.

Words to know

  • Skill: a name, when to use it and the instructions.
  • Run: one time a skill runs on a schedule, from start to finish.
  • Insight: what our rules or your skills found, newest first.
  • Finding: what a skill's run reports to the skill's owner.
  • Project knowledge: the team's instructions and memory your agent reads first.
  • Connector: a tool your team added, such as Linear or HubSpot, that agents can act through.

Set it up

Add a skill in Skills > Add more. To run your skills on a schedule, allow it on your Claude Code once. Run skills on a schedule.

Where do I use it?

  • Your agent: "Run my weekly check-up", "Anything I should know this week?". See Your agent.
  • Email: "Your agent found something on shop.example", when a run finds something.
  • The dashboard: Skills, to add, write and schedule skills.

What are skills good at, and where do they fall short?

Skills are at their best on the steady work nobody makes time for: watching the same thing every day or week, explaining a change with numbers and proposing the exact fix.

They won't change your site on their own (a run never does), answer beyond the data you have or make a decision that's yours to make.

Learn by example

Related
  • Run skills on a schedule: Allow scheduled skills on your Claude Code once: a cloud routine with a token, or a one-line hourly check.
  • Skills security: What a scheduled analytics run can read and do, whose Claude Code runs it, what it can never touch and the limits that keep your website safe.
  • 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.
Still have questions?
Was this page useful?