skill-sync

Sync skill metadata from SKILL.md files to AGENTS.md Auto-invoke tables.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pepeccz/msi-a --skill skill-sync-pepeccz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sync
Source: https://github.com/pepeccz/msi-a/tree/main/skills/skill-sync
Command: npx skills add https://github.com/pepeccz/msi-a --skill skill-sync-pepeccz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Skill metadata changes often require updating Auto-invoke tables across AGENTS.md files to reflect the latest available skills and their trigger actions. This tool ensures those tables stay current by reading skill SKILL.md frontmatter and regenerating the Auto-invoke sections.

Core Features & Use Cases

  • Reads YAML frontmatter from skills/*/SKILL.md to extract fields like name, description, scope, and auto_invoke.
  • Generates and updates Auto-invoke tables in AGENTS.md across repo root and per-scope files.
  • Supports a dry-run mode to preview changes without modifying any files.
  • Guides and enforces consistent skill metadata usage to keep repository automation reliable.

Quick Start

Run the sync script to refresh all AGENTS.md Auto-invoke sections after creating or modifying skills.

Frequently Asked Questions about skill-sync

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

FAQPage Schema
How do I automatically update AGENTS.md Auto-invoke tables when skill metadata changes?

To automatically update AGENTS.md Auto-invoke tables, you can run a sync script that reads YAML frontmatter from skills/*/SKILL.md files and regenerates the action-to-skill tables. It detects new or modified skills and applies updates across root and scope-specific AGENTS.md files.

Can I preview changes to Auto-invoke tables before modifying repository files?

Yes, you can preview changes to Auto-invoke tables before modifying repository files by using the dry-run option. This mode analyzes YAML frontmatter from SKILL.md files and displays the proposed sorted action-to-skill table updates without writing any changes to your AGENTS.md files.

How do you generate scoped Auto-invoke tables from YAML frontmatter in SKILL.md files?

Generating scoped Auto-invoke tables involves reading the metadata.scope field from YAML frontmatter in skills/*/SKILL.md files. The sync tool extracts the name, scope, and auto_invoke fields to build sorted action-to-skill tables, updating both root and per-scope AGENTS.md files accordingly.

What is the best way to keep repository AGENTS.md files synchronized with multiple skill definitions?

The best way to keep repository AGENTS.md files synchronized with multiple skill definitions is an automated metadata sync tool. It enforces consistent skill metadata usage by extracting YAML frontmatter fields and regenerating sorted Auto-invoke tables whenever new or modified skills are detected.

Does skill metadata synchronization require manual edits to root and per-scope AGENTS.md files?

No, skill metadata synchronization does not require manual edits to root and per-scope AGENTS.md files. The sync process reads YAML frontmatter from SKILL.md files and automatically regenerates the Auto-invoke sections across all defined scopes, ensuring repository automation remains reliable.

Why are my AGENTS.md Auto-invoke sections out of sync after adding new skills?

Your AGENTS.md Auto-invoke sections are out of sync because adding new skills requires updating the action-to-skill tables. Running a metadata sync script reads the updated YAML frontmatter from the new SKILL.md files and regenerates the tables to reflect the latest available trigger actions.