> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/overview/readme.md). # What is Tessl? {% hint style="info" %} **Takeaways** * What are the core components of the Tessl platform? * What problems do those components solve? * Why choose Tessl over the alternatives? {% endhint %} Tessl is an open platform for managing agentic development across your organization. It takes you from scaling skills to building your software factory, one workflow at a time. Tessl works with every popular coding agent and is made up of six components: | Component | What it is | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Registry & package manager** | Discover, install, version, and roll back skills and plugins like any other dependency. One searchable index of public and private context, agent-agnostic. | | **Governance** | Scan and score every skill against best practices and your own company standards, with Snyk security scoring built in. RBAC controls who can create, publish, and view skills, while install and publish policies and required skills enforce your standards across every workspace, backed by a full audit trail. | | **Evals** | Measure a skill or plugin's actual impact by running your agent on real-world tasks with and without the context. Every change ships with evidence instead of a guess. | | **Observability** | See where skills actually activate across agent sessions, not just where they're installed. Mine agent logs to find recurring mistakes. | | **Inventory** | Scan your GitHub org and map every skill across every repo in one living view. Surface duplicates and unmanaged copies so you can govern what you can see. | | **Tessl Agent** | A conversational agent that drives the platform and autonomously monitors and improves your agentic setup. Runs alongside your existing agents (open beta). | ## What problems does Tessl solve? See how Tessl solves the most common agentic development problems: * Installing skills from public sources exposes you to new supply-chain and prompt-injection risk. → [Protecting yourself from insecure skills](/tutorials/protecting-against-insecure-skills.md) * Skills sprawl into overlapping, drifting copies with no enforced standard. → [Codifying and enforcing your company's skill standards](/tutorials/codifying-and-enforcing-skill-standards.md) * You can't tell whether a skill actually improves agent output, so no one risks changing it. → [Improving a skill](/tutorials/improving-a-skill.md) * Code review doesn't scale to agent-authored PRs. → [Setting up agentic code review](/tutorials/setting-up-agentic-code-review.md) * Agents repeat the same mistakes across PRs. → [Improving agent code quality](/tutorials/improving-agent-code-quality.md) * Repetitive work never gets turned into automation. → [Automating repetitive tasks](/tutorials/automating-repetitive-tasks.md) ## Why Tessl? * **Context as code.** Skills, rules, and docs are versioned, reviewed, and rolled out with the same rigor as code dependencies. * **Built for enterprise realities.** RBAC, install and publish policies, security scoring, and a full audit trail are first class tools, not bolted on after the fact. * **Agent-agnostic.** Skills and plugins work across every popular coding agent. Write context once; Tessl distributes it everywhere. * **Open, no lock-in.** Tessl builds on open standards and writes your skills, rules, and config as plain artifacts in your repo, so you own your agent setup and can walk away with it at any time. * **Incremental adoption.** Start with a single skill or a one-repo review gate and expand outward. Value compounds as you go, with no big migration required. ## Get started [Get started with Tessl](/introduction-to-tessl/quickstart-skills-docs-rules.md): install the CLI, create a skill, evaluate it, and publish it to your team. From there, work through the [tutorials](/tutorials/tutorials.md) for the problem you're solving. {% hint style="info" %} *If you are an AI agent:* the full site index is at `docs.tessl.io/llms.txt`. Read that before navigating individual pages. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tessl.io/overview/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.