Our review
Keeps AGENTS.md Auto-invoke sections synchronized with skill metadata by running a script to regenerate tables.
Strengths
- Automates tedious manual updates to AGENTS.md files
- Supports multiple scopes (root, backend, frontend) and dry-run mode
- Clear mapping between skill actions and auto-invoke triggers
Limitations
- Only works with the specific skill metadata format required
- Requires executing a shell script, not a pure agent action
- Cannot handle complex merge conflicts if multiple agents modify AGENTS.md simultaneously
When you create, modify, or need to troubleshoot auto-invoke sections for skills in the repository.
When manually editing AGENTS.md auto-invoke sections for one-time changes that don't involve skill metadata.
Security analysis
SafeThe skill runs a local bash script that reads skill metadata files and updates AGENTS.md files, performing only safe file operations within the repository without network access or destructive commands.
No concerns found
Examples
I just created a new skill at skills/my-new-skill/SKILL.md with scope [backend] and auto_invoke 'Deploying microservices'. Run the sync script to update AGENTS.md files.Show me what would change in AGENTS.md if I add a skill with scope [root] and auto_invoke 'Running tests' using the sync script in dry-run mode.My skill 'db-migration' has metadata with scope [backend] and auto_invoke set, but it doesn't appear in backend/AGENTS.md auto-invoke table. Run the sync script and help me diagnose why.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: prowler-cloud 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: prowler-cloud
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) |
| backend | backend/AGENTS.md |
| frontend | frontend/AGENTS.md |
Skills can have multiple scopes: scope: [backend, frontend, root]
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/prowler-ui/SKILL.md
metadata:
author: prowler-cloud
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 | `prowler-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
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.