skill-sync

Synchronize AGENTS.md Auto-invoke tables with skill metadata from SKILL.md files.

Updated Jan 7, 2024
One-click install
npx skills add https://github.com/angelriera-dev/angelriera-dev.github.io --skill skill-sync-angelriera-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-sync
Source: https://github.com/angelriera-dev/angelriera-dev.github.io/tree/main/.agents/skills/skill-sync
Command: npx skills add https://github.com/angelriera-dev/angelriera-dev.github.io --skill skill-sync-angelriera-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill ensures AGENTS.md Auto-invoke sections stay synchronized with skill metadata across the repository.

Core Features & Use Cases

  • Reads all SKILL.md files under the skills directory (and .agents/skills) to extract metadata.scope and metadata.auto_invoke.
  • Regenerates per-scope Auto-invoke tables in AGENTS.md, enabling deterministic updates and dry-run validation.
  • Supports multiple scopes and updates the appropriate AGENTS.md files in their respective folders.

Quick Start

Run the sync script to refresh all AGENTS.md Auto-invoke sections

Frequently Asked Questions about skill-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep AGENTS.md auto-invoke tables synchronized with skill metadata?

You can keep AGENTS.md auto-invoke tables synchronized by scanning SKILL.md files to extract metadata.scope and metadata.auto_invoke, then regenerating scope-specific tables deterministically across the repository.

What is a dry-run mode for updating AGENTS.md files?

Dry-run mode validates the synchronization of skill metadata and auto-invoke sections without applying changes, ensuring deterministic updates are safe before writing to the respective scope folders.

How do I extract metadata from SKILL.md YAML frontmatter for agent automation?

Metadata is extracted from SKILL.md YAML frontmatter by reading the metadata.scope and metadata.auto_invoke fields, which are then used to regenerate per-scope auto-invoke tables in AGENTS.md files.

Does skill-sync support multiple scopes when regenerating auto-invoke tables?

Yes, the synchronization supports multiple scopes by reading each skill's defined metadata.scope and updating the appropriate AGENTS.md files in their respective folders to reflect the correct auto-invoke sections.

Why are my AGENTS.md auto-invoke sections out of date after adding new skills?

AGENTS.md auto-invoke sections become outdated when new skills are added without regenerating the tables. Running the sync script scans all SKILL.md files and updates the sections deterministically.