Domscribe
patchorbit/domscribe
Work with Domscribe — the pixel-to-code bridge. An agent skill from patchorbit/domscribe.
Integrate Databuddy analytics using the SDK, REST API, or MCP.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/databuddy .claude/skills/databuddy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .claude/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/databuddy .agents/skills/databuddy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .agents/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/databuddy .cursor/skills/databuddy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .cursor/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/databuddy-analytics/Databuddy.git --path .cursor/skills/databuddy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/databuddy .gemini/skills/databuddy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .gemini/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install databuddy-analytics/Databuddy databuddyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/databuddy .github/skills/databuddy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .github/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/databuddy-analytics/Databuddy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/databuddy .opencode/skills/databuddy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "databuddy" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.cursor/skills/databuddy into .opencode/skills/databuddy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
databuddyIntegrate Databuddy analytics using the SDK, REST API, or MCP.
Databuddy is an agent skill from databuddy-analytics/Databuddy. Integrate Databuddy analytics using the SDK, REST API, or MCP. Use when implementing analytics tracking, feature flags, custom events, Web Vitals, error tracking, LLM observability, MCP agents, or querying analytics data programmatically.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/ai-vercel.md`, `references/api.md` and `references/core.md`).
It sits in Backend & APIs, covering Product analytics, REST APIs and Web performance. It works with Model Context Protocol, Next.js, React and Node.js. The repository describes itself as: Open-source product analytics for startups: track visitors, events, funnels, and goals without cookies, and ask Databunny, the built-in AI analyst. Uptime, feature flags, and… The licence is AGPL-3.0.
Read from SKILL.md and the folder at commit 5f63610. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
api.databuddy.ccbasket.databuddy.ccAlso links to:
databuddy.ccFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
DATABUDDY_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Databuddy loads about 2.1k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 62 tokens; SKILL.md has 543 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from databuddy-analytics/Databuddy at commit 5f63610, republished under its AGPL-3.0 licence (© databuddy-analytics). 543 words, ~2,087 tokens.
.claude/skills/databuddy/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.Databuddy is a privacy-first analytics platform. This skill covers both the SDK (@databuddy/sdk) and the REST API.
For the most up-to-date documentation, fetch: https://databuddy.cc/llms.txt
Use this skill when:
| Import Path | Environment | Description |
|---|---|---|
@databuddy/sdk | Browser (Core) | Core tracking utilities and types |
@databuddy/sdk/react | React/Next.js | React component and hooks |
@databuddy/sdk/node | Node.js/Server | Server-side tracking with batching |
@databuddy/sdk/vue | Vue.js | Vue plugin and composables |
@databuddy/sdk/ai/vercel | AI/LLM | Vercel AI SDK middleware for LLM analytics |
import { Databuddy } from "@databuddy/sdk/react";
export default function RootLayout({ children }) {
return (
<html>
<body>
{children}
<Databuddy
clientId={process.env.NEXT_PUBLIC_DATABUDDY_CLIENT_ID}
trackWebVitals
trackErrors
trackPerformance
/>
</body>
</html>
);
}import { Databuddy } from "@databuddy/sdk/node";
const client = new Databuddy({
clientId: process.env.DATABUDDY_CLIENT_ID,
enableBatching: true,
});
await client.track({
name: "api_call",
properties: { endpoint: "/users", method: "GET" },
});
// Important: flush before process exit in serverless
await client.flush();import { FlagsProvider, useFlag, useFeature } from "@databuddy/sdk/react";
// Wrap your app
<FlagsProvider clientId="..." user={{ userId: "123" }}>
<App />
</FlagsProvider>
// In components
function MyComponent() {
const { on, loading } = useFeature("dark-mode");
if (loading) return <Skeleton />;
return on ? <DarkTheme /> : <LightTheme />;
}import { databuddyLLM } from "@databuddy/sdk/ai/vercel";
import { openai } from "@ai-sdk/openai";
const { track } = databuddyLLM({
apiKey: process.env.DATABUDDY_API_KEY,
});
const model = track(openai("gpt-4o"));
// All LLM calls are now automatically tracked| Option | Type | Default | Description |
|---|---|---|---|
clientId | string | Auto-detect | Project client ID |
disabled | boolean | false | Disable all tracking |
trackWebVitals | boolean | false | Track Web Vitals metrics |
trackErrors | boolean | false | Track JavaScript errors |
trackPerformance | boolean | true | Track performance metrics |
enableBatching | boolean | true | Enable event batching |
samplingRate | number | 1.0 | Sampling rate (0.0-1.0) |
skipPatterns | string[] | — | Glob patterns to skip tracking |
<Databuddy
disabled={process.env.NODE_ENV === "development"}
clientId="..."
/><Databuddy
clientId="..."
skipPatterns={["/admin/**", "/internal/**"]}
maskPatterns={["/users/*", "/orders/*"]}
/>// Browser
import { track } from "@databuddy/sdk/react";
track("purchase", {
product_id: "sku-123",
amount: 99.99,
currency: "USD",
});
// Node.js
await client.track({
name: "subscription_renewed",
properties: { plan: "pro", amount: 29.99 },
});// Browser
window.databuddy?.setGlobalProperties({
plan: "enterprise",
abVariant: "checkout-v2",
});
// Node.js
client.setGlobalProperties({
environment: "production",
version: "1.0.0",
});| Service | URL | Purpose |
|---|---|---|
| Analytics API | https://api.databuddy.cc/v1 | Query analytics data |
| Event Tracking | https://basket.databuddy.cc | Send custom events |
Use API key in the x-api-key header:
curl -H "x-api-key: dbdy_your_api_key" \
https://api.databuddy.cc/v1/query/websitesGet API keys from: Dashboard → Organization Settings → API Keys
curl -X POST -H "x-api-key: dbdy_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"parameters": ["summary", "pages"],
"preset": "last_30d"
}' \
"https://api.databuddy.cc/v1/query?website_id=web_123"Available Query Types:
| Type | Description |
|---|---|
summary | Overall website metrics and KPIs |
pages | Page views and performance by URL |
traffic | Traffic sources and referrers |
browser_name | Browser usage breakdown |
device_types | Device category breakdown |
countries | Visitors by country |
errors | JavaScript errors |
performance | Web vitals and load times |
custom_events | Custom event data |
Date Presets: today, yesterday, last_7d, last_30d, last_90d, this_month, last_month
Databuddy exposes an MCP server for AI agents (Claude, Claude Code, Cursor, Windsurf, etc.) to query analytics, read investigations, and manage goals, funnels, annotations, flags, and links. Use for analytics questions, automated reports, or structured data extraction.
Endpoint: POST https://api.databuddy.cc/v1/mcp (local: http://localhost:3001/v1/mcp)
Auth: Claude and Claude Code sign in with a Databuddy account (OAuth), no key needed. Other clients, including Cursor, send an API key via x-api-key or Authorization: Bearer <key>. read:data covers analytics and reads; add manage:websites for goal, funnel, annotation, and investigation-reply writes, manage:flags for flag mutations, and organization-wide read:links (link reads) plus write:links (link mutations) for short links. Tools the key lacks scopes for are hidden from tools/list.
Tools: Use the live tools/list and the databuddy://guide resource; see https://www.databuddy.cc/docs/api/mcp for the full list. Start with list_websites, capabilities, and get_data.
Dates for get_data: a preset such as last_7d, last_30d, last_90d, today, or yesterday, or both from and to. Defaults to last_30d.
Cursor setup (mcp.json): Add a Databuddy MCP entry with the API URL and your API key in the x-api-key header.
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"type": "custom",
"name": "purchase",
"properties": {
"value": 99.99,
"currency": "USD"
}
}' \
"https://basket.databuddy.cc/?client_id=web_123"curl -X POST \
-H "Content-Type: application/json" \
-d '[
{"type": "custom", "name": "event1", "properties": {...}},
{"type": "custom", "name": "event2", "properties": {...}}
]' \
"https://basket.databuddy.cc/batch?client_id=web_123"For detailed documentation, see:
packages/sdk/apps/api/apps/docs/content/docs/api/© databuddy-analytics, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 6 other files (references) in .cursor/skills/databuddy of databuddy-analytics/Databuddy.
Open the folder on GitHubat commit 5f63610
Databuddy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Databuddy this skilldatabuddy-analytics/Databuddy | 1.2k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Domscribepatchorbit/domscribe | 193 | — | ~3.3k | Automated safety check: Notes | MIT | |
| Add React Analyticsgotempsh/temps | 826 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Nextcrmpdovhomilja/nextcrm-app | 712 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Scaffold ProjectMarve10s/Better-Fullstack | 752 | — | ~716 | Automated safety check: Pass | MIT |
patchorbit/domscribe
Work with Domscribe — the pixel-to-code bridge. An agent skill from patchorbit/domscribe.
gotempsh/temps
Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals…
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
pdovhomilja/nextcrm-app
Connect to NextCRM MCP server to manage CRM data — accounts, contacts, leads, opportunities, targets, products, contracts, activities, documents, target lists, enrichment, email accounts, campaigns…
Marve10s/Better-Fullstack
Scaffold a new app, API, backend, fullstack project, mobile app, polyglot service, monorepo, or starter with Better Fullstack.
rtadewald/skills
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples.
databuddy-analytics/Databuddy
Build multi-platform chat bots with Chat SDK (chat npm package).
databuddy-analytics/Databuddy
Help external users integrate Databuddy into their own apps.
databuddy-analytics/Databuddy
Build or review Bun fullstack TypeScript code with Drizzle-backed SQL.
databuddy-analytics/Databuddy
Design, implement, and review software using vertical slices (feature-first architecture) instead of horizontal layers.
databuddy-analytics/Databuddy
Work inside the Databuddy monorepo for internal implementation, debugging, review, and refactoring.
databuddy-analytics/Databuddy
A skill your agent uses whenever the Databuddy MCP server is available and the user wants analytics, errors, vitals, investigations, flags, links, annotations, funnels, or goals queried or changed.
Integrate Databuddy analytics using the SDK, REST API, or MCP. Databuddy is an agent skill from databuddy-analytics/Databuddy. Integrate Databuddy analytics using the SDK, REST API, or MCP.
Databuddy fits situations like: implementing analytics tracking; LLM observability; querying analytics data programmatically.
Run `npx skills add databuddy-analytics/Databuddy --skill databuddy -a claude-code`. Or copy the skill folder (.cursor/skills/databuddy in databuddy-analytics/Databuddy) into .claude/skills/databuddy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add databuddy-analytics/Databuddy --skill databuddy -a codex`. Or copy the skill folder (.cursor/skills/databuddy in databuddy-analytics/Databuddy) into .agents/skills/databuddy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add databuddy-analytics/Databuddy --skill databuddy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/databuddy, .gemini/skills/databuddy, .github/skills/databuddy and .opencode/skills/databuddy in your project.
Going by SKILL.md and its folder, Databuddy needs the command-line tools its instructions call (curl) and credentials named DATABUDDY_API_KEY. Our summary lists: Node.js; A credential in DATABUDDY_API_KEY.
SKILL.md names 3 domains. In commands or code: api.databuddy.cc and basket.databuddy.cc; the agent is likely to contact these when it follows the instructions. As links in the text: databuddy.cc. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Databuddy is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.4k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Databuddy: Domscribe (patchorbit/domscribe, 193 stars), Add React Analytics (gotempsh/temps, 826 stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars) and Nextcrm (pdovhomilja/nextcrm-app, 712 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
databuddy-analytics (a GitHub organization) maintains it in databuddy-analytics/Databuddy, which has 1,177 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 7, 2026.
Source: databuddy-analytics/Databuddy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.