Menu

Individual skill

loom

Mandatory routing skill. When the user explicitly invokes @loom, call the matching Loom MCP route before any repository work; plain delivery requests must start with loom.plan.

plugins/codex/skills/loom/SKILL.md

Read pinned source

Source commit 7cf9b229d22656ac28cb6fa47d26bb6230155b0a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,442
Repository last updated
Nov 3, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# loom

Use Loom MCP as the workflow authority. Do not inspect `.loom` directly, invent a workflow in chat, or touch repository files before the route below returns.

This is the mandatory routing entrypoint. When a user invokes `@loom`, resolve the Loom route before any repository work. For `@loom <request>` or `@loom plan <request>`, call `mcp__loom__plan` when it is available. If deferred loading hides that tool, make one targeted search for `Loom plan software delivery @loom`, then call the returned plan tool. Do not search for deploy, inspect, or generic skills, and do not call `exec_command`, `apply_patch`, or other repository tools before the plan call returns.

## Route

Use the current workspace as `projectRoot`.

- `@loom <request>`: call `loom.plan` with `{ projectRoot, requestText: "<full request>" }`.
- `@loom plan <request>`: same call with `<request>`.
- `@loom continue|resume|proceed|next`: call `loom.continue`.
- `@loom verify`, `@loom status`, `@loom knowledge ...`, and `@loom deploy ...`: call the matching Loom tool directly.