agentleFS
Pablo-Lozano-GilPablo-Lozano-Gil/battletested-agent-skills/skill-propagator/SKILL.md

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).

The file

Files
SKILL.md

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

ScopeUpdates
rootAGENTS.md (repo root)
uiui/AGENTS.md
apiapi/AGENTS.md
sdk{project-name}/AGENTS.md
mcp_servermcp_server/AGENTS.md
dbdb/AGENTS.md

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


Usage

After Creating/Modifying a Skill

skill-propagator/assets/propagate.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. Generates Auto-invoke tables for the skill folder README.md
  5. Updates the ### Auto-invoke Skills section 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 ui

Checklist After Modifying Skills

  • Added metadata.scope to new/modified skill
  • Added metadata.auto_invoke with action description
  • Ran skill-propagator/assets/propagate.sh
  • Verified AGENTS.md files updated correctly
  • Verified skill folder README.md updated correctly

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.