Skip to main content
TinyAnalytics Agent Skills are five open-source instruction packs that teach an AI coding agent to run TinyAnalytics end to end—register, create the site, install the tracking script, prove real data arrives, then instrument events, answer questions from the data, and build goals, funnels, and dashboards. You state the intent; the agent does the analytics work. Install them into your agent with one command:
The skills live in the public tinyanalytics/agent-skills repository and are MIT-licensed.
Agent Skills tell an agent how to work with TinyAnalytics. They are not the same as the TinyAnalytics MCP server, which gives an agent a live connection to your analytics data, or Ask AI, which answers questions inside the dashboard. The comparison below shows which to reach for.

​
What is an Agent Skill?

An Agent Skill is a Markdown file that an AI coding agent loads when a task matches its trigger, giving the agent step-by-step procedure, exact request bodies, and explicit failure handling for that task. TinyAnalytics publishes five, each scoped to one job so an agent loads only what the current task needs.

​
Which skills are included?

Each skill declares when to skip itself, so an agent asked to instrument checkout reaches for tinyanalytics-events rather than re-running setup.

​
How do I install the Agent Skills?

Prerequisites: Node.js (for npx) and an agent that supports skills—Claude Code, Cursor, and Codex all work, along with the other targets the skills CLI supports.
1

Add the skills to your project

Run the install command from your project root:
Keep both non-interactive flags. Without them the CLI opens a picker, which stalls an agent-driven install that has no one to answer it.
2

Ask for what you want

Describe the outcome in your own words and let the matching skill trigger:
Other phrasings that match: “add analytics to my site”, “is tracking working?”, “track signups”, “what were our top pages last week?”, or “build a signup funnel”.
3

Answer the agent's account question

The setup skill asks which email to register with rather than inventing one, and hands you the generated password and login URL afterward. If the response says a verification link was emailed, click it.

​
Verify

Ask your agent to list the skills available in the current project. The installation is complete when all five TinyAnalytics skills appear and a request such as “is tracking working?” selects the verification skill.

​
How does the agent get an API key?

The setup skill works down an access ladder instead of assuming you already have a key:
  1. A key already in your project’s .env or environment — it verifies the key still works and uses it.
  2. No key — a single headless registration call creates the user, organization, site, and API key together, so setup never requires the web UI.
  3. Registration disabled on the instance — the agent asks you to sign up and mint a key yourself from Settings → Account, then paste it in.
The key the agent creates or receives carries its owner’s access, exactly like a key you make by hand.
The skills require the key to go into a gitignored .env and be read back as an environment variable—never into chat output, a commit, a log, or any other file. Review the agent’s diff before committing, as you would for any generated code.

​
How do the skills stay current?

Every skill fetches dash.tinyanalytics.io/setup.md at run time and treats that page as the source of truth for endpoints, request bodies, and response shapes. Where an installed skill disagrees with the fetched page, the fetched page wins—so an old install still calls current endpoints. If the page is unreachable, the skill stops and tells you rather than guessing an endpoint from memory. Documented endpoints are additive-only, and anything scheduled for deprecation is dated in dash.tinyanalytics.io/llms.txt first. To pick up new skills, re-run the install command. The same flow is written for people at dash.tinyanalytics.io/setup.md if you would rather follow it yourself.

​
Do the skills prove tracking actually works?

Yes. The verification skill reports success only on observed data—it polls your site’s overview endpoint until a real pageview appears, and never reports “verified” from the fact that a snippet was added. When the count stays at zero, it works through the served HTML, the site ID, whether the script loaded, your Content Security Policy, and ad blockers, reporting each finding as it goes. You can also verify the installation yourself.

​
Agent Skills, MCP server, or Ask AI?

All four surfaces use AI with TinyAnalytics, and they answer different questions: Agent Skills and the MCP server work well together: the skills supply the procedure, and the MCP server can supply the connection. The setup skill writes its steps as outcomes, so an agent already connected over MCP can reach them with MCP tools instead of raw HTTP calls.

MCP server

Connect an AI agent to your analytics data.

Use docs with AI

Give an assistant these pages as context.

Quickstart

Install TinyAnalytics yourself in a few minutes.

API keys

Understand what a key can reach.

Verify installation

Confirm your first pageview by hand.

Ask AI

Ask questions inside the dashboard.

Related topics

Bot and AI Crawler AnalyticsUse TinyAnalytics Documentation with AI ToolsHow Analytics Bot Detection Works