skill-sync
- Repo stars 13,864
- Author repo prowler
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) |
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
./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
- Fluxly category
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Author / version / license
- @prowler-cloud · no license declared
- Fluxly token estimate
- Lean
- Fluxly setup estimate
- Plug-and-play
- External API key
- No requirement detected
- Detected OS requirements
- Unspecified
- Runtime requirements
- Unspecified
- Detected file/system behavior
-
- Read-only
- Write / modify
- Detected network behavior
- Local-only
- Install commands
- None (reference only)
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
The current SKILL.md does not define a fixed output example. 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.
Each skill that should appear in Auto-invoke sections needs these fields in metadata. autoinvoke can be either a single string or a list of actions:
Scope · Updates root · AGENTS.md (repo root) ui · ui/AGENTS.md
Usage
After Creating/Modifying a Skill
Reads all skills//SKILL.md files Extracts metadata.scope and metadata.autoinvoke Generates Auto-invoke tables for each AGENTS.md
## 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:
```yaml
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) |
| `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
```bash
./skills/skill-sync/assets/sync.sh
```
### What It Does
1. Reads all `skills/*/SKILL.md` files
2. Extracts `metadata.scope` and `metadata.auto_invoke`
3. Generates Auto-invoke tables for each AGENTS.md
4. Updates the `### Auto-invoke Skills` section in each file
---
## Example
Given this skill metadata:
```yaml
# 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`:
```markdown
### Auto-invoke Skills
When performing these actions, ALWAYS invoke the corresponding skill FIRST:
| Action | Skill |
|--------|-------|
… Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.
sections -> Purpose → Required Skill Metadata → Scope Values → Usage → After Creating/Modifying a Skill → What It Does
terms -> or · Keeps AGENTS.md Auto-invoke sections in sync with skill metadata. · Each skill that should appear in Auto-invoke sections needs these fields in metadata. · 1. Reads all skills//SKILL.md files 2.
files/cmd -> metadata · autoinvoke · root · AGENTS.md · ui/AGENTS.md · api/AGENTS.md · sdk · prowler/AGENTS.md
body sha256 -> c6146bf11930
Decide Fit First
Design Intent
How To Use It
Boundaries And Review