Agent skill

Tutti Agent Workspace App

by tutti-os in tutti-os/tutti

Build or evolve a complex agent-enabled Tutti workspace app repository.

Apache-2.0Auto-check passedDevelopment

Install Tutti Agent Workspace App

skills CLI
$ npx skills add tutti-os/tutti --skill tutti-agent-workspace-app -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tutti-os/tutti tutti-agent-workspace-app --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tutti-os/tutti.git skills-src && mkdir -p .claude/skills && cp -r skills-src/services/tuttid/service/workspace/agent_workspace_app_reference .claude/skills/tutti-agent-workspace-app && rm -rf skills-src

Use ~/.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/

Facts

Skill name
tutti-agent-workspace-app
GitHub stars
3.8k
Token cost
~1.9k tokens
SKILL.md length
871 words
Files
8 (incl. references)
Skills in repo
8
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build or evolve a complex agent-enabled Tutti workspace app repository.

  • Works in 9 steps: Inspect the existing app shape, scripts,… → Choose the smallest architecture that… → Define shared contracts before wiring… → …
  • Tutti apps with web/server/shared monorepos
  • SKILL.md covers When To Use, Required References, Workflow and Managed and standalone agent…, plus 1 more section
  • Calls pnpm and python3

What it does

Tutti Agent Workspace App is an agent skill from tutti-os/tutti. Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging, i18n harnesses, and production package validation. For simple package creation or repair, use tutti-workspace-app-factory instead.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `agents/openai.yaml`, `references/agent-acp-kit.md` and `references/app-architecture.md`).

It sits in Development, covering Internationalization, MCP servers and Monorepo tooling. It works with Model Context Protocol. The repository describes itself as: Where people and agents build in tune. The licence is Apache-2.0.

When your agent uses it

  • Tutti apps with web/server/shared monorepos
  • @tutti-os/agent-acp-kit local agent runtimes
  • Kit-owned TUTTICLI agent/composer discovery
  • Dynamic agent catalogs

Example prompts

  • “/tutti-agent-workspace-app”

Requirements

  • Python 3

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Inspect the existing app shape, scripts, runtime dependencies, build output, storage, i18n, and agent surfaces.
  2. Choose the smallest architecture that can stay maintainable: do not add local agents, WebSocket, MCP, CLI, or background workers unless…
  3. Define shared contracts before wiring web/server calls. Keep domain DTOs, WebSocket messages, CLI-visible shapes, and runtime profile…
  4. Build the web UI as the primary development surface. Keep the server as local API/static host and app orchestration layer.
  5. If agents are needed, add an exact released @tutti-os/agent-acp-kit, use its default app-owned runtime, call the /tutti auto facade for…
  6. Add package generation only after the local dev app runs. Package the built web assets, bundled server, tutti.app.json, optional…
  7. If the user asks to connect to the Tutti app ecosystem, treat ecosystem integration as required: expose app capabilities through…
  8. For GitHub-hosted app repositories that should publish releases, add staging and production release workflows after the package builder is…
  9. Verify with the repo's targeted checks first, then package checks.

What it can do on your machine

Read from SKILL.md and the folder at commit 207beee. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tutti Agent Workspace App loads about 1.9k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 871 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~12k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from tutti-os/tutti at commit 207beee, republished under its Apache-2.0 licence (© tutti-os). 871 words, ~1,860 tokens.

Download SKILL.mdSave it as .claude/skills/tutti-agent-workspace-app/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
tutti-agent-workspace-app
description
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTI_CLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging, i18n harnesses, and production package validation. For simple package creation or repair, use tutti-workspace-app-factory instead.

Tutti Agent Workspace App

Use this skill when the task is to create or evolve a full Tutti app repository, not just a final package directory. The target app is usually a local-first web app with a server, shared contracts, optional local agent runtime, and an app-owned scripts/package-tutti-app.mjs.

For the final package contract, defer to $tutti-workspace-app-factory and its references. This skill owns app architecture patterns; the factory skill owns tutti.app.json, tutti.cli.json, bootstrap.sh, runtime env, storage, i18n harness, and static package validation rules.

When To Use

Use this skill for:

  • New agent-enabled Tutti app repositories.
  • Existing web/server apps being converted into maintainable Tutti app repos.
  • Apps that need @tutti-os/agent-acp-kit for app-owned local Agent execution and @tutti-os/agent-acp-kit/tutti for auto CLI-backed/standalone platform context.
  • App-specific MCP or command gateways that expose domain tools to local agents.
  • Multi-package pnpm workspaces with apps/web, apps/server, and packages/shared.
  • App-owned packaging, smoke tests, i18n enforcement, and CLI/reference endpoints.
  • GitHub Actions release workflows for publishing Tutti app releases and staging/production catalogs.

Use $tutti-workspace-app-factory instead for a small standalone package, package repair, or manifest-only validation.

Required References

Read only the references needed for the task:

  • references/app-architecture.md for repository layout, web/server/shared boundaries, and dependency choices.
  • references/agent-acp-kit.md when implementing local agent providers, ACP event mapping, or run-scoped MCP tools.
  • references/dynamic-agent-providers.md when implementing agent catalog/composer endpoints, standalone behavior, agent pickers, default selection, or canonical agent-id persistence. Read this before hard-coding any agent or provider list.
  • references/package-builder.md when adding scripts/package-tutti-app.mjs, bootstrap.sh, Tutti CLI output docs, or package validation.
  • references/github-actions-release.md when creating or changing .github/workflows/publish-tutti-app.yml, .github/workflows/publish-tutti-app-staging.yml, release variables, or catalog publishing.
  • references/i18n-and-web-debugging.md when changing UI copy, language handling, web-first debug flow, or smoke/e2e checks.

Also read $tutti-workspace-app-factory before changing final package files or package runtime behavior.

Workflow

  1. Inspect the existing app shape, scripts, runtime dependencies, build output, storage, i18n, and agent surfaces.
  2. Choose the smallest architecture that can stay maintainable: do not add local agents, WebSocket, MCP, CLI, or background workers unless the product needs them.
  3. Define shared contracts before wiring web/server calls. Keep domain DTOs, WebSocket messages, CLI-visible shapes, and runtime profile types in packages/shared.
  4. Build the web UI as the primary development surface. Keep the server as local API/static host and app orchestration layer.
  5. If agents are needed, add an exact released @tutti-os/agent-acp-kit, use its default app-owned runtime, call the /tutti auto facade for catalog/composer/skill context, normalize events, and add a run-scoped tool gateway. Follow references/dynamic-agent-providers.md: do not pass mode, check TUTTI_CLI, call Agent catalog HTTP routes, read app ID/token/API environment, parse CLI JSON, or maintain provider aliases. Render every facade agent, persist exact agent target ids, keep unavailable entries disabled with their reason, and never maintain a fixed provider catalog. For apps that must run both locally and in cloud/managed Tutti, follow references/agent-acp-kit.md exactly: managed credentials come from request headers on the server, never from browser JSB fallback or request body fields.
  6. Add package generation only after the local dev app runs. Package the built web assets, bundled server, tutti.app.json, optional tutti.cli.json, executable bootstrap.sh, assets, locales, and package-local AGENTS.md.
  7. If the user asks to connect to the Tutti app ecosystem, treat ecosystem integration as required: expose app capabilities through tutti.cli.json, make the app callable by other Tutti apps and agents, and use TUTTI_CLI for any calls to other installed Tutti apps.
  8. For GitHub-hosted app repositories that should publish releases, add staging and production release workflows after the package builder is stable.
  9. Verify with the repo's targeted checks first, then package checks.
Show full SKILL.md (294 more words)Show less

Managed and standalone agent checklist

Keep Tutti-hosted and standalone behavior behind the kit's fixed auto facade while sharing the same runtime execution layer:

  1. Pin an exact kit version that exports the auto catalog/composer/skill facade and managed header context helper.
  2. Call loadTuttiAgentCatalog({ runtime }); do not use the deprecated provider-catalog projection, pass mode, or inspect TUTTI_CLI.
  3. Load composer options lazily for one exact agent target id and expose only app/domain DTO projections.
  4. Persist only canonical agent target ids returned by the facade. Migrate legacy provider-only state only when it maps unambiguously to one current agent; never retain provider as selection identity.
  5. Await createManagedAgentRunContextFromHeaders(...) directly. Do not pre-read credentials or pre-check provider support in app code.
  6. Without a managed header, use an app-owned local cwd. Pass the provider derived from the selected agent entry, selected cwd, and optional managedAgentInvocation into runtime execution.
  7. Delete raw Agent HTTP/CLI clients, browser credential fallbacks, request-body credential fields, alias maps, and dependency patch scripts.
  8. Never persist managed credentials or expose managed cwd and credentials through frontend events, logs, status APIs, or stored app state.
  9. Do not hard-code /workspace, .agent-runs, or CODEX_HOME; the kit derives managed context.
  10. If instructions arrive over WebSocket, confirm the host injects the managed credential into that route; do not create a second credential channel.
  11. Package the built server, web assets, MCP/tool entrypoints, and runtime metadata needed by Tutti.
  12. Test CLI-backed auto, standalone auto, configured CLI failure, canonical IDs, managed/local run context, and secret non-leakage.

Validation

Prefer app-local scripts when they exist:

bash
pnpm check
pnpm test
pnpm typecheck
pnpm check:i18n
pnpm package:tutti

For final package validation, run the validator from $tutti-workspace-app-factory when available:

bash
python3 <factory-skill>/scripts/validate_tutti_app_package.py <generated-package-root>

If the app includes real local agent execution, add or run a smoke check that starts with provider detection before launching a real turn.

© tutti-os, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in services/tuttid/service/workspace/agent_workspace_app_reference of tutti-os/tutti.

  • SKILL.md
  • agents/openai.yaml
  • references/agent-acp-kit.md
  • references/app-architecture.md
  • references/dynamic-agent-providers.md
  • references/github-actions-release.md
  • references/i18n-and-web-debugging.md
  • references/package-builder.md

Open the folder on GitHubat commit 207beee

Compare with similar skills

Tutti Agent Workspace App 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.

Tutti Agent Workspace App compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tutti Agent Workspace App this skilltutti-os/tutti3.8k—~1.9kAutomated safety check: PassApache-2.0
Vscode MCP Architecturetjx666/vscode-mcp105—~1.5kAutomated safety check: PassCustom licence
Contributingbutterbase-ai/butterbase-skills534—~1.5kAutomated safety check: PassMIT
Databuddy MCPdatabuddy-analytics/Databuddy1.2k—~711Automated safety check: PassAGPL-3.0
SlintMoosync/Moosync259—~2.4kAutomated safety check: PassGPL-3.0
Nx Monorepoaiskillstore/marketplace433—~2kAutomated safety check: PassNone

Similar skills

  • Vscode MCP Architecture

    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.

    105 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed
  • Contributing

    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

    534 GitHub stars~1.5k tokensUpdated 5 days ago
    DevelopmentAuto-check passed
  • Databuddy MCP

    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.

    1.2k GitHub stars~711 tokensUpdated today
    DevelopmentAuto-check passed
  • Slint

    Moosync/Moosync

    Expert guidance for building, debugging, and working with Slint GUI applications.

    259 GitHub stars~2.4k tokensUpdated 9 days ago
    DevelopmentAuto-check passed
  • Nx Monorepo

    aiskillstore/marketplace

    Nx monorepo management skill for AI-native development. An agent skill from aiskillstore/marketplace.

    433 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Managing MCP Index

    Comfy-Org/workflow_templates

    Builds and maintains templates/index.mcp.json for Comfy Cloud MCP tools.

    1.3k GitHub stars~1.9k tokensUpdated today
    Frontend & DesignAuto-check: notes

More from tutti-os/tutti

All 8 skills in this repo
  • Tutti UI System

    tutti-os/tutti

    A skill your agent uses when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business…

    3.8k GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check passed
  • Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove…

    3.8k GitHub stars~3.3k tokensUpdated 3 days ago
    Auto-check passed
  • From a Tutti checkout, run, audit, freshly replay, publish, or diagnose Session Replay cassettes that are driven by case-repository scenario scripts (CDP), not by interactive UI recording.

    3.8k GitHub stars~4k tokensUpdated 3 days ago
    Auto-check passed
  • Create, convert, or repair one Tutti workspace app as either a self-contained publishable package under package/ or a Chrome-style local debug app under .tutti/dev-app/.

    3.8k GitHub stars~5.9k tokensUpdated 3 days ago
    Auto-check passed
  • Review tutti git diffs for project structure, layering, module ownership, and duplicate event-center infrastructure by planning focused architecture review tasks, then having the main agent…

    3.8k GitHub stars~2.3k tokensUpdated 3 days ago
    Auto-check passed
  • Tutti App Release

    tutti-os/tutti

    Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow.

    3.8k GitHub stars~4.1k tokensUpdated 3 days ago
    Auto-check passed

Questions about Tutti Agent Workspace App

What does Tutti Agent Workspace App do?

Build or evolve a complex agent-enabled Tutti workspace app repository. Tutti Agent Workspace App is an agent skill from tutti-os/tutti. Build or evolve a complex agent-enabled Tutti workspace app repository.

When should I use Tutti Agent Workspace App?

Tutti Agent Workspace App fits situations like: tutti apps with web/server/shared monorepos; @tutti-os/agent-acp-kit local agent runtimes; kit-owned TUTTICLI agent/composer discovery; dynamic agent catalogs.

How do I install Tutti Agent Workspace App in Claude Code?

Run `npx skills add tutti-os/tutti --skill tutti-agent-workspace-app -a claude-code`. Or copy the skill folder (services/tuttid/service/workspace/agent_workspace_app_reference in tutti-os/tutti) into .claude/skills/tutti-agent-workspace-app in your project. Claude Code loads it when a task matches its description.

How do I install Tutti Agent Workspace App in Codex?

Run `npx skills add tutti-os/tutti --skill tutti-agent-workspace-app -a codex`. Or copy the skill folder (services/tuttid/service/workspace/agent_workspace_app_reference in tutti-os/tutti) into .agents/skills/tutti-agent-workspace-app in your project. Codex loads it when a task matches its description.

Can I use Tutti Agent Workspace App in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tutti-os/tutti --skill tutti-agent-workspace-app -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tutti-agent-workspace-app, .gemini/skills/tutti-agent-workspace-app, .github/skills/tutti-agent-workspace-app and .opencode/skills/tutti-agent-workspace-app in your project.

What does Tutti Agent Workspace App need to run?

Going by SKILL.md and its folder, Tutti Agent Workspace App needs the command-line tools its instructions call (pnpm and python3). Our summary lists: Python 3.

Does Tutti Agent Workspace App access the network?

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.

Is Tutti Agent Workspace App safe to install?

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.

What licence does Tutti Agent Workspace App use?

Tutti Agent Workspace App is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tutti Agent Workspace App use?

About 1.9k tokens (SKILL.md is roughly 7.4k 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 10k tokens, read only when the agent opens those files.

What are the alternatives to Tutti Agent Workspace App?

Skills that share tags, products or a category with Tutti Agent Workspace App: Vscode MCP Architecture (tjx666/vscode-mcp, 105 stars), Contributing (butterbase-ai/butterbase-skills, 534 stars), Databuddy MCP (databuddy-analytics/Databuddy, 1.2k stars) and Slint (Moosync/Moosync, 259 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tutti Agent Workspace App?

tutti-os (a GitHub organization) maintains it in tutti-os/tutti, which has 3,811 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 8, 2026.

Source: tutti-os/tutti on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.