Automated summary
Synchronizes skill metadata to AGENTS.md auto-invoke sections to keep documentation up-to-date.
Strengths
- Automatically updates auto-invoke tables when skills are created or modified.
- Supports multiple scopes (root, ui, api, sdk, mcp_server).
- Provides a dry-run mode to preview changes before applying.
- Uses a simple shell script for easy integration.
Limitations
- Requires each skill to have correctly defined scope and auto_invoke metadata.
- Only works within a specific directory structure (skills/*/SKILL.md).
- Needs manual execution of the sync script.
Use this skill after creating or modifying a skill to update the auto-invoke tables in AGENTS.md.
Avoid this skill if your skills do not need to appear in auto-invoke sections or if you do not use the AGENTS.md structure.
Security analysis
SafeThe skill runs a local shell script that reads skill metadata and updates AGENTS.md files within the project. It does not perform destructive actions, exfiltrate data, or disable safety features. No obfuscated or dangerous commands are present.
No concerns found
How this analysis is madeExamples
I just updated the metadata for the 'example-ui' skill. Run the sync script to update AGENTS.md auto-invoke tables.Run the sync script with --dry-run to show what changes would be made to AGENTS.md files.Sync only the UI scope AGENTS.md by running the sync script with --scope ui.name: skill-sync description: > 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). license: Apache-2.0 metadata: author: Alan version: "1.0" scope: [root] auto_invoke: - "After creating/modifying a skill" - "Regenerate AGENTS.md Auto-invoke tables (sync.sh)" - "Troubleshoot why a skill is missing from AGENTS.md auto-invoke" allowed-tools: Read, Edit, Write, Glob, Grep, Bash
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:
metadata:
author: Alan
version: "1.0"
scope: [ui] # Which AGENTS.md: ui, api, sdk, root
# Option A: single action
auto_invoke: "Creating/modifying components"
# Option B: multiple actions
# auto_invoke:
# - "Creating/modifying components"
# - "Refactoring component folder placement"
Scope Values
| Scope | Updates |
|-------|---------|
| root | AGENTS.md (repo root) |
| ui | ui/AGENTS.md |
| api | api/AGENTS.md |
| sdk | sdk/AGENTS.md |
| mcp_server | mcp_server/AGENTS.md |
Skills can have multiple scopes: scope: [ui, api]
Usage
After Creating/Modifying a Skill
./skills/skill-sync/assets/sync.sh
What It Does
- Reads all
skills/*/SKILL.mdfiles - Extracts
metadata.scopeandmetadata.auto_invoke - Generates Auto-invoke tables for each AGENTS.md
- Updates the
### Auto-invoke Skillssection in each file
Example
Given this skill metadata:
# skills/example-ui/SKILL.md
metadata:
author: Alan
version: "1.0"
scope: [ui]
auto_invoke: "Creating/modifying React components"
The sync script generates in ui/AGENTS.md:
### Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
| Action | Skill |
|--------|-------|
| Creating/modifying React components | `example-ui` |
Commands
# Sync all AGENTS.md files
./skills/skill-sync/assets/sync.sh
# Dry run (show what would change)
./skills/skill-sync/assets/sync.sh --dry-run
# Sync specific scope only
./skills/skill-sync/assets/sync.sh --scope ui
Checklist After Modifying Skills
- [ ] Added
metadata.scopeto new/modified skill - [ ] Added
metadata.auto_invokewith action description - [ ] Ran
./skills/skill-sync/assets/sync.sh - [ ] Verified AGENTS.md files updated correctly
Design-to-Dev Specification Writer
Development
Translate your mockups into technical specifications for developers.
Exports & Barrel Files
Development
Defines conventions for module exports and barrel files: named exports only, no flat wildcards (except `export * as Name` for compound components), sectioned comments, types alongside values, and one export line per source file. Helps maintain consistent, tree-shakeable exports in portal apps using Turbopack or similar bundlers.
Write an Agent Skill
Development
Step-by-step guide to create a structured Agent Skill for coding agents, including directory structure, SKILL.md format, and design principles.