SKILL.md reference
Retired. Autonnel's agent-facing API is the MCP server; the standalone SKILL.md repository is no longer published.
This page is retired. The agent-facing surface is the MCP server.
SKILL.md was the older, plain-Markdown form of autonnel’s agent documentation. It predated the MCP server, and the workflow it described — an agent fetching raw Markdown from a public repository at session start and caching it as prompt context — has been superseded. The standalone autonnel/skills repository it pointed at is no longer published, and any link to it or to its raw file URLs will fail.
What to use instead
- An agent that speaks MCP: connect to
/api/mcp. Tools are self-describing — the client reads names, descriptions and input schemas on connect, so there is nothing to fetch or cache. See MCP server. - A deterministic integration: call the REST surface directly. See External endpoints.
Both use the same API key and the same writeAccess gate. See API keys.
Why the change
Repeating tool signatures in prose was duplication that drifted: the Markdown was a snapshot, the API kept moving, and nothing failed loudly when the two disagreed. Introspection cannot drift, because the schema an agent reads is the schema the handler validates against.
What introspection genuinely cannot express — the error envelope, the write rules, the build order, and where MCP and REST diverge — is documented on the MCP server page instead.
Related
- MCP server — the agent-facing integration path.
- External endpoints — the REST surface.
- API overview — authorization model and surface area summary.
- API keys — required for any API call an agent makes.