skills/skill-sync/SKILL.md
Automatically syncs skill metadata to AGENTS.md Auto-invoke sections. Trigger: Adding new skills, updating skill metadata, or regenerating skill routing tables.
npx skillsauth add agustinalbonico/ai-customizations skill-syncInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically keeps AGENTS.md Skill Routing tables in sync with skill metadata.
When working with multiple skills across projects, manual maintenance of skill routing tables becomes error-prone and tedious. This skill provides automation: run one script and all AGENTS.md files update automatically based on the metadata in each SKILL.md.
Inspired by Prowler's skill-sync system. Each skill file contains metadata that describes:
A sync script reads all SKILL.md files, extracts this metadata, and generates the Skill Routing tables automatically.
Each skill that should appear in Auto-invoke sections needs this in its frontmatter:
---
name: mi-skill
description: What this skill does
metadata:
author: user
version: "1.0"
scope: [root] # Which AGENTS.md to update
auto_invoke:
- "Creating API endpoints"
- "Adding database queries"
---
| Scope | Updates |
|-------|---------|
| root | AGENTS.md (repo root) |
| frontend | First existing path among frontend, web, client, apps/frontend, apps/web, apps/client |
| backend | First existing path among backend, api, server, apps/backend, apps/api, apps/server |
| shared | First existing path among packages/shared, shared, common, packages/common |
| mcp / mcp_server | First existing path among mcp_server, mcp, mcp-server |
| sdk | First existing path among sdk, lib, packages/sdk, packages/lib |
Scopes can be combined: scope: [frontend, backend]. Custom scopes are also supported when a matching directory exists or when .agents/skill-scopes.json defines it.
Example custom scope file:
{
"scopes": {
"admin": "apps/admin",
"mobile": "apps/mobile"
}
}
Single action or list:
# Single
auto_invoke: "Creating React components"
# Multiple
auto_invoke:
- "Creating React components"
- "Adding Tailwind CSS"
.\.agents\skills\skill-sync\assets\sync.ps1
.\.agents\skills\skill-sync\assets\sync.ps1 -DryRun
.\.agents\skills\skill-sync\assets\sync.ps1 -AutoAddMetadata
.\.agents\skills\skill-sync\assets\sync.ps1 -Scope root
.\.agents\skills\skill-sync\assets\sync.ps1 -ProjectRoot C:\ruta\proyecto
If the repo stores skills at skills/ instead of .agents/skills/, run the equivalent skills/skill-sync/assets/sync.ps1 path.
./.agents/skills/skill-sync/assets/sync.sh
./.agents/skills/skill-sync/assets/sync.sh --dry-run
./.agents/skills/skill-sync/assets/sync.sh --auto-add-metadata
./.agents/skills/skill-sync/assets/sync.sh --scope root
If the repo stores skills at skills/ instead of .agents/skills/, run the equivalent skills/skill-sync/assets/sync.sh path.
.agents/skills/*/SKILL.md or skills/*/SKILL.mdmetadata.scope and metadata.auto_invoke from each### Auto-invoke Skills table for each AGENTS.mdCreate/edit SKILL.md
↓
Add metadata.scope + metadata.auto_invoke
↓
Run sync script
↓
AGENTS.md auto-invoke table updates automatically
metadata.scope to skillmetadata.auto_invoke with action descriptionsync.ps1 or sync.sh with -DryRun / --dry-run firstskills/skill-sync/
├── SKILL.md # This file
└── assets/
├── sync.ps1 # Windows PowerShell script
└── sync.sh # macOS/Linux bash script
Pattern inspired by Prowler's skill-sync system.
development
Onboarding automático de proyectos existentes. Escanea el stack tecnológico, detecta componentes (backend, frontend, etc.), busca skills con `npx skills find`, audita seguridad, pide aprobación, instala y rutea a AGENTS.md automáticamente. Trigger: "onboarding del proyecto", "setup del proyecto", "configurar skills", "instalar skills para este proyecto".
tools
Trigger: verificar spec, probar spec, /verificar-spec, e2e visual. Ejecuta specs con Playwright MCP y documenta errores en iteracion 1/errores/.
development
Transforma ideas vagas en definiciones estructuradas de features mediante conversación adaptativa. Usa 5.5 fases (contexto, alcance, funcional, casos borde, técnico, review) para convertir una idea en un PRD de negocio y un Plan técnico con arquitectura. Genera dos documentos: <slug>-prd.md y <slug>-plan.md. El caso de uso es "quiero un..." o "/shape mi idea".
development
Migrar aplicaciones React + NestJS + Postgres desde web a desktop con Tauri en entornos LAN. Usar cuando se necesite planificar, implementar, verificar y preparar release con backend local en 127.0.0.1, base remota por IP fija, sidecar estable y diagnostico de logs de arranque.