amcos-label-taxonomy

Standardize AMCOS GitHub label taxonomy for agent assignments and status tracking.

1|Updated Feb 27, 2026

Search Tags:#automation #workflow #label taxonomy #amcos #github labels

Ready to run

npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-label-taxonomy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: amcos-label-taxonomy
Source: https://github.com/Emasoft/ai-maestro-chief-of-staff/tree/main/skills/amcos-label-taxonomy
Command: npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-label-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The label taxonomy standardizes how AMCOS and team roles use GitHub labels, reducing confusion and mislabeling across agents and tasks.

Core Features & Use Cases

Reference mapping for role prefixes (amcos-, eoa-, eia-, eaa-, eama-)
Label consistency across assignment, status, and priority labels
Automation readiness to feed workflows, reporting, and registry synchronization

Quick Start

Consult the taxonomy references when labeling issues to ensure you apply the correct assign:, status:, and role-based prefixes for AMCOS.

Frequently Asked Questions about amcos-label-taxonomy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize GitHub labels for agent assignments and status tracking?▼

Standardize GitHub labels for agent assignments by enforcing consistent label prefixes such as assign:, status:, and priority across issues. This taxonomy reduces confusion by providing a reference mapping for role-based prefixes like amcos-, eoa-, and eia-.

What role-based prefixes does the AMCOS label taxonomy enforce?▼

The AMCOS label taxonomy enforces role-based prefixes including amcos-, eoa-, eia-, eaa-, and eama-. These prefixes standardize label categories for agent assignments and status tracking across per-team GitHub workflows.

How do I apply GitHub label taxonomy to AMCOS team workflows?▼

Apply GitHub label taxonomy to AMCOS workflows by consulting the taxonomy references when labeling issues. Ensure you use the correct assign:, status:, and role-based prefixes to maintain consistency across automation scripts and registries.

Does the AMCOS label taxonomy integrate with workflow automation scripts?▼

Yes, the AMCOS label taxonomy integrates with workflow automation scripts and registries. It provides automation readiness to feed workflows, reporting, and registry synchronization by maintaining label consistency across GitHub issues.

Why do I need a label taxonomy for GitHub issues in AMCOS?▼

A label taxonomy is needed for GitHub issues in AMCOS to reduce mislabeling across agents and tasks. It standardizes how AMCOS and team roles use labels, ensuring consistent assignment and status tracking throughout the workflow.

Can I use custom label prefixes instead of the standard AMCOS taxonomy?▼

The AMCOS label taxonomy enforces specific prefixes like amcos-, eoa-, eia-, eaa-, and eama- for roles. Using these standardized prefixes ensures automation readiness and maintains consistency for registry synchronization across per-team workflows.