| name | agent-file-structure |
| description | Standard structure and key principles for agent definition markdown files. |
Agent File Structure Skill
Purpose
Defines the required structure and best practices for creating agent definition files in .github/agents/*.agent.md.
When to Use
- When creating a new agent definition file
- When reviewing or refactoring existing agent definitions
- When ensuring consistency across the agent ecosystem
Required Structure
All agents must follow this structure:
---
description: Brief, specific description (≤100 chars)
name: Workflow Engineer (coding agent)
model: <model name>
---
# Agent Name Agent
You are the **Agent Name** agent for this project...
## Your Goal
Single, clear goal statement.
## Boundaries
✅ Always Do: ...
⚠️ Ask First: ...
🚫 Never Do: ...
## Context to Read
- Relevant docs with links
## Workflow
Step-by-step numbered approach
## Output
What this agent produces
Key Principles
- Specific over general - "Write unit tests for React components" beats "Help with testing"
- Commands over descriptions - Include exact commands:
npm test, dotnet build
- Examples over explanations - Show real code examples, not abstract descriptions
- - Clear rules prevent mistakes