- scripts/skill.sh: install (bundled or path) / activate / deactivate / uninstall (refuses while enabled) / list - skills-enabled + skills-available dirs under the data root; a skill not in skills-enabled is not enabled or available for use - pi adapter: MOSAIC_SKILLS -> --skill per dir; --no-skills when none - agent.sh: seat definitions declare skills[]; resolution against skills-enabled refuses the launch loudly when missing - ms-* skills completed (owner-authored canon, hands-off): ms-tools adapted to the runtime, ms-file-read/write/agent/conductor bodies written in the owner's style; ms-agent-watch + ms-unslop untouched - tasks/USER.md onboarding fixtures; suite hardening (nested def path, user seed, mock-adapter dispatch evidence) Suites: config 24, task 74, release 14, conductor 17, verify PASS. RELEASE 0.0.12 packaged; health-gated activation on merge. Closes #40, closes #41, closes #42
1.7 KiB
1.7 KiB
name, description, disable-model-invocation
| name | description | disable-model-invocation |
|---|---|---|
| ms-tools | Reference for all available tools in Mosaic Stack. | false |
ms-tools
You are a Mosaic seat agent. The maintained tooling lives in the repository
scripts/ directory (conductor side) and /opt/mosaic (your container).
Use it FIRST for the tasks below. Improvising with raw commands causes the
recurring failures this skill exists to prevent.
Lifecycle
- scripts/bootstrap.sh creates the system config. Idempotent, never overwrites.
- scripts/build.sh builds the release image. Tag comes from RELEASE.
- scripts/verify.sh runs the gated startup check. Exit 0 means MOSAIC_HELLO_OK.
- scripts/release.sh ensure aligns what is installed with RELEASE. No manual release commands; drift is detected and corrected at launch.
Tasks and runs
- scripts/run-task.sh run <task.json> executes a governed task. Every run leaves a write-once record under /runs/.
- node scripts/mosaic-task.mjs list shows run history.
- node scripts/mosaic-task.mjs show inspects one run: receipts, snapshots, stderr.
- node scripts/mosaic-task.mjs retry re-executes a recorded task as a new run. The old record stays.
Inter-agent communications
- tools/tmux/agent-send.sh # Send a tmux message to an agent launched in tmux
Seats
- scripts/agent.sh launches an interactive seat. It onboards the user if needed, then opens the TUI with contracts, identity, and user context.
- agents// holds a seat definition: agent.json plus SOUL.md.
Rules
- Exit codes: 0 ok, 1 failed, 2 invalid input, 3 config missing, 4 usage.
- A refusal is evidence. Diagnose it; do not route around it.
- Full reference: docs/TOOLS.md.