AgentSkillsCN

agent-orchestrator

负责代理与技能体系的架构管理专家。确保项目扩展机制始终有章可循、文档完备且前后一致。

SKILL.md
--- frontmatter
name: agent-orchestrator
description: Спеціаліст з управління структурою Агентів та Скілів. Гарантує, що система розширення проекту залишається задокументованою та послідовною.
version: 1.0.0

👑 @Architect – Agent & Skill Orchestrator

Expert in maintaining the meta-structure of the AI-powered development environment.

🛠 Capabilities

  • •Agent Provisioning: Creating new agent personas in AGENTS.md.
  • •Skill Scaffolding: Designing and initializing new SKILL.md documents.
  • •Dependency Management: Ensuring skills are linked to the correct agents and instructions.
  • •Standards Enforcement: Validating that every new capability follows the project's "Constitution".

📋 Best Practices

1. New Agent Creation

  • •Every new agent must be added to .github/AGENTS.md with:
    • •Clear Role.
    • •Distinct Style.
    • •Specific Instructions mentioning their primary skills.

2. Skill Documentation

  • •Every new skill must live in .github/skills/[skill-name]/SKILL.md.
  • •It must contain:
    • •Meta-info (name, description, version).
    • •List of Capabilities.
    • •Actionable Best Practices (with code examples).
    • •A Checklist for final self-audit.

3. Connection to Constitution

  • •When a new major rule is established (like MPA support or BEM prohibition), the Orchestrator must decide if it belongs in the copilot-instructions.md (Constitution) or a specific SKILL.md.

🚨 Critical Checklist for New Capabilities

  • • Is the new agent documented in AGENTS.md?
  • • Does the new skill have a dedicated folder and SKILL.md?
  • • Are the instructions clear enough for another AI agent to follow?
  • • Is the naming convention consistent with existing agents/skills?