Agent Skills and AI-readable docs

Combined publishes a small procedural Agent Skill separately from its live product documentation. The skill teaches an agent how to discover, query, paginate, authenticate, and report evidence; these docs and the OpenAPI contract remain the current source of API truth.

Install from skills.sh-compatible clients

npx skills add combined-ai/skills

This follows Tinybird's owner/repository pattern. A bare npx skills add combined is not valid because the CLI requires a source. The public repository is combined-ai/skills, and the installed skill is named combined.

Combined also publishes standards-based same-origin discovery, so compatible installers can use the product URL directly and receive the full skill with its references and helper script:

npx skills add https://platform.trycombined.com

Use with curl only

No skill installer is required:

curl -fsSL https://platform.trycombined.com/skill.md
curl -fsSL https://platform.trycombined.com/llms.txt
curl -fsSL https://platform.trycombined.com/llms-full.txt
curl -fsSL https://platform.trycombined.com/openapi.json

/skill.md is the short procedural skill, /.well-known/skills/index.json is the standard discovery index, /llms.txt is the compact docs index, /llms-full.txt combines all authored documentation, and /docs-markdown/<slug> returns one page. These routes are public and contain no account data. The REST and MCP data surfaces still require authentication and enforce grants.

Why both exist

Fumadocs supplies the processed Markdown and documentation-tree primitives used by llms.txt, llms-full.txt, and per-page Markdown. It does not generate an installable Agent Skill. Combined uses the Agent Skills discovery protocol for that layer, while the hosted Fumadocs output and OpenAPI document remain the live source of product facts.

Agent operating rules

The published skill directs an agent to discover the live catalogue, use logical names, parameterize values, bound results, follow pagination, check freshness, and preserve evidence. Installing the skill does not grant access: REST and MCP still evaluate the current credential and grants on every request.

Treat the hosted skill and docs as updateable instructions. Pin the public skills repository revision if your deployment requires change control, then review updates before promotion. Never place an account token in the skill directory, prompt examples, or installer command.

AI-readable routes

Generated endpoint pages are represented by the OpenAPI contract. Use /openapi.json for exact request and response schemas and /llms-full.txt for concepts and operating guidance.