The AARRR Pirate Metrics Coach skill for Claude
You give Claude your product and your figures, and you get your customer journey back as a funnel of five stages: Acquisition, Activation, Retention, Referral, Revenue. With exactly one KPI per stage that measures a customer action, one stage flagged as the biggest leak, two worked out actions on that leak, and a re-measurement agreement. Any figure you do not supply gets marked [ESTIMATE] instead of being quietly filled in. That way you steer on data rather than gut feeling.
the lines above come from the zip on this page · SKILL.md is 8,960 bytes
Figures in, leak out
reg. P.001This is the worked example that sits in the SKILL.md itself, shortened here. All the figures are fictional, and the file states that explicitly itself: the example shows the format, not a measurement. Watch what happens at Activation. The user measures accounts, and the skill rejects that exact KPI before it calculates any further.
What the AARRR Pirate Metrics Coach is
The AARRR Pirate Metrics Coach is a free skill from our own skill library. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed way of working for one task. Not software you install, no connection to your analytics, no subscription: a single text file of 1,284 words that tells Claude how to lay out your customer journey in five stages, which KPI counts per stage, how it finds the biggest leak, and what it may never fill in itself. What a skill actually is and why files like this work, you can read in what Claude skills are NL.
The problem this skill solves is one anyone selling through a site or app will recognise. Traffic comes in, all sorts of things happen, and yet it does not grow. The reflex is almost always the same: buy more visitors. But a funnel that leaks at the bottom does not get better from more volume going in. What it enforces is the other order: map the whole journey first, then flag the biggest leak, only then act. And because every stage gets exactly one KPI that measures a customer action, your team suddenly talks about the same five figures instead of separate dashboards.
It is written for business owners, marketers and product teams: webshops, SaaS, apps and local services, as the file states literally. It is part of the skill library of 100 free skills NL we make available through the AI and automation service, with no account and no sales email afterwards.
One thing you need to know upfront: the skill does not measure anything itself. It needs your figures, or your honest estimates, and that second category stays marked as [ESTIMATE] throughout the whole analysis. That is not a limitation but the whole point: a growth analysis that leans on invented benchmarks is worse than no analysis at all.
Why steering on growth usually goes wrong
Anyone who wants to improve their growth usually looks at the figures that are easiest to find. And those are almost always the wrong ones. The skill's refusals list reads like a list of what actually goes wrong in practice, so let us name that practice first.
Steering happens on vanity metrics. Page views, followers, likes: figures that feel good but do not measure a customer action. A dashboard full of records while revenue stands still. The skill rejects figures like that as a KPI, with a fixed test: does this measure something a customer does, or something we like to see?
The funnel stops at the deal. A classic sales funnel ends where the customer pays. But it is precisely after that where growth becomes cheap or expensive: do customers come back, do they bring others, do they buy again? Anyone not measuring Retention and Referral pays for every customer again through advertising.
Everything gets tackled at once. After a disappointing quarter, an action list sweeps through: new campaign, new onboarding, new pricing plan, all in the same month. If things improve afterwards, nobody knows why. One leak gets flagged and the rest is deliberately put on hold. That feels strict, and it is the only way to know afterwards whether anything actually helped.
Estimates become facts. Someone says in a meeting that conversion is around two per cent, and three weeks later that figure sits in a quarterly plan as a measurement. Every figure you do not supply yourself gets the label [ESTIMATE], and that label stays put through the entire analysis.
Activation gets confused with registration. The subtlest mistake, and exactly the mistake from the example in the file: creating an account is an administrative action, not a success experience. Anyone measuring activation on accounts is blind to the moment the customer genuinely decides whether this product is for them.
In diff form: what gets thrown out of an average growth dashboard, and what the five stages hand back instead.
Five stages, one leak
reg. P.002The funnel from the FIG.01 example, stage by stage. Each stage answers one question about your customer journey, and the bars show why you always read a funnel from top to bottom: every figure is a percentage of what was left above it. The amber row is the stage the skill flags as the biggest leak in this example.
What is actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The file opens with a frontmatter that determines when Claude picks up the skill: for words like funnel, conversion, retention, churn, growth hacking, North Star and KPI, but also for ordinary frustrations like where is my funnel leaking, why do not customers stick around and which KPI should I measure. There are also English triggers in it, from activation rate to referral loop, so the skill also kicks in when your conversation runs half in English.
Then comes the core: a fixed method of six steps. One: map the product and revenue model, and immediately choose the analysis order, AARRR or the retention-first variant RARRA, with the choice explicitly named. Two: define exactly one KPI per stage that measures a customer action, with a fixed measurement point, and reject vanity metrics. Three: fill the funnel with real figures over a fixed period, with every estimated figure getting the label [ESTIMATE].
Four: find the biggest leak, exactly one stage, with the explanation of why that particular stage costs the most. Five: two actions per stage, of which only the one on the leak is fully worked out with what, why and how you measure the effect. Six: plan the re-measurement, in four to six weeks, with the same definitions and the same period length.
The file also prescribes a fixed answer format, with the blocks PRODUCT, FUNNEL, BIGGEST LEAK, DIAGNOSIS, ACTIONS and RE-MEASUREMENT. That format is the reason you can compare analyses across weeks: the re-measurement in week six has exactly the same shape as today's baseline, so any difference you see is a difference in your figures and not in the shape of the answer.
The file also contains the worked example you saw in FIG.01, with the explicit note that all figures are fictional, and a list of six things the skill never does. Those refusals get their own section below, because they matter at least as much as the method itself. The file closes with four source references: Dave McClure's original presentation and three articles that explain the framework and the RARRA variant.
Want to learn to build an instruction file like this yourself? The full structure of a good SKILL.md sits in writing a SKILL.md NL. This skill is a compact example of that: frontmatter with triggers, a numbered method, a fixed output format, an example and a refusals list.
The theory the skill rests on
AARRR comes from Dave McClure. He presented the framework in August 2007 at Ignite in Seattle under the name Startup Metrics for Pirates and published it that September on his own blog, Master of 500 Hats (the original post). The story is often linked to his work at investment fund 500 Startups, but he did not found that fund until 2010.
The pirates sit in the acronym: say AARRR out loud and you sound like a pirate. Behind the joke sits a serious point. McClure saw startups steering on figures that impress investors but say nothing about the health of the business. His answer: five stages that together describe a customer's entire life cycle, each with a metric that measures a behaviour rather than a feeling.
RARRA comes from Thomas Petit and Gabor Papp. In 2017 they described the same five stages in a different order, with Retention first. Their argument: for products that run on recurring use, such as apps and subscriptions, acquisition is pointless as long as users do not stay. Every new user who leaves after a week is marketing money evaporating. The skill knows both orders, and it explicitly names which one it chooses and why, which is step one of the method.
The one-leak rule is classic bottleneck logic. A funnel is a chain, and a chain gets stronger at its weakest link, not its strongest. Work on Referral while Activation leaks, and you have satisfied customers inviting others to an experience that loses new users straight away. Hence the fixed order: leak first, then re-measure, only then the next stage. Anyone who likes that principle will find the broader version in the Pareto Analyst skill: finding the small cause that carries the largest share of the effect.
The stages connect to other frameworks in the library. Retention is at its core habit formation, and that is what the Hook Model Builder skill is about: the loop of trigger, action, reward and investment that brings users back. And anyone still shaping their entire revenue model can put the funnel next to the canvas from the Lean Canvas Strategist skill, where the same metrics have their own box.
Even without installing the skill, you can sharpen your own growth question with the framework: draw the five stages, put the most honest figure you have against each stage, and look at where the drop-off is biggest. That exercise alone often already exposes that you have been pushing in the wrong place.
What the skill refuses
reg. P.003The SKILL.md contains a list of six things the skill never does. For a growth analysis that list is not a side note: every invented figure in a funnel propagates into every decision that follows it. In conversation the rules play out like this: every line is a request you might make, with the response the skill gives according to its own instructions.
Installing in Claude Code, Claude.ai or Codex
The zip contains one folder, ai-aarrr-pirate-metrics-coach, with the SKILL.md inside. Installing is a matter of putting the file in the right place, and that place differs per environment. SKILL.md has been an open standard since December 2025, so the same skill also works in Codex, Cursor and Gemini CLI. So you are not downloading a Claude file but a working instruction any modern AI assistant can read.
- Unpack the zip into
~/.claude/skills/(or.claude/skills/in your project). - Claude then recognises the skill on its own as soon as you start talking about your funnel or growth.
- You can also call it directly, with
/ai-aarrr-pirate-metrics-coach.
- Go to Customize and then Skills.
- Upload the zip there as a skill.
- Or paste the contents of SKILL.md into the project instructions of a Project.
- Open
AGENTS.mdin your repo. - Paste the contents of SKILL.md into it, or put SKILL.md next to it as a separate file and refer to it from
AGENTS.md. - Codex reads that along at every session.
After that, using it is simple: describe your product and give the most honest figure you have per stage. It asks itself what is missing and neatly flags what is estimated. If you get stuck anywhere while installing, every environment is explained step by step in installing Claude skills NL.
When you do and do not use it
It is at its strongest for businesses with a digital customer journey in which customers can come back: webshops, SaaS, apps, membership models and services with repeat orders. There all five stages carry meaning and the analysis gives the most direction. For products that run on recurring use, the skill chooses the RARRA order and starts at Retention, because new intake is pointless there as long as existing users leave.
There are also situations where you are better off leaving it be, or using it with adjusted expectations. If you sell one-off projects with no repeat character, Retention and Referral structurally say little and you effectively end up with a classic funnel: the skill still works, but the distinguishing part of the framework stays unused. If you have no product and no figures yet at all, do not start at the measurement but at the model: the Lean Canvas comes before the funnel. And do not mistake the skill for an analytics connection: it does not read anything out automatically, you supply the figures and it watches whether they are honestly labelled.
The most important limit is the same as with any measurement framework: the analysis is only as good as the discipline behind it. Anyone who has the leak flagged but skips the re-measurement has a nice diagnosis and no proof at all that the treatment works. That is why it plans the re-measurement in by default, with the same definitions and the same period length as the first time. The one thing it cannot do is carry it out for you.
Run it yourself or have it run
reg. P.004This skill is the free do it yourself version of work we also deliver as a service. It stays complete and without any catches, but be clear about what a skill is: it teaches your AI how to do something, while every new session starts empty. It is not the engine and not the memory. You prompt, you supply your figures again every month, you watch that the re-measurement actually happens. Anyone who wants that differently has two next steps: hand over the engine, or sort out the memory.
where you are now The skill: you are the engine You run the AARRR Pirate Metrics Coach yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep it entirely in your own hands: no trial period, no locked off parts. The limit is your own discipline: the funnel only gets calculated when you supply your figures, and the re-measurement only happens if you remember it.
prepared for you The AI employee: it is ready without you prompting Exactly this work, but as a service: the Reporting Employee prepares your weekly and monthly reports, funnel figures included, without you having to sit behind Claude for it. Control stays with you, because output remains a draft until a human approves it. We deliver this through Mansotti, the company TheSEO is the trading name of, which alongside the Reporting Employee also builds a Quotes Employee and a Sales Employee. Read what an AI employee is and does.
everything from one source Jarvis: all your AIs work from the same company knowledge The skill teaches the AI; the brain is where the memory lives. Want all your AIs to work from the same company knowledge? That is Jarvis, the organisation brain. It connects ChatGPT, Claude, Codex and your people to the same projects, core knowledge and decisions, so your next AI session does not start from scratch. For this skill that means: your KPI definitions, your previous measurements and the agreement on what Activation actually is are simply still there in the next session. What that delivers in practice, from the plans to your first week, you can read at Jarvis itself.
What Jarvis delivers in practice
reg. P.005Step 3 deserves more than a paragraph, because with funnel analysis memory is half the work. A re-measurement is only a re-measurement if the definitions stay the same, and those definitions are exactly what you lose in separate chat sessions. Jarvis is the organisation brain: it remembers what your AIs need to know, divides up the work and keeps track of what happened. You notice it first at the start of a new measurement session.
We have been running on this system ourselves for months. Every agent session, every task and every decision gets logged in it and can be read back. So a new session does not start blank: it first retrieves the logged decisions, the running projects and the latest changes, and carries on from where the previous one stopped. So we are not describing a promise but the way of working we ourselves work in every day.
See the four plans at jarvis/pricing NL. Through the waiting list NL you only pass on your preferred plan with no obligation. That does not yet create an account, an order or a payment obligation. Business arrangements we discuss first.
The skills around it
reg. P.006A funnel analysis never stands on its own: the leak is found, and then the real work starts. These skills from the same library each take on a different piece of that chain, exactly as the library's relationship map connects them.
Once the leak is found
the growth skillsAARRR flags the stage. These two help you actually fix the stage after that.
Hook Model BuilderBuilds the usage loop of trigger, action, reward and investment that makes Retention structural.SKILL RICE PrioritisationPuts your growth actions in order of reach, impact, confidence and effort, so you do not choose on gut feeling.SKILLChoosing what comes first
the leverageOne leak at a time, says the skill. These two help you back up that choice.
MoSCoW Prioritisation CoachSplits your action list into must, should, could and won't, so the leak genuinely gets priority.SKILL Pareto AnalystLooks for the twenty per cent of causes behind eighty per cent of the effect: the same leverage logic as the one-leak rule.SKILLUnderstand first, then turn the wheel
the basicsNew to skills? These three articles lay the foundation under everything on this page.
What Claude skills areWhat a SKILL.md is, why it works and what it gets you.BLOG NL Installing Claude skillsStep by step installation in every environment, with screenshots.BLOG NL Writing a SKILL.md yourselfThe structure of a good instruction file, using this library as the example.BLOG NLLooking further
the contextWhere this skill comes from and what else is out there.
The whole skill libraryAll 100 free skills in one list, sorted by subject.HUB NL Lean Canvas StrategistYour revenue model on one page, with the same metrics as this funnel.SKILL AI and automationThe service behind it: from separate skills to automation that works in your business.SRV Knowledge baseArticles about SEO, AI and online visibility, searchable.DOCFrequently asked questions
What does the AARRR Pirate Metrics Coach skill cost?
Nothing. The skill is free, falls under the MIT licence, and you do not have to create an account or leave an email address. You download a 4.0 KB zip containing a folder and a single file, SKILL.md, and that is the complete skill. There is no paid version and no sales email follows.
Does this skill also work in Codex, Cursor or Gemini CLI?
Yes. SKILL.md has been an open standard since December 2025, so the same file also works in Codex, Cursor, Gemini CLI and other tools that follow the standard. In Codex you unpack the zip into .agents/skills/ in your project, or into ~/.agents/skills/ for all your projects; Codex has supported SKILL.md directly since the open standard of December 2025. Putting the contents of SKILL.md into your AGENTS.md still works too. The instructions are plain readable text, so any AI assistant that accepts instruction files can work with it.
Do I already need measurement data to start?
No, but the skill is honest about it. For every stage it asks for the real figure over a fixed period. If you do not have a figure, it asks whether you want to estimate and marks that figure as [ESTIMATE]. An estimate never gets presented as a measurement, not even silently. So even with half the data you already get direction, without fooling yourself.
What is the difference from an ordinary sales funnel?
A sales funnel stops at the deal. AARRR also measures what happens after the deal: do customers come back (Retention), do they bring others (Referral) and what do they yield over their whole lifetime (Revenue). It is precisely in those last stages that most businesses have their unused share of growth, and that is exactly where a classic funnel does not look.
What is RARRA and when does the skill choose it?
RARRA is the variant Thomas Petit and Gabor Papp described in 2017: the same five stages, but with Retention first. The skill considers that order for products that mainly run on recurring use, such as apps, subscriptions and membership models. Attracting new visitors there has little point as long as existing users do not come back. The skill always explicitly names which order it chooses and why.
Does the skill optimise all five stages at once?
No, and that is a deliberate rule in the file. The skill flags exactly one stage as the biggest leak and fully works out two actions for it. The other stages get their actions in one line, as a backlog for later. Anyone pulling on everything at once improves nothing measurably. After four to six weeks the re-measurement follows and you see whether the leak has shrunk.
Does the skill invent benchmarks or growth figures?
No. The list of refusals in the file is clear about it: no benchmarks or industry averages without a source, no estimates presented as measurements and no guarantees about growth or outcomes. The framework points at the leak; execution determines the result. Even the example in the file itself is explicitly labelled as fictional.
Get found first, then the funnel
The whole funnel starts at Acquisition: people need to find you first. If your funnel already leaks there, that is where the real work for this analysis sits: becoming visible to the people looking for you, in Google and in AI answers. The free SEO scan shows in a few seconds where your site stands. And if you want to talk further about what else AI can do for your growth, from separate skills to full automation, we simply do that in a conversation.