genie MCP工具

Install

The one-paste install at the top fetches the signed binary for Linux or Apple Silicon macOS and finishes with genie install. Stable is declared for Linux and macOS: both run in the release gate, so a change that breaks either one does not ship. Windows is not supported; WSL2 works but is not on the tested matrix. Coming from an earlier version? UPGRADING.md covers what changed, what left, and how to clean up.

<details> <summary>What the install delivers, consent scopes and release verification</summary>

Genie ships exactly two surfaces: - The signed binary, installed and updated by install.sh and genie update. - The skills and the saved workflows, delivered through the skills.sh channel. genie install and genie update run the pinned skills CLI over the tree the signed release put on disk, copy the workflows into ~/.claude/workflows, and record what landed in ~/.genie/skills-install.json.

The installer hands its arguments to genie install. --integrations auto|codex|claude|all|none (or --skip-integrations) is the consent scope for the skills channel: any value other than none installs to every detected agent skill home, because the skills CLI already installs per agent; none skips the channel, writes no record, and reports skills: skipped (consent: none). To install the binary and skip the skills channel:

curl -fsSL https://raw.githubusercontent.com/automagik-dev/genie/main/install.sh | bash -s -- --integrations none

Each detected agent gets the skills in its own skills home: ~/.claude/skills for Claude Code, and the shared ~/.agents/skills for Codex and the other agents that read it. genie install and genie update install the skills from the tree the signed release delivered, never from a GitHub ref. The public npx skills add automagik-dev/genie command serves the repository's default branch instead, so it can be ahead of or behind any release.

Every release is cosign-signed with SLSA provenance, and genie update verifies it offline, with no GitHub credential. The repository-hosted .well-known/latest.json and dev.json manifests are the authoritative channel pointers. GitHub's /releases/latest route and prerelease badge are deliberately not channel authority: a promotion advances only a monotonic manifest and never rewrites already-published assets or channel-significant draft/prerelease/latest metadata. Security and releases has the details. </details>

Workflows

A saved workflow is a Claude Code script for a procedure worth running the same way twice. genie install and genie update deliver the catalog to ~/.claude/workflows. Genie v6.261003.1 ships 12. The Workflows docs describe each one. In Codex and other agents without saved workflows, the skills that start them (wish, brainstorm, council, docs, research, skill-audit, workfly) run the same stages by hand.

<details> <summary>All 12 saved workflows</summary>

- brainstorm: runs one round of a brainstorm whose state lives in DRAFT.md, so you answer between rounds, and ends in a reviewed DESIGN.md - council: architecture, delivery, product, security and dissent lenses, then a synthesis; assess only - docs-audit: audits every documentation surface against the live product and ranks the drift; assess only - evidence-gate: verifies a frozen contract of files, commands and claims against the artifact it covers; its only write is the report - observability-review: reviews traced Claude Code sessions in Phoenix and proposes rule changes, each tied to cited evidence; proposal only - pm-ledger-verify: adversarial lenses over uncommitted wish ledger edits - research-sweep: investigates a frozen question against a frozen source list and keeps every claim cited; read only - skill-audit-sweep: sweeps the shipped skills into a keep, improve, update, merge or retire table; assess only - skill-intake: assesses candidate skills from outside the catalog and assigns each exactly one disposition; mutates nothing - test-simplify: audits every test file in scope and proposes batches of tests to delete or consolidate; deletes nothing - wish: the engine behind the wish skill: admission, one executor in a worktree, a gate, an independent review, bounded repair and a PR; merging stays with you - workfly: discovers a procedure and builds its saved workflow, checked by a static test and refuters </details>

Repository packages

Mikro lives in mikro/ with its original Git history, npm lockfile, Node build and independent CI. Its runtime and dependencies are not part of the Genie binary or release payload. Root Bun, Biome and Knip discovery exclude that package; its full npm checks run separately.

The standalone runtime requires Node 22.19 or newer and pins the Pi SDK family to 1.0.2. genie mikro call <agent> --engine rlm|pi selects an engine explicitly; otherwise the agent's engine wins, then rlm. RLM remains the default. Pi uses an isolated native session with read, grep, glob, hermetic git and emit_done, not the RLM Python tool pack or an ambient Pi installation. Both paths retain the caller's schema and citation checks. Missing or partial provider usage is unknown: an observed subtotal is not a complete bill. See the agent schema and standalone upgrade boundary.

Repository checks use Bun 1.3.11 or newer, matching CI: subtree test pruning relies on test.pathIgnorePatterns. This development prerequisite does not change Genie's existing CLI runtime floor.

bun run check
npm --prefix mikro run deps:ci
npm --prefix mikro run build
npm --prefix mikro run check
npm --prefix mikro test

mikro update is for a standalone Mikro Git worktree, including linked worktrees. It refuses the nested package before acquiring update ownership or changing Git state. Update the owning Genie source checkout explicitly instead; genie update remains the signed installed-release update path.

How it compares

Superpowers, Spec Kit and GSD work the same ground. Each of their rows comes from that project's own README.