원클릭으로
ai-maestro-plugin
ai-maestro-plugin에는 Emasoft에서 수집한 skills 26개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Drive an agent's HTML dashboard side panel via the frozen aimaestro-panel.sh CLI — push HTML or a live URL, open/close/refresh the panel, check how many dashboard clients are connected, and drain feedback events the panel's HTML posted back. Use when an agent wants to render a status view, a form, or a live page in its own dashboard panel. Trigger with /ama-panel, 'show this in my side panel', 'push this HTML to my panel', 'check if anyone is watching my panel', 'read panel feedback'. CRITICAL gotcha: 'delivered: 0' from open/set means the content was DROPPED, not queued — always check status first when delivery matters. Loaded by ai-maestro-plugin
Drive an agent's own terminal and read its own activity state via the frozen aimaestro-session.sh CLI — send or enqueue an allowlisted slash command (works even while busy/hibernated), type raw text into a live pane, read the 5-state activity, and read/answer a pending permission or AskUserQuestion prompt. Use when an agent must act on itself: arm its janitor heartbeat, answer a pending prompt, check if idle/busy, or queue work for later. Trigger with /ama-session, 'queue a command for when I'm idle', 'answer my pending prompt'. Not for reconfiguring an agent (role/plugin/team) — that is ai-maestro-agents-management. Loaded by ai-maestro-plugin
Search, read, verify, and server-mediated mutate TRDDs via the aimaestro-trdd.sh CLI — the AI Maestro dashboard's authorization-aware view of the design/ corpus. Write verbs (edit / approve / refuse / promote / archive) are STRICT, gated by each TRDD's min-approval-requirement with a hard self-approval ban. Use when server-mirrored state or server-side authorization matters: the dashboard kanban, approving a proposal, confirming an approval is real. Trigger with /ama-trdd-server, 'approve this TRDD', 'search TRDDs on the dashboard'. For local design/ file editing use ama-trdd-find/write/update/transition. Loaded by ai-maestro-plugin
Recall prior knowledge from the markdown wiki-memory corpus via memgrep and the janitor's global recall skills. Use before acting on a recurring problem, a design decision, or a repeated alert. Trigger with /memory-search. Loaded by ai-maestro-plugin
Manage AI agent lifecycle via CLI. Use when creating, listing, deleting, configuring, or looking up an agent's consolidated config (launch args, title, role-plugin, teams, GitHub repo, Docker, pending tasks, AID public key). Trigger with /ai-maestro-agents-management. Loaded by ai-maestro-plugin
Use when managing teams or governance titles. Trigger with /team-governance. Loaded by ai-maestro-plugin
Manage team kanban boards and tasks. Use when creating, moving, filtering, getting, or editing tasks. Trigger with /team-kanban. Loaded by ai-maestro-plugin
RETIRED — the AI Maestro docs indexing backend (the docs-search/docs-index shell wrappers) is permanently gone. Use the tldr CLI (tldr-code skill) for codebase docs/signatures instead. Trigger with /docs-search. Loaded by ai-maestro-plugin
RETIRED — the CozoDB graph backend (the graph-describe/graph-find-* shell wrappers) is permanently gone. Use the codegraph MCP tools instead for symbol/caller/callee/impact queries. Trigger with /graph-query. Loaded by ai-maestro-plugin
Persistent markdown planning files for complex tasks. Use when starting multi-step tasks needing 5+ tool calls. Trigger with /planning. Loaded by ai-maestro-plugin
Use when sending or receiving inter-agent messages via AMP. Trigger with /amp-send, /amp-inbox, /amp-read. Loaded by ai-maestro-plugin
Use when an agent needs to clone or create repos, branch, open PRs, list project repos/team members, or report task done/blocked to its orchestrator via AMP. Trigger with /agent-repo-workflow. Loaded by ai-maestro-plugin
Network security model, Tailscale VPN access, IP filtering, and remote device connectivity. Use when configuring remote access or debugging connectivity. Loaded by ai-maestro-plugin
Use when managing agent identity — Ed25519 keys, proof of possession, OAuth token exchange. Trigger with 'create agent identity', 'register with auth server', 'get API token', 'check my registrations'. Loaded by ai-maestro-plugin.
Discover MCP server tools, resources, and prompts without installing plugins. Use when exploring MCP servers or debugging connections. Trigger with /mcp-discovery. Loaded by ai-maestro-plugin
Mutate a project's PRRD rules — add/revise/delete a SILVER rule, or promote/demote between SILVER and GOLDEN. GATED: direct mutation is MANAGER-only (enforced by the script's AID_AUTH check); GOLDEN edits and promote/demote are USER-only; a non-MANAGER agent routes to /ama-prrd-propose instead. Use when a MANAGER (or solo USER) decides to change a SILVER rule. Trigger with /ama-prrd-edit, 'add/revise/delete a project rule', or 'promote rule N to golden'. The WRITE pillar of the AI-Maestro PRRD; proposing is /ama-prrd-propose, reading is /ama-prrd-get.
Move a TRDD between kanban columns (the 14-stage pipeline plus blocked/failed) — enforcing the transition matrix: who may trigger each move, the frontmatter side-effects it requires, and the AMP broadcast it sends. Each move is role-gated (ORCH dispatches, ARCH designs, INTEGRATOR owns the ->complete flip, assignee signals dev->testing, MEMBER is signal-only). Use when advancing a task through the pipeline. Trigger with /ama-trdd-transition, 'move TRDD X to testing', 'dispatch this task', or 'mark it blocked'. Authoring is /ama-trdd-write, editing /ama-trdd-update, rendering /ama-kanban-render.
Render the project's design/spec kanban board as a READ-ONLY view over the TRDD pile (the TRDD files under design/ ARE the board) — the full board, just the RED (blocked) column with priority ranking, one column, grouped by assignee, or as JSON; also drift-check. Allowed for every role. Use when you want to see what work exists and what column each TRDD is in before acting, or to check what's blocked. Trigger with /ama-kanban-render, 'show the kanban', or 'what's blocked'. The board is READ-ONLY here; column moves are done via /ama-trdd-transition.
Batch-approve, refuse, or archive TRDD proposals — move them between the four design/ zones (proposals/ to tasks/ on approve; to refused/ on refuse; to archived/ on complete/cancel/supersede). GATED: only a MANAGER (or solo USER) may approve/refuse/archive; the COS relays but does not approve; list is open to all. Use when a MANAGER drains the proposal queue or archives a finished/cancelled/superseded TRDD. Trigger with /ama-proposal-approvals, 'list pending proposals', or 'approve proposals 4,6'. Column moves within tasks/ are /ama-trdd-transition.
Search a project's PRRD rules by content or metadata — find rules whose text matches a keyword, list all GOLDEN or SILVER rules, find which rules a TRDD cites, find unused rules, or get rule-count stats. Use when an agent asks 'which rule covers X', 'are there rules about credentials/auth/deploys', 'what rules does this TRDD reference', 'which rules are never cited'. Searching is allowed for EVERY role. Trigger with /ama-prrd-find. The SEARCH pillar of the AI-Maestro PRRD; to read one rule by number use /ama-prrd-get, to mutate use /ama-prrd-edit (gated) or /ama-prrd-propose.
Read a PRRD rule by number from a project's design/requirements/PRRD.md. Use when an agent needs the exact text of a project rule it must comply with, wants to cite a rule (PRRD G64.134), list all rules, or bootstrap an empty PRRD. Reading is allowed for EVERY role. Trigger with /ama-prrd-get or 'what does PRRD rule N say', 'cite rule N', 'list the project rules', 'show the PRRD'. The READ pillar of the AI-Maestro PRRD; for searching by content use /ama-prrd-find, to mutate use /ama-prrd-edit (gated) or /ama-prrd-propose.
File a PRRD-change proposal for MANAGER (or USER) review without mutating the PRRD. This is the path EVERY non-MANAGER role uses to request a rule change, and the path for ANY GOLDEN-rule change (which is USER-only). Proposals are non-binding — they queue for approval. Use when an agent thinks a project rule should be added/reworded/removed but lacks the authority to do it directly. Trigger with /ama-prrd-propose or 'propose a rule change', 'suggest revising rule N'. The PROPOSAL pillar of the AI-Maestro PRRD; direct mutation (MANAGER, SILVER) is /ama-prrd-edit, reading is /ama-prrd-get.
Find TRDD task-design documents under design/ — by 8-char id (TRDD-9a8aba94), column, assignee, blocked-by, cited PRRD rule, a SQL-ish --where filter, or free-text; also --validate a TRDD's frontmatter. Read-only, allowed for every role. Use when locating a task spec before working on it, resuming a TRDD from a todo-list id, or auditing the backlog. Trigger with /ama-trdd-find, 'find the TRDD for X', or 'which TRDDs are blocked'. Authoring is /ama-trdd-write, editing /ama-trdd-update, column moves /ama-trdd-transition.
Edit an existing TRDD's body or non-column frontmatter as work proceeds — bump updated:, append implementation-commits/ci-runs/test results, write the STATE block, add review notes or post-mortems, set labels/priority/severity. Only the TRDD's current-owner edits its body; coordination fields (column, assignee) are moved by their owners. Use when recording progress on a task you own — NOT for column moves (/ama-trdd-transition) and NOT for a terminal frozen TRDD. Trigger with /ama-trdd-update, 'update the TRDD', or 'record the commit on TRDD X'. Authoring is /ama-trdd-write, finding /ama-trdd-find.
Author a new TRDD task-design document under design/ with correct v2 frontmatter — uuid + timestamps, the right zone (tasks/ for a Tier-0 task written directly as 'planned'; proposals/ for a Tier-1/2/3 task needing approval), and a self-contained body. Allowed for every role (MEMBER via COS). Use when a non-trivial task, feature, or decision must be captured as a tracked spec, or a report's decision becomes a TRDD. Trigger with /ama-trdd-write, 'write a TRDD for X', or 'capture this as a task spec'. Finding is /ama-trdd-find, editing /ama-trdd-update, column moves /ama-trdd-transition.
Debug Claude Code hooks (PreToolUse, PostToolUse, etc.). Use when hooks aren't firing or produce wrong output. Trigger with /debug-hooks. Loaded by ai-maestro-plugin