maestro-settings
View and change Maestro toggles (terse, frontier, context-bar, discipline, verify) via the settings CLI
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- maestro-settings
- license
- MIT
- description
- View and change Maestro toggles (terse, frontier, context-bar, discipline, verify) via the settings CLI
03 SKILL.md 正文
View or change Maestro settings for this project. The settings CLI manages
five primary toggles: terse, frontier, context-bar, discipline
(the optional enforcement-hook pack; off is the default), and verify
(the optional S7.3 verify-gate Stop hook; off is the default).
When the user invokes this skill, run the settings CLI from the repo root. Do not edit settings files by hand.
Command launcher
Use node settings/cli.cjs when Maestro is installed in the project root. If
that file is not present and this skill is loaded from the Maestro Codex
plugin, locate the plugin root by walking up from this SKILL.md until
.codex-plugin/plugin.json is present, then run:
node "<maestro-plugin-root>/settings/cli.cjs" ...
Discover available commands
node settings/cli.cjs --help
If settings/cli.cjs is not present, use the plugin-root launcher above.
Common operations
List current settings:
node settings/cli.cjs status
Set a toggle (the CLI takes a set subcommand):
node settings/cli.cjs set terse <off|lite|full|ultra>
node settings/cli.cjs set frontier <off|single:<model>|fusion:<preset>>
node settings/cli.cjs set context-bar <on|off>
node settings/cli.cjs set discipline <on|off>
node settings/cli.cjs set verify <off|warn|block>
If a subcommand name or argument differs from the above, follow the usage
printed by --help — do not guess flags.
Notes
- Changes persist in Maestro's settings store and apply to subsequent agent turns in this project.
- Requires
nodeonPATH. A project-local Maestro install is optional when the skill is loaded from the Maestro Codex plugin.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.