Skip to main content
Tools tell an agent what it can call. Skills tell it how to make something good — Moda’s design doctrine, the format-by-format workflow, the verify loop, the failure modes that look like success. An agent with the tools and no skills produces plausible-looking, badly designed output. The same nine workflows reach your agent three ways, depending on where it runs.

​
The nine skills

Every one of them opens with the same check (is the CLI or connector there, are you signed in, what is this account entitled to) and the same rules: deliverables over plumbing, an explicit verify loop, and anything that spends credits labeled with its cost class up front and a receipt after.
The connector’s copies of these workflows route one thing differently: its tool surface reads sites but does not build or publish them, so building or publishing a website happens in the Moda app. The skill says so at the point it matters; on the CLI the moda site verbs do it directly. Brand kits are not a difference — brand_create is a connector tool, matching moda brand create. (Attaching logo images to a kit stays an app step on the connector; the CLI has moda brand add-image.)

​
With the CLI

That installs the skills for Claude Code, Codex, Cursor, and anything else that reads the standard skills directory. In Claude Code you can instead take them through the plugin, which keeps them updated through the marketplace:
Skills are hash-pinned once installed and never update behind your back — re-run npx skills add moda-design/moda to pick up a new release. The CLI updates separately (npm i -g @moda-design/moda).

​
With the connector: load_skill

The Moda connector serves the same guidance itself, so a chat host needs no upload at all. load_skill is a normal tool call — free, fast, and always current, because the server is the one holding the text.
The tool’s own description carries the whole routing table, so the model can pick the right guide without loading anything first. Forty-plus entries, in four groups: Good moments to call it: before authoring a format for the first time in a conversation, when a fill or effect gets rejected, and when a result looks wrong. The guides are free — a model that reads one first is cheaper overall than one that guesses and repairs.

​
With claude.ai: skill ZIPs

Uploading the skills to claude.ai as Agent Skills gets you host-level auto-invocation: Claude matches the request against each skill’s description and pulls the right one in without being told. This complements the connector’s load_skill — the connector still works with no skills uploaded at all.

Turn on code execution

Settings → Capabilities → Code execution and file creation. Skills ride that capability.

Download the ZIPs

Grab the moda-<skill>.skill.zip files from the latest release.

Upload each one

Settings → Capabilities → Skills (also at claude.ai/customize/skills) → + → Upload skill. The upload format takes one skill per ZIP, so nine skills means nine uploads.
Team and Enterprise admins: upload the same ZIPs once under Organization settings → Skills → + Add. They are provisioned to every member and enabled by default — zero end-user setup.
Uploaded skills are static snapshots: a new Moda release means re-uploading (one admin action for an org). The connector’s load_skill never goes stale, which is why it is the better default if you only want one.

​
Which should I use?

Whichever route you take, the content is generated from one source, so the workflow your agent learns is the same across transports.