skill-sync
skill-sync maintains AGENTS.md auto-invoke sections by reading skill metadata and regenerating action-to-skill mappings. Run the sync script after creating or modifying skills to automatically update all affected AGENTS.md files across your repository scopes.
skill-sync automatically updates AGENTS.md auto-invoke sections when you create or modify skills with metadata changes.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-07-27
skill-sync automatically updates AGENTS.md auto-invoke sections when you create or modify skills with metadata changes. skill-sync maintains AGENTS.md auto-invoke sections by reading skill metadata and regenerating action-to-skill mappings. Run the sync script after creating or modifying skills to automatically update all affected AGENTS.md files across your repository scopes.
Use it when
- skill-sync is an automation tool that maintains AGENTS.md auto-invoke sections by reading skill metadata and regenerating action-to-skill.
- skill-sync lets you configure which scopes your skills apply to and what triggers their auto-invoke behavior.
Verify before relying
Read SKILL.md below before installing (3 files). Open directory: indexed for reading, not audited.
Install
prowler-cloud/prowler/skill-sync · repository language: Python
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I sync skill metadata to AGENTS.md?
skill-sync reads your skill metadata and regenerates the auto-invoke sections in AGENTS.md files across all repository scopes. After creating or modifying skills, run the sync script to automatically update action-to-skill mappings. This ensures AGENTS.md stays current with your skill definitions without manual editing.
What is the skill-sync script and how does it work?
skill-sync is an automation tool that maintains AGENTS.md auto-invoke sections by reading skill metadata and regenerating action-to-skill mappings. The script processes skill definitions across configured scopes and updates all affected AGENTS.md files in your repository, keeping auto-invoke tables synchronized with your current skill inventory.
How do I configure skill metadata scope and auto-invoke triggers?
skill-sync lets you configure which scopes your skills apply to and what triggers their auto-invoke behavior. Set scope and auto-invoke metadata in your skill definitions, then run skill-sync to propagate these settings into the corresponding AGENTS.md auto-invoke sections. This controls how and when skills are automatically invoked.
Why don't my skills appear in AGENTS.md after syncing?
skill-sync may skip skills if their metadata is incomplete, scope is misconfigured, or auto-invoke triggers aren't properly defined. Check that your skill definitions include required metadata fields and that scope settings match your target AGENTS.md files. Run a dry-run preview first to diagnose which skills are being processed.
Can I preview changes before syncing skill metadata?
Yes, skill-sync supports a dry-run mode that shows you exactly which AGENTS.md sections will be updated before making any changes. Run the dry-run preview to verify that all skills are detected correctly and that auto-invoke tables will be regenerated as expected before committing the sync.
How do I automate updates to auto-invoke skill tables across scopes?
skill-sync automates AGENTS.md updates by batch-processing skill metadata across all configured scopes. Define your skill scope and auto-invoke metadata once, then skill-sync regenerates all affected auto-invoke tables in a single run. This eliminates manual updates and keeps your entire repository's skill mappings synchronized.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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
(truncated - see the full file via the links below)
File tree — 3 files
skills/skill-sync/SKILL.md
skills/skill-sync/assets/sync.sh
skills/skill-sync/assets/sync_test.sh
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Sync skill metadata changes to AGENTS.md auto-invoke sections”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
skill-creator helps you build new AI agent skills by establishing when to trigger them, documenting critical patterns, and organizing templates and examples. It enforces naming conventions and frontmatter structure to keep skills discoverable and reusable across projects.
This skill drafts and executes git commits following the conventional-commits standard, enforcing structure with type, scope, and concise descriptions. It analyzes staged changes, presents a formatted message for review, and commits only after explicit user approval.
Prowler-changelog automates changelog management across UI, API, MCP Server, and SDK components using a fragment-based system that prevents merge conflicts on concurrent PRs. Each change gets its own fragment file under `changelog.d/` directories, which compile into versioned `CHANGELOG.md` files at release time. The skill enforces semantic versioning rules, validates fragment format, and requires explicit confirmation before any changelog edits.
Prowler-ui equips you with the component patterns and design principles that power Prowler's cloud security platform. Learn the established conventions for building cohesive user interfaces and maintaining design consistency across the ecosystem. This skill bridges the gap between raw components and production-ready UI architecture.
This skill streamlines pull request reviews for compliance framework updates by validating JSON syntax, checking for duplicate requirement IDs, and ensuring framework metadata completeness. It applies a structured checklist covering file location, changelog fragments, and dashboard patterns to catch issues before merge.
Prowler-docs provides the authoring standards and formatting conventions for creating consistent Prowler documentation. It covers brand voice principles, markdown formatting, SEO best practices, and MDX component usage across feature docs, tutorials, API references, and compliance guides.