emasoft/amama-label-taxonomy
skills/amama-label-taxonomy/SKILL.md
Use when managing GitHub issue labels or priorities. Trigger with label or triage requests. Loaded by ai-maestro-assistant-manager-agent-main-agent.
data-ai
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add emasoft/ai-maestro-assistant-manager-agent amama-label-taxonomyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 3:56 AM12.2s3 files scanned
SKILL.md
- name:
- amama-label-taxonomy
- description:
- Use when managing GitHub issue labels or priorities. Trigger with label or triage requests. Loaded by ai-maestro-assistant-manager-agent-main-agent.
- version:
- 2.3.2
- compatibility:
- Requires AI Maestro installed.
- context:
- fork
- agent:
- amama-assistant-manager-main-agent
- user-invocable:
- false
AMAMA Label Taxonomy
Overview
Label taxonomy for AMAMA. Manages priority labels, status labels, and translates label states into user messages.
Prerequisites
- GitHub CLI (
gh) available - Repo with GitHub issue tracking enabled
- AMAMA role context (user communication, role routing)
Instructions
- Analyze request -- determine priority (
priority:critical|high|normal|low) and type (type:bug|feature|...) - Create issue with labels:
status:backlog,priority:*,type:* - Monitor status changes from other agents; translate to user messages
- Update priorities when user expresses urgency changes
- Set blocked (as a flag) when user requests pause
- Facilitate review when AMIA escalates
- Report status by querying issues with relevant labels
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.
Checklist
Copy this checklist and track your progress:
- [ ] Identify priority and type from user request
- [ ] Create issue with correct labels
- [ ] Confirm creation to user
- [ ] Monitor for status changes from other agents
- [ ] Translate label changes into user-friendly updates
- [ ] Update priority or blocked status as needed
Output
| 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 Handling
| 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 |
Examples
Example: User reports urgent bug
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."
Example: Priority change
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.
Resources
- label-tables: Priority Labels, Kanban Columns (Canonical 5-Status Model), Status Labels AMAMA Updates, Labels AMAMA Monitors, Labels AMAMA Never Sets, AMAMA's Approval Authority
- commands-and-patterns: Label Commands, User Communication Patterns, Full Examples
Related Skills
emasoft/amama-user-communication
data-ai
VerifiedTrustedCommunity
Use when communicating with users for clarification, presenting options, requesting approval, or reporting completion. Trigger with user requests or communication needs. Loaded by ai-maestro-assistant-manager-agent-main-agent.
SKILL.mdUpdated Apr 26, 2026
emasoft/amama-status-reporting
development
VerifiedTrustedCommunity
Use when generating status reports. Queries AI Maestro APIs (sessions, agents, teams, tasks) for live data. Trigger with status report requests.
SKILL.mdUpdated Apr 26, 2026
emasoft/amama-session-memory
testing
VerifiedTrustedCommunity
Use when restoring user context, tracking decisions, or managing availability states. Trigger with session start or preference changes. Loaded by ai-maestro-assistant-manager-agent-main-agent
SKILL.mdUpdated Apr 26, 2026
emasoft/amama-role-routing
testing
VerifiedTrustedCommunity
Use when routing user requests to specialist agents. Trigger with work delegation needs. Loaded by ai-maestro-assistant-manager-agent-main-agent
SKILL.mdUpdated Apr 26, 2026