Back to directory

Maestro-Playbooks

A collection of playbooks for the RunMaestro.ai agent orchestrator: saved Auto Run configurations that step an AI agent through a sequence of Markdown task documents until an exit condition is met.

Maestro-Playbooks

Each playbook in this collection is a sequence of Markdown documents with task checkboxes that Maestro processes through AI agents, looping until a defined exit condition, such as all documents being completed or no pending items remaining. The playbooks are grouped into three categories: Assistants playbooks are one-shot setup workflows that install personal-AI frameworks such as a Life Operating System, an iMessage bridge, or an Apple Voice Memos journal onto a fresh agent.

Development playbooks work with Maestro's default agent prompt and cover tasks such as comparing two competing pull requests, raising documentation coverage to a target percentage, making a React site mobile-friendly, finding and fixing performance issues, refactoring to reduce duplication, auditing and remediating security vulnerabilities, and raising test coverage. Research playbooks require a custom agent prompt with user configuration and cover turning a source list into an interlinked knowledge base or building an Obsidian-style knowledge vault.

It is written in Python and released under the AGPL-3.0 license.

More in Agent skills

See all 581
  • Provenance gate

    github.com

    A deterministic authorization gateway that sits between an AI agent and its tools, tracing where each parameter of a side-effect call came from, and blocking the call or asking a human when the source does not check out.

  • A markdown framework of system rules that restates Isaac Asimov's Four Laws of Robotics as a set of prioritized loss calculations for large-language-model agents to follow, published as a discovery file for agents and crawlers to read.

  • Vitruvius

    github.com

    An engineering research agent that runs a discover, read, synthesize, verify and review loop over technical questions, reading sources directly rather than inferring from titles, and publishing its own scored verifier benchmark, weaknesses included.