Skip to main content
Timoni ships agent skills and a documentation MCP server so that AI coding agents can operate Timoni end-to-end: from authoring modules and bundles to orchestrating multi-cluster deployments.
Evaluated with agentsThe skills are evaluated by running agents against them with no other documentation, on realistic tasks that cover the full lifecycle: from discovering a module’s config schema to previewing changes with a server-side diff, applying, checking status and cleaning up.

Agent skills

Timoni publishes its skills following the Agent Skills standard. Each skill is a self-contained SKILL.md file that an agent loads into its context when a task calls for it.

Install the skills

Install all the Timoni skills into any supported agent (Claude Code, Cursor, Codex, Copilot and others) with:
The command discovers the skills from the Timoni website and places them in the agent’s skills directory.

What the skills cover

Docs MCP server

The Timoni documentation is exposed as a streamable HTTP MCP server at https://timoni.sh/mcp. It requires no authentication and provides tools for searching the documentation and fetching pages as markdown, so that agents can answer questions and look up details that go beyond the skills, using the latest published docs.

Connect the MCP server

Register the server for the current project with:
Or add it to the project .mcp.json file to share it with your team:
Every page of this website is also available as markdown by appending .md to its URL, for example timoni.sh/bundle.md. The full index is published at timoni.sh/llms.txt for agents that work without MCP.

Example prompts

With the skills installed and the MCP server connected, agents can carry out tasks such as:
  • Deploy the oci://ghcr.io/stefanprodan/modules/redis module in the cache namespace with persistence enabled, and show me the diff before applying.
  • Create a bundle that deploys podinfo and redis to the apps namespace, reading the redis password from the redis-auth Secret at apply time.
  • Write a runtime for the staging and production kube contexts and apply the bundle to both, with two replicas in staging and three in production.
  • Scaffold a Timoni module for my web app with a typed config for the image, replicas and ingress host, vendor the cert-manager CRDs, and add a test job.
  • Upgrade all the instances in the monitoring namespace to the latest module versions and report their status.
Agents operating Timoni follow the same safe workflow as humans: validate with timoni mod vet and timoni bundle vet, preview with --diff or --dry-run, apply, then confirm with timoni status. Scope an agent’s cluster access with a dedicated kube context and namespace when trying it out.