How do I install the Stop skill?

Run npx skillmds@latest add g-bastianelli/stop in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Stop skill do?

Use when the user wants to stop future Monkey Maestro dispatches for a Linear project. Appends one approved active:false control while leaving existing Superset work untouched. It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stop?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

g-bastianelli (@g-bastianelli) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stop by g-bastianelli — Agent Skill

Name: Stop
Author: g-bastianelli

File contents

stop

Agent resolution: before dispatch, read ${CLAUDE_PLUGIN_ROOT}/shared/agent-runtime-map.md and select the active runtime name for monkey-maestro:linear-reader.

Voice

Read ../../persona.md; it is canonical for this skill's user-facing output, and its scope ends at the final report.

Contract

Read ${CLAUDE_PLUGIN_ROOT}/shared/project-execution-contract.md. Stop is Linear-only. Never call Superset or GitHub, change issue status or relations, or terminate/delete an existing workspace, terminal, or agent.

Workflow

Require one exact Linear project id. Dispatch monkey-maestro:linear-reader in MODE: control and resolve its complete marker-bearing set with scripts/records.mjs resolve-controls.
No usable control returns not-configured. An inactive usable control returns already-stopped. Neither writes anything.
Build a minimal schema-v2 successor with scripts/records.mjs build-control, retaining the run and transport configuration, setting active: false, incrementing revision, and using the current updatedAt.
Show the exact project, run, revision, and active: true -> false, then ask once:

Stop future Maestro dispatches? Existing Superset work keeps running. (y / cancel)

On approval, append one Linear project comment. On denial, do nothing. Dispatch the reader once more in MODE: control and require the exact successor; report failed verification without rewriting.

Report

monkey-maestro:stop report
  Project/run: <project id> / <run id>
  Control:     schema v2 · revision <n> · inactive
  Existing:    Superset work untouched
  Next:        idle

Frequently asked questions

Stop