AesopScott

Use when working on the Sub-agent Dispatch harness and you need capability control: Registers new agent types, pluggable planning strategies, and enforced result schemas.

Use when working on the Orchestrator harness and you need capability control: Lets operators swap the "why this next" decision logic (round-robin, risk-first, deadline-first) without touching the orchestrator core.

Use when working on the Trace harness and you need performance control: Writes traces asynchronously so audit logging doesn't block the call path.

Use when working on the Orchestrator harness and you need cost efficiency control: Caps concurrent high-cost reasoning sessions per project and reclaims idle slices, holding total attention spend under a set ceiling.

Use when working on the Latency harness and you need capability control: Adds SLO config and availability probes for new routes.

Use when working on the Provider harness and you need cost efficiency control: Chooses batch over realtime endpoints and compresses payloads where latency allows to reduce vendor cost.

Use when working on the Latency harness and you need cost efficiency control: Trades latency for cheaper batch processing where the task tolerates delay.

Use when working on the Cost harness and you need performance control: Checks budget before dispatch so over-budget work is stopped before it spends.

Build role agents for a root organization or multi-agent corporation. Use when the user wants to create an organizational role such as CEO, CFO, advisor, operator, manager, support lead, data steward, research lead, or functional department voice, and needs to decide role mode, engagement type, authority, implementation form, learning behavior, and whether the role should be advisory, workflow-owned, skill-backed, loop-backed, autonomous, human-in-the-loop, or only a lightweight prompt/persona.

Observe CLI model calls, prompt/input payloads, stdout/stderr, provider-reported usage metadata, and local token estimates across Codex, Claude, DeepSeek, OpenAI, Anthropic, or other AI CLIs. Use when a user needs truthful token visibility, prompt-origin accounting, usage audits, or a harness around model CLI input/output; labels exact provider usage separately from local estimates and blocks claims that cannot be proven.

Observe CLI model calls, prompt/input payloads, stdout/stderr, provider-reported usage metadata, and local token estimates across Codex, Claude, DeepSeek, OpenAI, Anthropic, or other AI CLIs. Use when a user needs truthful token visibility, prompt-origin accounting, usage audits, or a harness around model CLI input/output; labels exact provider usage separately from local estimates and blocks claims that cannot be proven.

Create an agent brief for the MAPS Define phase from an existing role. Use when turning an approved role artifact into an agent brief with goals, users, authorization, scope, non-goals, success criteria, failure criteria, escalation points, risks, and assumptions.

Accounting skill owned by Finn (Finance Director). Runs on: scheduled + emails link. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/accounting/ to use.

Adrian Legal Gate skill owned by Adrian (Legal Director). Runs on: external commitment / contract. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/adrian-legal-gate/ to use.

Agentify skill owned by Tess (Autonomy Engineer). Runs on: autonomy central tool. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/agentify/ to use.

Amara Research Synthesis skill owned by Amara (User Research Director). Runs on: research session completion. Scaffold generated from the Mindshare skills registry; install into ~/.claude/skills/amara-research-synthesis/ to use.

MAPS Phase 3 Build skill that merges base /build-agent, incremental implementation, and test-driven development into one implementation workflow.

Run MAPS Phase 6 Deploy by wrapping /deploy-agent with GitHub Actions environments and Cloudflare deployment automation. Use when Codex needs GitHub to deploy a Cloudflare Pages, Workers, or Agents project; replace manual Wrangler deploys; configure workflow gates, encrypted secrets, smoke tests, release evidence, and rollback records.

Create the MAPS Design phase artifact for an agent or multi-agent system. Use when defining roles, workflows, handoffs, memory, context, guardrails, approvals, escalation paths, test-first proof requirements, and system boundaries from an agent brief.

Run enhanced MAPS M8 Experience Design for websites, SaaS products, dashboards, landing pages, and agent-facing product surfaces. Use when Codex needs to wrap /design-experience with website design references, component-system choices, accessibility primitives, UX/service-design reasoning, responsive layout, page hierarchy, and production-ready UI handoffs.

Run MAPS M8 Experience Design for multi-agent products, or optional A2 Experience Design for single-agent products without an M layer. Use when Codex needs to turn product intent, orchestration behavior, agent behavior, and product constraints into user journeys, surfaces, information architecture, interaction states, accessibility requirements, and system-evaluation handoffs.

Run MAPS Phase 5 Evaluate by wrapping the base Evaluate process with LangSmith, Inspect AI, and Phoenix. Use when Codex needs to create eval suites, trace-backed eval runs, safety/tool-use checks, regression evidence, eval reports, or Phase 7 observability handoff for an equipped agent.

Create the MAPS Evaluate phase artifact for an agent or multi-agent system. Use when designing scenario tests, eval datasets, rubrics, scorecards, regression checks, red-team prompts, safety checks, and release evidence.

Start M0 Project Foundation for a MAPS project or instantiate a MAPS framework/org scaffold. Use when kicking off a new agent, multi-agent project, MAPS+Org project, reusable MAPS framework, or replacing /scaffold by creating project intent, portable path layer settings, notes/source/memory/RAG scaffold, Git and remote readiness, env/secrets scaffold, source inventory, assumptions, decisions, evidence index, RAG-readiness plan, and optional full MAPS repo structure before system shape or APS phase work begins.

Create the MAPS Design phase artifact for an agent or multi-agent system. Use when defining roles, workflows, handoffs, memory, context, guardrails, approvals, escalation paths, test-first proof requirements, and system boundaries from an agent brief.

Run enhanced MAPS M8 Experience Design for websites, SaaS products, dashboards, landing pages, and agent-facing product surfaces. Use when Codex needs to wrap /design-experience with website design references, component-system choices, accessibility primitives, UX/service-design reasoning, responsive layout, page hierarchy, and production-ready UI handoffs.

Run MAPS M8 Experience Design for multi-agent products, or optional A2 Experience Design for single-agent products without an M layer. Use when Codex needs to turn product intent, orchestration behavior, agent behavior, and product constraints into user journeys, surfaces, information architecture, interaction states, accessibility requirements, and system-evaluation handoffs.

Create the MAPS Evaluate phase artifact for an agent or multi-agent system. Use when designing scenario tests, eval datasets, rubrics, scorecards, regression checks, red-team prompts, safety checks, and release evidence.

Start M0 Project Foundation for a MAPS project. Use when kicking off a new agent or multi-agent project, creating the project intent, notes scaffold, Git and remote readiness, env/secrets scaffold, source inventory, assumptions, decisions, evidence index, and RAG-readiness plan before system shape or APS phase work begins.

Create the MAPS Phase 00 Alignment artifact. Use when agreeing on lifecycle phase names, phase order, scope, scaffolding, repo structure, curriculum structure, naming decisions, templates, catalogs, and where future work belongs before defining or building agents.

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

Search the skills.sh community registry and install a skill globally. Use this when the user wants to find, discover, or install a community skill — e.g. "find me a skill for X", "is there a skill that does Y?", "install a skill for Z", "search for a skill to help me with X". Always use this skill rather than building from scratch when the user wants to find existing community skills.

Copy active Advanced AI Concepts Meetup events from one city group to another through the approved Meetup API automation. Use when Scott invokes /copy-meetup-events, asks to copy/sync/replicate Meetup events, or wants Colorado Springs events copied to another Advanced AI Concepts city group without duplicates.

Copy the Advanced AI Concepts Meetup group into another city through the approved Meetup API automation. Use when Scott invokes /copy-meetup-group, asks to copy/replicate/clone the Meetup group into a city, or asks to create a new Advanced AI Concepts city group with the same description and topics as the source group.

Use when setting up, refreshing, debugging, or explaining Obsidianify for Codex or Claude sessions. Reads Obsidian vaults, ranks graph memory by project proximity, creates session context packets, and records valuable completed turn outcomes into typed Obsidian session notes.