emasoft/amama-user-communication
skills/amama-user-communication/SKILL.md
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.
data-ai
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add emasoft/ai-maestro-assistant-manager-agent amama-user-communicationInstall 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 AM23.4s7 files scanned
SKILL.md
- name:
- amama-user-communication
- description:
- 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.
- version:
- 2.3.2
- compatibility:
- Requires AI Maestro installed.
- context:
- fork
- agent:
- amama-assistant-manager-main-agent
- user-invocable:
- false
User Communication Skill
Overview
Standardized patterns for user communication: clarification, options, approval, completion, blockers, and status updates.
Prerequisites
None required.
Instructions
- Identify communication type (clarification, options, approval, completion, blocker, status)
- Use the appropriate template from reference docs
- Fill all placeholders; include UUIDs, issue numbers, file paths
- Follow Quality Rules: be specific, actionable, honest, concise, traceable
Checklist
Copy this checklist and track your progress:
- [ ] Identify communication type
- [ ] Select and fill appropriate template
- [ ] Review against Quality Rules
- [ ] Include UUIDs and references
- [ ] Send communication
Output
| Type | When to Use | |------|-------------| | Clarification Request | Input incomplete or ambiguous | | Option Presentation | Multiple approaches viable | | Approval Request | Before irreversible operations | | Completion Report | Task finished | | AMCOS Handoff | Routing to specialist agents | | Status Update | During long-running operations |
Error Handling
| Error | Resolution | |-------|------------| | No user response | Wait, then send reminder per escalation timeline | | Ambiguous input | Ask for specific clarification | | Template mismatch | Re-evaluate and use correct template | | AMCOS unresponsive | Follow recovery in amcos-monitoring.md |
Examples
Clarification Request:
I need clarification:
1. Should login support both email and username?
2. What is the session timeout duration?
Completion Report:
Task Complete
Summary: Implemented login endpoint with OAuth2.
Changes: src/auth/login.py, tests/test_login.py (15 tests)
Verify: pytest tests/test_login.py
Next: Proceed with logout endpoint
Resources
Related skills: amama-amcos-coordination, amama-approval-workflows, amama-role-routing
Reference Documents
- references/communication-patterns.md
-
- Clarification Request
-
- Option Presentation
-
- Approval Request
-
- Completion Report
- See Also
-
- references/response-templates.md
- Work Request Acknowledgment
- Status Updates
- Approval Requests
- Completion Reports
- Error Notifications
- references/blocker-notification-templates.md
-
- When to notify the user about blockers
-
- Blocker notification message format
-
- Handling user response to blockers
-
- Timeout handling when user does not respond
-
- Blocker resolution routing
-
- references/workflow-examples.md
- Workflow 1: Routing Implementation Request
- Workflow 2: Granting AMCOS Autonomous Mode
- Workflow 3: Presenting AMCOS Approval Request to User
- See Also
- references/amcos-monitoring.md
- Monitoring Schedule
- Health Check Procedure
- AI Maestro Inbox Check
- Responsiveness Ping (15 Minute Timeout)
- Actions When AMCOS Unresponsive
- See Also
- references/handoff-protocol.md
- Steps
- Design Document Scripts
- See Also
Related Skills
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
emasoft/amama-label-taxonomy
data-ai
VerifiedTrustedCommunity
Use when managing GitHub issue labels or priorities. Trigger with label or triage requests. Loaded by ai-maestro-assistant-manager-agent-main-agent.
SKILL.mdUpdated Apr 26, 2026