> ## Documentation Index
> Fetch the complete documentation index at: https://to11.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# What is to11?

> What to11 is, who it's for, and how it fits the way your team works with LLMs and coding agents.

to11 is a hosted control plane for the text your team gives to models and agents. Chat prompts and coding-agent skills live in to11 as versioned resources instead of strings in application code or files copied between laptops, and the work your coding agents do can be uploaded and read in one place.

## Who it's for

* **Teams that use coding agents** such as Claude Code and Codex, and want every developer's agent to follow the same company instructions, kept current without anyone copying files around.
* **Teams that ship LLM features** and want prompts out of application code, so a wording change is a publish rather than a deploy, with a history of every version.
* **Engineering leads** who want to read what their team's Claude Code sessions did: the prompts, the tool calls, the tokens, and what that usage would cost at API prices.

## What you get

### Skills

A skill is a folder of instructions, with a `SKILL.md` entry document, that a coding agent reads from its skills directory. You store a skill in a project with the to11 CLI, and every machine that follows the project receives the new version on its next sync, in the directories Claude Code, Codex, and other agents read. See [Skills](https://to11.ai/docs/skills/overview.md).

### Chat prompts

A chat prompt is a versioned template of messages, variables, tools, and model settings. You author it in the dashboard and your application renders its newest version at runtime with the [TypeScript](https://to11.ai/docs/reference/typescript-sdk.md) or [Python](https://to11.ai/docs/reference/python-sdk.md) SDK, then sends it with the provider client you already use. See [Prompt management](https://to11.ai/docs/platform/prompts/overview.md).

### Sessions

The to11 CLI uploads the transcripts of the Claude Code sessions you run, with secrets masked, to a project. The dashboard lists them and shows each one as a thread of prompts, responses, and tool calls, with its token usage and an API-price estimate. See [Sessions](https://to11.ai/docs/sessions/overview.md).

### Access and accountability

Members sign in with GitHub, Google, or Microsoft and get access through roles at the organization, workspace, and project level. Applications and CI use scoped API keys. Changes are recorded in audit logs. See [Platform](https://to11.ai/docs/platform/overview.md).

## How it's organized

Everything nests into **Organization → Workspace → Project**. Prompts, skills, environments, and sessions belong to a project. See [Core concepts](https://to11.ai/docs/get-started/concepts.md).

## Next steps

> [card] [Quickstart](https://to11.ai/docs/get-started/quickstart.md)
>
> Create a project and use it from the SDK and the CLI.

> [card] [Core concepts](https://to11.ai/docs/get-started/concepts.md)
>
> How to11 is organized.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.