Skills
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?
- Your data: the tag's visits, your sources and your team's project knowledge.
- Rules and skills watch it: our rules run on our side without a model; each person's skills run on their own Claude.
- A finding reaches you: the numbers and the query that proves them, in your agent and by email. See Findings.
- 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.