Tutti Agent Workspace App
tutti-os/tutti
Build or evolve a complex agent-enabled Tutti workspace app repository.
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.
$ npx skills add databuddy-analytics/Databuddy --skill databuddy-mcp -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy-mcp --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/.agents/skills/databuddy-mcp .claude/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .claude/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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/.agents/skills/databuddy-mcpType 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-mcp -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy-mcp --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/.agents/skills/databuddy-mcp .agents/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .agents/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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-mcp -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy-mcp --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/.agents/skills/databuddy-mcp .cursor/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .cursor/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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 .agents/skills/databuddy-mcp--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-mcp -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install databuddy-analytics/Databuddy databuddy-mcp --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/.agents/skills/databuddy-mcp .gemini/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .gemini/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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 databuddy-mcpInstalls 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-mcp -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/.agents/skills/databuddy-mcp .github/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .github/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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-mcp -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-mcp --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/.agents/skills/databuddy-mcp .opencode/skills/databuddy-mcp && 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-mcp" agent skill from https://github.com/databuddy-analytics/Databuddy/tree/main/.agents/skills/databuddy-mcp into .opencode/skills/databuddy-mcp/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "databuddy-mcp", 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.
databuddy-mcpA 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.
Databuddy MCP is an agent skill from databuddy-analytics/Databuddy. Use whenever the Databuddy MCP server is available and the user wants analytics, errors, vitals, investigations, flags, links, annotations, funnels, or goals queried or changed. Covers getdata, capabilities, getschema, the investigation lifecycle, and workspace mutations. Not for SDK integration help (use databuddy) or monorepo implementation (use databuddy-internal).
Its SKILL.md is about 710 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering MCP servers, Third-party API integration and Monorepo tooling. It works with Model Context Protocol. 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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Databuddy MCP loads about 711 tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 334 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). 334 words, ~711 tokens.
.claude/skills/databuddy-mcp/SKILL.md (or your agent's skills folder).The MCP server's session-start instructions, live tools/list, and databuddy://guide resource are canonical. Do not rely on a static tool catalog.
get_data. Batch 2-10 with queries[].list_investigations, then get_investigation for its evidence and history.reply_to_investigation. It is answered from the case's saved evidence; it does not fetch new data, change actions, or start a new investigation. It posts without a preview.get_investigation; retry with the same replyId, never a new one.get_data.capabilities (catalog) or get_schema (columns).websiteId, websiteName, or websiteDomain; any one works. Short-link tools need one too, to pick the organization. get_investigation, reply_to_investigation, and goal/annotation update and delete do not need a website selector. list_flags, update_flag, and add_users_to_flag act on organization-wide flags when no website is given; create_flag needs a website.preset OR both from+to (YYYY-MM-DD). Defaults to last_30d. Don't pass only one of from/to. Row timestamps are UTC.get_data returns at most 20 rows per query; time series keep the newest rows. Each query type has a fixed breakdown; pick the type that breaks down by the dimension you need. Batch items inherit top-level filters, limit, orderBy, and timeUnit.field is a common dimension, a query-specific field from capabilities with detail='full', or trait:<key> for identified-user traits. Rejected fields return the allowed list; there are no typo suggestions. List values only go with in/not_in.confirmed: false and write with confirmed: true. Each tool needs its scope, from an API key or an OAuth grant; tools outside the grant are missing from tools/list.Fetch databuddy://guide for query conventions and investigation behavior. Use live tool schemas for exact inputs.
© 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
Just SKILL.md in .agents/skills/databuddy-mcp of databuddy-analytics/Databuddy.
Open the folder on GitHubat commit 5f63610
Databuddy MCP 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 MCP this skilldatabuddy-analytics/Databuddy | 1.2k | — | ~711 | Automated safety check: Pass | AGPL-3.0 | |
| Tutti Agent Workspace Apptutti-os/tutti | 3.8k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Vscode MCP Architecturetjx666/vscode-mcp | 106 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Contributingbutterbase-ai/butterbase-skills | 534 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Nx Monorepoaiskillstore/marketplace | 430 | — | ~2k | Automated safety check: Pass | None | |
| ReleaseWebMCP-org/npm-packages | 103 | — | ~1.6k | Automated safety check: Notes | MIT |
tutti-os/tutti
Build or evolve a complex agent-enabled Tutti workspace app repository.
tjx666/vscode-mcp
VSCode MCP Bridge project architecture — current monorepo layout, IPC/EventDispatcher flow, per-workspace socket discovery, MCP/CLI adapters, tool filtering, and VSCode extension services.
butterbase-ai/butterbase-skills
A skill your agent uses when contributing to the Butterbase codebase, adding new MCP tools, creating API routes, writing migrations, or understanding the monorepo architecture
aiskillstore/marketplace
Nx monorepo management skill for AI-native development. An agent skill from aiskillstore/marketplace.
WebMCP-org/npm-packages
Release the @mcp-b monorepo with Changesets and pnpm, using npm trusted publishing in GitHub Actions.
holaboss-ai/holaOS
Builds new holaOS apps with @holaboss/app-builder-sdk, either as integration-only MCP modules or as dashboard apps with a shadcn UI under src/client/.
databuddy-analytics/Databuddy
Integrate Databuddy analytics using the SDK, REST API, or MCP.
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.
Works with
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. Databuddy MCP is an agent skill from databuddy-analytics/Databuddy. Use whenever the Databuddy MCP server is available and the user wants analytics, errors, vitals, investigations, flags, links, annotations, funnels, or goals queried or changed.
Databuddy MCP fits situations like: the Databuddy MCP server is available and the user wants analytics; tasks that involve MCP servers; tasks that involve Third-party API integration.
Run `npx skills add databuddy-analytics/Databuddy --skill databuddy-mcp -a claude-code`. Or copy the skill folder (.agents/skills/databuddy-mcp in databuddy-analytics/Databuddy) into .claude/skills/databuddy-mcp in your project. Claude Code loads it when a task matches its description.
Run `npx skills add databuddy-analytics/Databuddy --skill databuddy-mcp -a codex`. Or copy the skill folder (.agents/skills/databuddy-mcp in databuddy-analytics/Databuddy) into .agents/skills/databuddy-mcp 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-mcp -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-mcp, .gemini/skills/databuddy-mcp, .github/skills/databuddy-mcp and .opencode/skills/databuddy-mcp in your project.
SKILL.md names no scripts, command-line tools or credentials: Databuddy MCP is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. 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 MCP 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 711 tokens (SKILL.md is roughly 2.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Databuddy MCP: Tutti Agent Workspace App (tutti-os/tutti, 3.8k stars), Vscode MCP Architecture (tjx666/vscode-mcp, 106 stars), Contributing (butterbase-ai/butterbase-skills, 534 stars) and Nx Monorepo (aiskillstore/marketplace, 430 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.