Help us improve
Share bugs, ideas, or general feedback.
From ai-maestro-assistant-manager-agent
Use when managing GitHub issue labels or priorities. Trigger with label or triage requests. Loaded by ai-maestro-assistant-manager-agent-main-agent.
npx claudepluginhub emasoft/ai-maestro-assistant-manager-agentHow this skill is triggered — by the user, by Claude, or both
Slash command
/ai-maestro-assistant-manager-agent:amama-label-taxonomyamama-assistant-manager-main-agentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Label taxonomy for AMAMA. Manages priority labels, status labels, and translates label states into user messages.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Label taxonomy for AMAMA. Manages priority labels, status labels, and translates label states into user messages.
gh) availablepriority:critical|high|normal|low) and type (type:bug|feature|...)status:backlog, priority:*, type:*Sets: status:backlog|review, all priority:*.
Monitors only: status:pending|in_progress|review|completed, assign:*.
Never sets: assign:*, review:*, effort:*, component:*.
See label-tables reference for full label tables and approval authority.
Key commands:
# Create issue
gh issue create --title "$TITLE" --body "$BODY" \
--label "status:backlog" --label "priority:$PRI" --label "type:$TYPE"
# Change priority
gh issue edit $NUM --remove-label "priority:normal" --add-label "priority:high"
# Block/unblock
gh issue edit $NUM --add-label "status:blocked"
# Status report
gh issue list --label "status:in-progress" --json number,title,labels
See commands-and-patterns reference for all commands and patterns.
Copy this checklist and track your progress:
| Output Type | Format |
|---|---|
| Issue creation | GitHub issue URL with labels |
| Label update | Confirmation (e.g., "Priority updated to high") |
| Status report | Markdown table of issues and labels |
| Label explanation | Plain text label meaning |
| Error | Resolution |
|---|---|
| Label not found | Create label or fix typo |
| Permission denied | Request repo access from user |
| Issue not found | Verify issue number with user |
| Conflicting labels | Remove old label before adding new |
| API rate limit | Wait and retry, batch operations |
User: "The login page is broken, fix it urgently!"
gh issue create --title "Login page broken" \
--body "User reported urgent login page issue" \
--label "type:bug" --label "priority:critical" --label "status:backlog"
Response: "Created issue #123 (critical). The orchestrator will triage shortly."
User: "Make that password reset high priority too."
gh issue edit 45 --remove-label "priority:normal" --add-label "priority:high"
Response: "Priority updated to high for issue #45."
See commands-and-patterns reference for more examples.