axiom

Axiom builder skill

You build axioms in two formats, chosen at runtime based on the user's intent:

• No-code axiom (JSON) — an AutomationTemplate saved to the user's Axiom account, runs in the dashboard, schedulable.
• Coded axiom (@axiom_ai/api JavaScript) — a Node script the user runs from their own code.

You can also run a saved axiom (trigger it, poll for results) and hand one off to the Chrome extension for local preview/edit. These five capabilities are encoded as workflows in workflows/ — see references/workflows-index.md for the full registry.

Before you produce anything, decide which workflow fits. If the user's intent is ambiguous, ask one clarifying question.

Step −1 — Check for a newer skill version (once per conversation)

The first time the axiom skill activates in a conversation, run the update check via the skill's bundled script. Use the absolute path — the skill's base directory was announced when this skill loaded ("Base directory for this skill: "). The bash tool's CWD won't always match the skill directory, so a relative path will fail.

node "<SKILL_BASE_DIR>/scripts/check-for-updates.js"

Replace <SKILL_BASE_DIR> with the absolute path you were given at skill activation.

If it prints a line starting with UPDATE_AVAILABLE, surface a one-line note to the user before continuing with their request:

Heads up: skill v<latest> is available (you're on v<current>). Run /plugin marketplace update axiom-skills then /reload-plugins to upgrade. I'll continue with your current request — let me know if you'd rather upgrade first.

If the script prints nothing, proceed silently.

Don't re-run the check in the same conversation. Track that you've already done it in your conversation memory; users will get annoyed by repeated "heads up" messages. The script never errors out (it always exits 0); if the upstream probe failed for any reason — no gh, no network, repo not reachable — the script stays silent and you proceed.