Kometa router

Kometa Router

Use this skill first for broad or ambiguous Kometa requests.

Goal

• Identify the target Kometa file type before writing YAML.
• Route to the smallest correct domain skill.
• Prevent the most common mistake: putting valid YAML in the wrong file.

Output contract

Always start with:

Target file type: <config.yml | collection file | overlay file | metadata file | playlist file>
Chosen skill: <skill-name>

Then either:

• produce YAML plus short rationale and caveats, or
• produce a review with sections valid, wrong file type, wrong nesting, missing dependency, and unsafe assumption

Routing table

• review, repair, meta.log, log excerpts, "why failing", unknown errors
  • route to kometa-debug-review
• config.yml
  • top-level connectors like plex, tmdb, trakt, radarr, sonarr
  • root settings, playlist_files
  • library wiring such as collection_files, metadata_files, overlay_files
  • operations, asset_directory, prioritize_assets, report_path, save_report, show_missing, schedule_overlays
  • route to kometa-config-core
• default files and template_variables
  • route to kometa-defaults
• metadata: item edits, match:, season/episode hierarchy
  • route to kometa-metadata-files
• playlists: files and cross-library playlist behavior
  • route to kometa-playlists
• dynamic_collections: blocks
  • route to kometa-dynamic-collections
• custom overlays, poster placement, text or image overlays, queues
  • route to kometa-custom-overlays
• custom collections, builders, filters, templates, collection operations
  • route to kometa-custom-collections

Routing priority

When signals conflict, use this order:

1. log or review request beats generation
2. config.yml wiring beats collection or overlay details
3. default: beats custom collections or overlays
4. explicit top-level keys win:
   • metadata: -> metadata skill
   • playlists: -> playlist skill
   • dynamic_collections: -> dynamic skill
   • overlays: -> overlay skill
   • collections: -> collection skill

Conflict rules

• remove Overlay label, item_label.remove: Overlay, or clean-art repair collections
  • route to kometa-custom-collections, not overlays
• asset_directory, report_path, operations, save_report, or show_missing
  • route to kometa-config-core even if the user mentions overlays or collections
• default overlay or default collection packs with template_variables
  • route to kometa-defaults unless the user explicitly wants raw overlays: or collections:
• "read this log", "meta.log", or pasted error output
  • route to kometa-debug-review even if the underlying fix will be in another file

File boundary rules

• config.yml does not directly hold collections:, overlays:, or metadata: bodies.
• playlist files are referenced at root playlist_files, not under a library.
• collection files may contain collections, dynamic_collections, templates, external_templates.
• overlay files may contain overlays, queues, templates, external_templates.
• metadata files are for metadata: edits, not for collection builders.

Reference loading

Load only what matches the request:

• config: references/cards/config--overview.md, config--file-blocks.md, config--libraries-deep.md
• defaults: references/cards/defaults--core.md plus the pack-specific card if needed
• collections: references/cards/collections--core.md, collections--ordering.md, then only the provider card that matches the source
• overlays: references/cards/files--overlays.md, overlays--core.md, overlays--clean-art.md
• metadata: references/cards/metadata--matching.md, metadata--hierarchy.md
• playlists: references/cards/files--playlists.md, playlists--core.md
• dynamic: references/cards/dynamic--core.md, dynamic--types.md
• templates: references/cards/templates--core.md only when templates or external_templates are involved
• examples: start with one examples/gold/* snippet; use examples/community/curated/* only if the user needs a bigger real-world pattern

Review checklist

When reviewing a snippet:

1. Name the file type it appears to target.
2. Check top-level key validity.
3. Check indentation and list/dictionary shape.
4. Check whether required upstream config exists, such as trakt in config.yml for a Trakt builder.
5. Check whether the answer should be a patch to an existing file or a standalone file.

Example routing

Request: "Build a Movies config with Plex and TMDb and wire in collection files."

• Target file type: config.yml
• Chosen skill: kometa-config-core

Request: "Make a corner ribbon for new releases."

• Target file type: overlay file
• Chosen skill: kometa-custom-overlays

Request: "Why is this collections: block in my config.yml failing?"

• Target file type: config.yml review
• Chosen skill: kometa-debug-review

Stopping condition

Finish when the correct Kometa file type is explicit and the request has been handed to the smallest correct domain skill.