agent-creator - SKILL.md Agent Skill

name: agent-creator description: > Creates and updates AGENTS.md files (repo root and subfolder/component). Provides copy-paste templates and ensures Auto-invoke sections stay syncable. Trigger: When the user asks to create/update an AGENTS.md, wants an AGENTS.md template, or is setting up root vs component agent instructions. license: Apache-2.0 metadata: author: jackonedev version: "1.0.0" scope: [agent_skills] auto_invoke: "Creating AGENTS.md files" allowed-tools: Read, Edit, Write, Glob, Grep, Bash, Task

Agent Creator

Creates AGENTS.md files that teach an agent how to work in a repo or subfolder.

When to Use

Use this skill when you need to:

Create a new root AGENTS.md (repo-wide rules)
Create a component/subfolder AGENTS.md (overrides + local conventions)
Refresh an existing AGENTS.md to reflect current skills/*/SKILL.md
Ensure ### Auto-invoke Skills can be generated by skill-sync

Critical Patterns

1) Pick the right scope

What you’re creating	Where it lives	What it contains
Root agent guide	`<repo>/AGENTS.md` (or this repo: `agent_skills/AGENTS.md`)	Cross-project norms, repo overview, global commands, top-level skills
Component agent guide	`<component>/AGENTS.md`	Only deltas: local commands, tech stack, component-specific skills, overrides

Rule: Component AGENTS.md must not duplicate the full root guide. It should reference the root and then list only what differs.

2) Always include a syncable Auto-invoke section

If the repo uses skills/skill-sync, keep this exact heading and table shape:

Heading: ### Auto-invoke Skills
Intro sentence: “When performing these actions, ALWAYS invoke the corresponding skill FIRST:”
Table header: | Action | Skill |

After adding/modifying skills (or their metadata.scope / metadata.auto_invoke), run:

./skills/skill-sync/assets/sync.sh

3) Don’t invent skills

Only list skills that exist under skills/*/SKILL.md. If a needed skill doesn’t exist, create it via skill-creator.

4) Keep it short and verifiable

Prefer:

A few concrete rules
Copy/paste commands
Links to skills

Avoid:

Long narrative paragraphs
Duplicating SKILL.md content in the AGENTS.md body

Templates

Root template: assets/AGENTS-TEMPLATE.md

Inputs (README-driven)

When generating a root AGENTS.md, prefer to source factual repo details from the target repo’s root README.md.

This repo ships a ready-to-fill README template at agent_skills/README_TEMPLATE.md (intended to be copied/adapted into the target repo). If the target repo’s README differs, extract the same information from equivalent sections.

Minimum data to extract:

1-paragraph project overview
Component table (name, location, tech stack)
Setup/run/lint/format/test commands
Commit/PR conventions (if any)

Suggested Workflow

Choose root vs component AGENTS.md
Read the target repo’s root README.md sections that describe overview, components, and dev commands
Start from the template
Fill in repo-specific commands and component map
Ensure the ### Auto-invoke Skills section exists
Run ./skills/skill-sync/assets/sync.sh
(Optional) Run ./skills/setup.sh --copilot or --all to propagate to assistant configs