Skip to content
june

Skills

There is no official June skill yet. You don't need one to give an agent accurate June context: use the MCP server when your client supports it, or llms.txt and the Markdown docs otherwise.

What a skill would add

The docs say what June does, and the MCP server lets an agent search and read them as it works. A skill would add the procedure: what to do, in what order, as instructions an agent loads when the task calls for it. It would point into the docs rather than repeat them:

  • When to use June. Several model calls that depend on each other, or that mix with your own async code, are June's job; one call or one agent loop is the AI SDK's. What June doesn't do is the boundary.
  • How to write a workflow. A file that default exports a component, step ids derived from the data they're about, and <Parallel> around independent work. Step identity and Parallelism and concurrency have the rules.
  • What to run to check it. june doctor for keys, june run --json for output a script can read, and tests with a mock model from ai/test, so they need no key or network. See CLI and Testing.
  • Where to look things up. The MCP server's search_docs and get_doc, or llms.txt.

When a June skill ships, this page will say how to install and use it.

Next