Guides

Agent skills

If a coding agent writes your pipelines, give it the skills. They teach it morca's current API: steps and partitions, morca.tables, the morca command, morca.toml and deploys. Then it writes code that compiles against the release you use, not against what it remembers. They follow the Agent Skills spec, so any agent that reads skills can use them.

Installing them

Claude Code (2.1.275 or later):

/plugin install magmalake --marketplace magmalake/skills

On an older Claude Code, add the marketplace first:

/plugin marketplace add magmalake/skills
/plugin install magmalake@magmalake

The plugin also installs the two skills these lean on: Modular's mojo-syntax, which keeps an agent writing current Mojo, and mojoshelf's mojoshelf-consume, which finds the tins and adds them to a project.

Codex, Cursor and other agents, with Node.js installed:

npx skills add magmalake/skills

That installs every skill where your agent looks for them, and npx skills update updates them. To install just one:

npx skills add magmalake/skills --skill morca

By hand: clone magmalake/skills and copy a skill's folder into your agent's skills folder, which for Claude Code is ~/.claude/skills/.

The skills

  • morca: pipelines in Mojo. It covers steps, partitions by month, day, hour or name, schedules and sensors, steps that call Dista or a Rust worker, and tables through morca.tables. It also covers the morca command (registering, backfills and fills, retiring, status), morca.toml and worker pools.
  • dista: distributing a step's work with Dista: tasks, shuffles, worker slots, and the rules for forking workers.
  • magmalake-apps: a whole project. It covers the layout, the lake, a web app over its tables, running it locally, the image, and deploying to a Hetzner server with upgrade steps and a beta stack.
  • mojo-data-performance: making Mojo data code fast, from per-row loops to readers and codecs, with the measurement behind every rule.

Staying current

Each skill names the release it was written for. The skills repo's CI compiles every Mojo example in them against the pinned morca and Dista, so a morca release that changes the public API fails there before it can mislead an agent. When you move to a new morca, update the skills too.