Skill Sync

Keep AGENTS.md files in sync with skill metadata automatically

✨ The solution you've been looking for

Verified

Tested and verified by our team

12565 Stars

Syncs skill metadata to AGENTS.md Auto-invoke sections. Trigger: When updating skill metadata (metadata.scope/metadata.auto_invoke), regenerating Auto-invoke tables, or running ./skills/skill-sync/assets/sync.sh (including --dry-run/--scope).

automation sync metadata agents skills documentation devtools maintenance

Repository

See It In Action

Interactive preview & real-world examples

Live Demo

AI Conversation Simulator

See how users interact with this skill

User Prompt

I just created a new skill for UI components. Can you sync the AGENTS.md files?

Skill Processing

Analyzing request...

Agent Response

AGENTS.md files are updated with the new skill's auto-invoke actions and scope mappings

Quick Start (3 Steps)

Get up and running in minutes

Install

claude-code skill install skill-sync

claude-code skill install skill-sync

Config

First Trigger

@skill-sync help

Commands

Command	Description	Required Args
@skill-sync after-creating-a-new-skill	Automatically update AGENTS.md files to include your new skill in the auto-invoke tables	None
@skill-sync troubleshooting-missing-skills	Diagnose why a skill isn't appearing in AGENTS.md auto-invoke sections	None
@skill-sync bulk-documentation-updates	Update all AGENTS.md files after modifying multiple skills' metadata	None

Typical Use Cases

After Creating a New Skill

Automatically update AGENTS.md files to include your new skill in the auto-invoke tables

Troubleshooting Missing Skills

Diagnose why a skill isn't appearing in AGENTS.md auto-invoke sections

Bulk Documentation Updates

Update all AGENTS.md files after modifying multiple skills' metadata

Overview

Purpose

Keeps AGENTS.md Auto-invoke sections in sync with skill metadata. When you create or modify a skill, run the sync script to automatically update all affected AGENTS.md files.

Required Skill Metadata

Each skill that should appear in Auto-invoke sections needs these fields in metadata.

auto_invoke can be either a single string or a list of actions:

 1metadata:
 2  author: prowler-cloud
 3  version: "1.0"
 4  scope: [ui]                                    # Which AGENTS.md: ui, api, sdk, root
 5
 6  # Option A: single action
 7  auto_invoke: "Creating/modifying components"
 8
 9  # Option B: multiple actions
10  # auto_invoke:
11  #   - "Creating/modifying components"
12  #   - "Refactoring component folder placement"

Scope Values

Scope	Updates
`root`	`AGENTS.md` (repo root)
`ui`	`ui/AGENTS.md`
`api`	`api/AGENTS.md`
`sdk`	`prowler/AGENTS.md`
`mcp_server`	`mcp_server/AGENTS.md`

Skills can have multiple scopes: scope: [ui, api]

Usage

After Creating/Modifying a Skill

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

What It Does

Reads all skills/*/SKILL.md files
Extracts metadata.scope and metadata.auto_invoke
Generates Auto-invoke tables for each AGENTS.md
Updates the ### Auto-invoke Skills section in each file

Example

Given this skill metadata:

1# skills/prowler-ui/SKILL.md
2metadata:
3  author: prowler-cloud
4  version: "1.0"
5  scope: [ui]
6  auto_invoke: "Creating/modifying React components"

The sync script generates in ui/AGENTS.md:

1### Auto-invoke Skills
2
3When performing these actions, ALWAYS invoke the corresponding skill FIRST:
4
5| Action | Skill |
6|--------|-------|
7| Creating/modifying React components | `prowler-ui` |

Commands

1# Sync all AGENTS.md files
2./skills/skill-sync/assets/sync.sh
3
4# Dry run (show what would change)
5./skills/skill-sync/assets/sync.sh --dry-run
6
7# Sync specific scope only
8./skills/skill-sync/assets/sync.sh --scope ui