engineering-agents-md-curator

Refines repository AGENTS.md files and writes path-specific Copilot instructions files.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-skills --skill engineering-agents-md-curator-scanady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-agents-md-curator
Source: https://github.com/scanady/nexus-skills/tree/main/skills/engineering-agents-md-curator
Command: npx skills add https://github.com/scanady/nexus-skills --skill engineering-agents-md-curator-scanady

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repositories that migrated to AGENTS.md often carry messy files full of stale pointers, duplicate rules, and leftover migration blocks, making agent instructions unreliable and hard to maintain. ## Core Features & Use Cases - AGENTS.md Refinement: Diagnoses migrated blocks, stale pointers, and duplicate rules, then restructures the file into a standard section layout while preserving every project-specific fact verbatim. - Path-Specific Instructions: Writes .github/instructions/*.instructions.md files with correct applyTo glob patterns for language-, framework-, or concern-scoped Copilot rules. - Use Case: After running a migration script, your repo's AGENTS.md contains <!-- migrated:claude-md --> blocks and dead links to .github/copilot-instructions.md. Invoke this Skill to lift the useful content into proper sections, drop stale stubs, and produce a clean, verified file. ## Quick Start Ask the agent to refine this repository's AGENTS.md and clean up the migrated blocks.

Frequently Asked Questions about engineering-agents-md-curator

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

FAQPage Schema
How do I clean up a messy AGENTS.md after migration?▼

Invoke the skill with the repository path and it will diagnose migrated blocks, stale pointers, and duplicate rules, then present a plan before rewriting. Content from `<!-- migrated:... -->` blocks is lifted into standard sections while project-specific facts are preserved verbatim.

How do I write a path-specific Copilot instructions file?▼

Ask for a `.github/instructions/<domain>.instructions.md` file specifying the language, framework, or concern. The skill generates valid `applyTo` glob frontmatter and structured rules, saved under `.github/instructions/` with a 50-200 line target length.

Does this skill modify CLAUDE.md or copilot-instructions.md?▼

No. The `.claude/CLAUDE.md` shim (`@../AGENTS.md`) is only verified, never edited, and `.github/copilot-instructions.md` is never recreated since Copilot reads AGENTS.md natively. The shared-principles marker block also stays byte-identical.

What applyTo glob patterns work for Copilot instructions?▼

Patterns match paths relative to the repository root using standard glob syntax, such as `**/*.ts,**/*.tsx` for TypeScript or `src/components/**/*.tsx` for React components. Multiple patterns are comma-separated without spaces.

When should rules go in AGENTS.md versus .github/instructions/?▼

Repository-wide facts like workflows, project structure, and conventions belong in AGENTS.md, while pattern-scoped rules tied to file globs belong in `.github/instructions/*.instructions.md`. The skill references existing per-file rules instead of duplicating them.