Sign inGet started
Skills

Built-in skills

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

The built-in analytics skills every nextanalytica project starts with: what each one does, the schedule it gets when added and what it needs.

Updated

Every project starts with these skills, and they're the quickest way to see what a skill is for. Add the ones you want in Skills > Add more; each person adds their own, with their own schedule.

SkillWhat it doesSchedule when addedNeeds
Weekly check-upWhat changed on the site this week and why, in five lines.Mondays, 09:00The tag
Wasted ad spendFinds campaigns and keywords that pay for visits that never convert.Every day, 06:00an ad account
Landing page fixesSpots pages people leave and writes the exact text change.Every day, 06:00The tag
Form drop-offFinds the field where people give up on a form.Every day, 06:00The tag
Traffic drop detectiveWhen visits fall, finds the channel, page or campaign behind it.When you askThe tag
Search titlesRewrites titles for queries you almost rank for.Mondays, 07:00Search Console
Build my dashboardBuilds the project's basic dashboard as one page, from get_dashboard.When you askThe tag

Change a schedule on the skill's page in Skills, or ask your agent to run one now: "Run my weekly check-up".

What else could a skill do?

A skill can do more than these. Write one with Write a skill: a name, when to use it and the instructions. Ideas that use data you already have:

SkillWhat it would do
Pricing page watchEvery Monday, compare visits to /pricing with trial starts, by channel, and flag a drop.
AI traffic reportWeekly visits from ChatGPT, Perplexity and Claude, and the pages they land on.
Campaign checkAfter a launch, compare the campaign's visitors and conversions with the week before.
Slow pagesPages whose mobile LCP got worse this week, with the numbers.
Lead qualityLeads by source in Odoo against sign-ups by channel on the site.

Next step

What's in a skill

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.
  • What's in a skill: A skill's parts: a name, when to use it and the instructions, as one SKILL.md you can write yourself.
  • 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?