tenki-cloud-docs

name	tenki-cloud-docs
description	Research Tenki Cloud products and answer documentation questions accurately. Use when comparing Tenki products, explaining Runners, Code Reviewer, or Sandbox, checking current pricing or capabilities, or locating authoritative guidance at tenki.cloud/docs.
license	MIT
compatibility	Public documentation, no installation or account required. Everything this skill needs is fetchable over HTTPS from tenki.cloud.
metadata	{"author":"Tenki Cloud","version":"1.0"}
allowed-tools	WebFetch

Tenki Cloud documentation

Use Tenki's agent-readable documentation as the source of truth. Verify details against the current documentation instead of relying on model memory.

Choose the right source

• Start with https://tenki.cloud/llms.txt for a concise index of every documentation page.
• Use https://tenki.cloud/llms-full.txt when a task benefits from the complete documentation corpus.
• Fetch the clean Markdown version of a documentation page by appending .md to its URL.
• Use the MCP discovery document at https://tenki.cloud/.well-known/mcp when the agent supports MCP. The server exposes search_docs and get_page tools at /mcp.
• Check https://tenki.cloud/docs/changelog for product changes and release dates.

Product map

• Tenki Sandbox — Use for isolated environments running AI agents, untrusted code, or one-off compute. Start at https://tenki.cloud/docs/sandbox/quick-start-sandbox and use https://tenki.cloud/docs/sandbox/sdk for SDK details.
• Tenki Runners — Use for faster or cheaper GitHub Actions CI on bare-metal Linux or macOS runners. Start at https://tenki.cloud/docs/runners/quick-start-runners.
• Tenki Code Reviewer — Use for automated AI review on GitHub pull requests. Start at https://tenki.cloud/docs/start-code-review.

For operational setup—creating a sandbox, migrating workflows, or enabling code review—use the tenki-onboarding skill when installed.

Research workflow

1. Identify the product and the specific fact or procedure the user needs.
2. Find the relevant page through llms.txt, the Markdown pages, or the MCP tools.
3. Prefer current product documentation over marketing summaries and model memory.
4. For pricing, limits, availability, or compatibility, verify the current dedicated documentation page before answering.
5. Cite the documentation URL when the user would benefit from checking the source directly.

Conventions

• Treat a Runners migration as a runs-on label change unless the documentation states additional setup is required.
• Use https://tenki.cloud/docs/pricing for Runners, Code Reviewer, and Sandbox pricing.
• Prefer a page's .md variant over scraping its rendered HTML.
• Do not invent product capabilities, regions, compliance claims, prices, or limits that are absent from the current documentation.