Author and consume packages and flows with Claude Code
Install Axiom's Skills into Claude Code with axiom skills install so your agent knows the create→validate→push→publish authoring loop AND the search→inspect→source→invoke loop for using published nodes, then drives the axiom CLI through the shell.
View as MarkdownAxiom lets Claude Code author packages
and flows for you — and find, verify, and call already-published ones — through
Skills: Markdown contracts that teach the agent each workflow and the sharp
edges that make it fail. Install them with axiom skills install, then the agent
drives the axiom CLI through the shell.
That is all Claude Code needs: it already runs shell commands, so the Skill's
workflow knowledge plus the CLI's --json output is enough for the agent to
author, validate, and publish — or to discover, inspect, and invoke a published
node — end to end. There is nothing else to install or register.
Install the Skills
The axiom CLI ships the Skills embedded in the binary, so installing them
needs no checkout and no network:
# From your project directory.
axiom skills installThis writes the Skills into ./.claude/skills by default — project-local, so
they travel with the repository and your agent picks them up the moment it opens
the project. The command prints what it installed:
✓ axiom-client-authoring → .claude/skills/axiom-client-authoring
✓ axiom-consume → .claude/skills/axiom-consume
✓ axiom-flow-authoring → .claude/skills/axiom-flow-authoring
✓ axiom-instance-authoring → .claude/skills/axiom-instance-authoring
✓ axiom-package-authoring → .claude/skills/axiom-package-authoring
Installed 5 skill(s) into .claude/skills.
Open the project in Claude Code — it picks up SKILL.md automatically.Claude Code reads any SKILL.md under a .claude/skills/ directory
automatically; there is no enable step.
Choose where they install
| Command | Target | Use when |
|---|---|---|
axiom skills install | ./.claude/skills | Per-project — the Skills commit alongside your code. |
axiom skills install --global | ~/.claude/skills | Every project on your machine. |
axiom skills install --dir DIR | DIR | An explicit location. |
axiom skills install --force | (as above) | Overwrite Skills that already exist in the target — otherwise existing copies are left untouched and reported as skipped. |
List what the binary bundles without installing anything:
axiom skills list
# axiom-client-authoring
# axiom-consume
# axiom-flow-authoring
# axiom-instance-authoring
# axiom-package-authoringWhat each Skill covers
| Skill | Use it to |
|---|---|
axiom-package-authoring | Author a node package — the create→validate→dev→push→publish loop, the frozen per-language node signatures, how to read axiom validate --json as a fix loop, and the sharp edges (messages before nodes, PascalCase names, commit and push before axiom push). |
axiom-flow-authoring | Author a flow with axiom flow — the full flow.yaml schema and the new→validate→compile→run→publish (and pull) workflow, including pauses, conditional branches, loops, joins, and nested subflows. |
axiom-client-authoring | Author a client (typed SDK) with axiom client — the declarative axiom-client.yaml→sync→download loop for bundling published nodes/flows into an SDK for another codebase. |
axiom-instance-authoring | Bind a Generic node's port(s) to a real type with axiom instance create — the declare→create→reference loop for turning a marketplace connector (a database query, an HTTP call) into a node typed for one specific table or endpoint. |
axiom-consume | Find, verify, and call already-published nodes and flows — the search→inspect (schema)→source (code + full repo)→invoke→pin loop for using someone else's marketplace artifact, including how to trust a third-party node before wiring it in. Also the propose/feedback loop: when the catalog is missing something the agent needed, or a node or the CLI was awkward, it reports that after trying (axiom propose, axiom feedback). The consume counterpart to the authoring Skills, and the same catalog surface the hosted MCP server exposes. |
Install the Skills manually
If you are not using the CLI binary, copy the Skill directories straight into a Claude Code skills directory:
cp -r skills/axiom-client-authoring ~/.claude/skills/
cp -r skills/axiom-consume ~/.claude/skills/
cp -r skills/axiom-flow-authoring ~/.claude/skills/
cp -r skills/axiom-instance-authoring ~/.claude/skills/
cp -r skills/axiom-package-authoring ~/.claude/skills/This is equivalent to axiom skills install --global — the embedded copies the
CLI installs are generated from these same source directories.
Next steps
- Write your first node and run your first flow — the workflows the Skills encode.
- Publish a flow to the marketplace — the last step the flow Skill drives.