monarchjuno Guru Packs
Manage only explicitly requested Guru Pack operations. Each Pack is data-only and contains exactly one reusable kind—Wiki, Lens, or Method—and a project has at most one installed source slot per kind. Packs never contain Evidence, Decisions, static files, hooks, scripts, MCP servers, or order code.
Guru Mode never makes a Pack install, update, removal, creation, or publication implicit. Every Pack lifecycle and publishing action still requires an explicit user request.
Resolve every linked reference path relative to this loaded SKILL.md. The
loaded Skill directory is authoritative: when it is under
<project>/.agents/skills/, ../../shared/... reaches
<project>/.agents/shared/.... Never substitute a user-global .codex path,
another plugin-cache path, or skills/shared/.... Read the workspace and Guru Pack
contract and the
record contract and the
Runtime contract before using
the CLI.
The CLI namespace is pack: invoke
gurumaker pack <install|list|inspect|update|remove|create|check>.
Install only into an initialized workspace whose matching local collection and
source slot are empty. Installation keeps the exact Git source read-only under
.guru-maker/packs/<kind>/ and seeds guru-maker/<kind>/ once. Ordinary
retrieval uses only the local copy. Updating or removing the source slot never
changes local memory.
Create one kind-specific Pack from explicitly selected local Markdown elements
and preserve their hierarchy within that collection. Pack elements must be
independently self-contained. A Wiki Pack must include every exact see_also
target authored by its declared elements. Validation fails when a target is
outside the manifest; creation never follows or automatically adds it. Lens
and Method remain without structured navigation.
Use system Git credentials without reading, storing, or printing them. Do not initialize Git, commit, push, publish, or alter local memory unless the user separately requests that action. Product plugin updates do not update Packs.