skill-propagator
Skill3 starsChanged 8 months agoApache-2.0View on GitHub
Propagates skill metadata to AGENTS.md Auto-invoke sections. Trigger: When updating skill metadata (metadata.scope/metadata.auto_invoke), regenerating Auto-invoke tables, or running skill-propagator/assets/propagate.sh (including --dry-run/--scope).
In this repository6 other files it gives its agents.
- aiogramSkill
- conventional-commitsSkill
- python-securitySkill
- skill-creatorSkill
- skill-creatorSkill
- skill-proposerSkill
The file
Files
Skill Propagator
Purpose
Keeps AGENTS.md and README.md Auto-invoke sections in sync with skill metadata. When you create or modify a skill, run the propagate 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: {Author name}
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 | {project-name}/AGENTS.md |
mcp_server | mcp_server/AGENTS.md |
db | db/AGENTS.md |
Skills can have multiple scopes: scope: [ui, api]
Usage
After Creating/Modifying a Skill
skill-propagator/assets/propagate.shWhat It Does
- Reads all
skills/*/SKILL.mdfiles - Extracts
metadata.scopeandmetadata.auto_invoke - Generates Auto-invoke tables for each AGENTS.md
- Generates Auto-invoke tables for the skill folder README.md
- Updates the
### Auto-invoke Skillssection in each file
Example
Given this skill metadata:
# .agent/skills/astro-ui/SKILL.md
metadata:
author: Pablo Lozano
version: "1.0"
scope: [ui]
auto_invoke: "Creating/modifying ASTRO 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 ASTRO components | `astro-ui` |Commands
# Sync all AGENTS.md files
skill-propagator/assets/propagate.sh
# Dry run (show what would change)
skill-propagator/assets/propagate.sh --dry-run
# Sync specific scope only
./.agent/skills/skill-propagator/assets/propagate.sh --scope uiChecklist After Modifying Skills
- Added
metadata.scopeto new/modified skill - Added
metadata.auto_invokewith action description - Ran
skill-propagator/assets/propagate.sh - Verified AGENTS.md files updated correctly
- Verified skill folder README.md updated correctly
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

