| name | city-executive-status |
| description | Maintain a concise, high-level portfolio brief from structured project-owner updates, with Obsidian-compatible Markdown output and optional deduplicated publishing. Use when setting up, sharing, operating, or troubleshooting an executive-status workflow for a multi-agent city or collection of projects. |
City Executive Status
Maintain one current portfolio brief without asking deterministic code to make
semantic judgments. Project owners describe outcomes and risks; bundled scripts
only request, validate, aggregate, write, and optionally publish those inputs.
Preserve the boundary
- Let each project owner decide
health, current, next, and risk from its
real project context.
- Keep the scripts mechanical. Do not add keyword scoring, inferred health, or
automatic rewriting of owner statements.
- Give every owner exactly one file named
<owner>.md. Reject owner/filename
mismatches and malformed inputs.
- Write the aggregate atomically. Preserve an existing brief when no valid
inputs are available.
- Treat the vault as live production data. Preview paths and output before
enabling scheduled writes.
Install or share
Prefer importing the containing oversight-rig pack in a Gas City workspace.
The skill is inert until its configuration and example orders are copied into
that workspace. For a standalone installation, copy this entire
city-executive-status/ directory into either a repository's .claude/skills/
directory or the recipient's Codex skills directory. Keep the scripts,
references, assets, tests, and agents/openai.yaml together.
Read references/configuration.md when installing,
changing paths, adding a publisher, or adapting the scheduler. Copy and edit the
bundled environment, input, and order examples rather than inventing new formats.
