verify-maestro
100 / 100 · Low risk
Fine to try.
Verify a change in the maestro repository on the running product - install the checkout into a scratch HOME, doctor it, drive the CLI the way a user does, and capture the transcript as proof. Use before claiming a maestro change reached the installed, live, or journey layer.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'verify-maestro' ] || [ -L ~/.agents/skills/'verify-maestro' ]; then echo 'A skill folder named verify-maestro already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/ReinaMacCredy/maestro' "$d" && git -C "$d" checkout --quiet '69ee7fc3253b283ead8813c4a6929f89c3ae70a4' -- '.agents/skills/verify-maestro' && mkdir -p ~/.agents/skills && cp -R "$d"/'.agents/skills/verify-maestro' ~/.agents/skills/'verify-maestro' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'verify-maestro' ~/.claude/skills/'verify-maestro' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/ReinaMacCredy/maestro/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 69ee7fc | 100 |