Sponsored by

Find leads on Reddit on auto pilot

Topic: mcp

13,395 skills in this topic.

maestro:plan-review-loop Deep-review any plan (maestro, Codex, Claude Code plan mode, or plain markdown) using iterative subagent review loops with BMAD-inspired adversarial edge-case discovery. Spawns reviewer subagents that find issues using pre-mortem, inversion, and red-team techniques, auto-fixes them with structured fix strategies, and re-reviews until the plan passes with zero actionable issues. Use when the user says 'review the plan', 'deep review', 'check the plan thoroughly', 'review loop', 'validate before approving', or wants rigorous plan validation before execution. Also use proactively before plan-approve when the plan is complex or high-risk.
ReinaMacCredy/maestro 26
maestro:brainstorming Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
ReinaMacCredy/maestro 26
maestro-v2-migration Guide for working with maestroCLI's v2 architecture. Covers the context-to-memory rename, 4-state task model, plain file backend, pre-agent hooks, research phase, and memory promotion. Use when touching v2 code, encountering legacy patterns (e.g. 'context' instead of 'memory', old task states), adding new v2 features, or debugging v2 behavior. Also use when you see imports from adapters/fs/context, references to 'contextAdapter', or task states that don't match the 4-state model.
ReinaMacCredy/maestro 26
maestro-skill-author Create, update, or debug maestro built-in skills. Covers SKILL.md frontmatter, reference directory structure, step-file architecture, build-time embedding, naming conventions, alias management, and registry validation. Use when creating a new maestro built-in skill, modifying an existing SKILL.md, adding reference files, debugging skill loading failures, updating the skills registry, or working on the skills full port. Also use when frontmatter validation fails, skills don't appear in skill-list, or reference files fail to load.
ReinaMacCredy/maestro 26
maestro-pipeline-test Run a full end-to-end smoke test of all maestro CLI commands in a single session. Use this skill when testing the maestro pipeline, verifying tool installation, validating a maestro setup, or checking that all tool groups work (feature, plan, task, memory, meta, graph, handoff, search). Trigger on "test maestro", "smoke test", "pipeline test", "verify all tools", "run pipeline test", or whenever the user wants to confirm maestro is functioning correctly -- even if they just say "does it work?" in a maestro context.
ReinaMacCredy/maestro 26
maestro-dev Development workflow for maestroCLI itself. Encodes the hexagonal architecture pattern (port -> adapter -> use-case -> command -> MCP tool -> test) and project-specific conventions. Use when implementing new maestro features, adding CLI commands, extending the MCP server, creating new adapters, modifying ports, writing use-cases, or debugging maestro's own code. Also use when you need to understand how maestro's layers connect or where to put new code.
ReinaMacCredy/maestro 26
cli-for-agents Designs or reviews CLIs so coding agents can run them reliably: non-interactive flags, layered --help with examples, stdin/pipelines, fast actionable errors, idempotency, dry-run, and predictable structure. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, or automation-friendly CLIs.
ReinaMacCredy/maestro 26
maestro:note Capture decisions, constraints, and context to persistent notepad. Priority notes are injected into every session and implementation run.
ReinaMacCredy/maestro 26
push Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
ReinaMacCredy/maestro 26
pull Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
ReinaMacCredy/maestro 26
linear Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
ReinaMacCredy/maestro 26
land Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
ReinaMacCredy/maestro 26
debug Investigate stuck runs and execution failures by tracing Symphony and Codex logs with issue/session identifiers; use when runs stall, retry repeatedly, or fail unexpectedly.
ReinaMacCredy/maestro 26
commit Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
ReinaMacCredy/maestro 26
maestro:symphony-setup Set up Symphony orchestration for any repository. Installs Codex skills, generates a customized WORKFLOW.md, configures Linear integration, and verifies the setup. Works with any tech stack.
ReinaMacCredy/maestro 26
maestro:setup Scaffolds project context (product, tech stack, coding guidelines, product guidelines, workflow) and initializes track registry. Use for first-time project onboarding.
ReinaMacCredy/maestro 26
maestro:review Code review for a track against its spec and plan. Verifies implementation matches requirements, checks code quality and security.
ReinaMacCredy/maestro 26
maestro:new-track Create a new feature/bug track with spec and implementation plan. Interactive interview generates requirements spec, then phased TDD plan. Use when starting work on a new feature, bug fix, or chore.
ReinaMacCredy/maestro 26
maestro:docker Use when working with Docker containers — debugging container failures, writing Dockerfiles, docker-compose for integration tests, image optimization, or deploying containerized applications
ReinaMacCredy/maestro 26
maestro:verification Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
ReinaMacCredy/maestro 26
maestro:tdd Use when implementing any feature or bugfix, before writing implementation code
ReinaMacCredy/maestro 26
maestro:dispatching Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
ReinaMacCredy/maestro 26
pyx Safe Python code execution using pyx CLI. Use when: running Python, executing scripts, testing code. Triggers: pyx, run python, execute code, test script. Default mode: MANIFEST_IO (file-first with manifest output).
Anudorannador/python-executor
agoragentic Capability router for autonomous agents. Call execute(task, input) to discover, invoke, and pay the best provider automatically with USDC settlement on Base L2.
rhein1/agoragentic-integrations 8