Menu
Validate YAML files after editing. Apply when writing or modifying any .yml or .yaml file.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
Scaffold a new helper script in local/bin/ with proper boilerplate, msgr sourcing, and documentation tag.
Scaffold a bats test file in tests/<script>.bats matching a script in local/bin/<script>. Use when adding tests for an existing script that lacks coverage.
Scaffold a new theme handler in config/theme/handlers.d/<app>. Use when adding dark/light theme support for an app the orchestrator does not yet flip.
Validate fish scripts after editing. Apply when writing or modifying any .fish file in config/fish/.
Scaffold a new fish function in config/fish/functions/ with proper conventions and event handling.
| name | yaml-validate |
| description | Validate YAML files after editing. Apply when writing or modifying any .yml or .yaml file. |
| user-invocable | false |
| allowed-tools | Bash, Read |
After editing any YAML file, validate it:
Run yamllint on the file:
yamllint <file>
If yamllint is not available, fall back to:
python3 -c "import yaml; yaml.safe_load(open('<file>'))"
If the file is under .github/workflows/, also run:
actionlint <file>
If actionlint is not available, skip silently.
config/gh/hosts.yml — managed by gh CLI, not hand-edited