AI Resources
How coding agents read, cite, and act on the ktx docs - Markdown endpoints, a task router, and copy-paste prompts.
This page is for coding assistants that read or cite the ktx docs. It covers the machine-readable endpoints, a task router for common questions, and copy-paste prompts. It is scoped to documentation lookup and safe command discovery - to wire ktx into an agent client, see Agent Clients.
Markdown endpoints
ktx docs are available as plain Markdown so assistants never have to parse the rendered HTML site.
/llms.txt- a curated index of high-value pages and agent entry points. Start here./llms-full.txt- the entire docs corpus in one response. Use only when a task needs broad context across many pages.- Per-page Markdown - append
.mdto any docs URL:
https://docs.kaelio.com/ktx/docs/getting-started/quickstart.md
https://docs.kaelio.com/ktx/docs/cli-reference/ktx-sl.md
https://docs.kaelio.com/ktx/docs/guides/building-context.mdA request for any docs URL with an Accept: text/markdown header returns the
same Markdown without the .md suffix:
curl -H "Accept: text/markdown" https://docs.kaelio.com/ktx/docs/getting-started/quickstart
Each Markdown response leads with the page title, description, canonical URL, and
Markdown URL; frontmatter is stripped; code blocks and tables are preserved; and
missing pages return a plain-text 404 instead of falling back to HTML. Rendered
pages also expose a Copy as Markdown action near the title.
Retrieval order
- Fetch
/llms.txt. - Pick one or two relevant per-page
.mdURLs. - Fetch
/llms-full.txtonly when page-level docs are not enough.
curl https://docs.kaelio.com/ktx/llms.txt curl https://docs.kaelio.com/ktx/docs/getting-started/quickstart.md
Task router
| User asks the agent to explain... | Read first | Then read |
|---|---|---|
| What ktx does | Introduction | The Context Layer |
| How to start from a checkout | Quickstart | ktx setup |
| How to check project readiness | ktx status | Quickstart |
| How context gets built | Building Context | ktx ingest |
| How semantic YAML works | Writing Context | ktx sl |
| How machine-readable CLI output is shaped | ktx sl | ktx wiki |
Agent instructions
Paste this into a project or system prompt when an assistant needs to answer from the ktx docs:
When answering ktx docs questions:
1. Start with https://docs.kaelio.com/ktx/llms.txt.
2. Fetch the smallest relevant Markdown page (append .md to its docs URL).
3. Prefer the .md route over rendered HTML.
4. Use https://docs.kaelio.com/ktx/llms-full.txt only when the task needs broad docs context.
5. Quote commands exactly from docs pages.
6. If docs and local CLI behavior disagree, say what differs and prefer local verified output.Prompts
Replace project names, connection ids, and business terms with your own values.
Install and configure ktx in a project
Run npx skills add Kaelio/ktx --skill ktx and use the ktx skill to install and configure ktxFind the right command
Find the correct ktx command for this task: <task>. Start with /llms.txt, then fetch the smallest relevant CLI reference .md page. Quote the exact command and flags from the docs.Review semantic changes
Review the ktx semantic-layer and wiki changes in this branch. Check that measures have clear definitions, joins use valid keys, hidden or internal columns are not exposed to agents, and validation passes. List concrete file and line issues first.Guardrails
- Do not invent CLI flags - fetch the relevant CLI reference page.
- Do not scrape rendered HTML when a
.mdroute exists. - Do not treat
/llms.txtas complete documentation - use it as an index, then fetch the linked pages. - Do not include credentials or secrets in prompts, URLs, or copied docs snippets.
- When docs and local CLI behavior disagree, prefer the local CLI output and mention the mismatch.