Kometa defaults

Kometa Defaults

Own built-in default: usage.

Goal

• Generate correct default: calls in the right file-reference block.
• Distinguish per-key toggles from file-wide overrides.
• Explain when defaults stop being enough and a custom file is needed.

Output Contract

Always return:

1. YAML snippet in the file where it belongs
2. 2-5 short bullets explaining inheritance and overrides
3. Caveats for file type, supported variables, and when to switch to a custom skill

File Boundary

Defaults belong in:

• collection_files:
• overlay_files:
• root playlist_files:

Defaults do not belong in:

• standalone collections: files
• standalone overlays: files
• standalone playlists: files
• arbitrary custom files unless the file itself defines templates for that behavior

Hard Rules

• use default: only in file-reference lists
• template_variables here are defaults-specific; custom files do not inherit this behavior automatically
• per-key variables such as use_top or visible_library_top target one generated key
• file-wide variables such as collection_order or schedule affect the whole default call when the default supports them
• if the user wants structure the default cannot express, route to the custom collection, overlay, or playlist skill

Decision Rules

Use this skill when:

• the user wants a built-in chart, genre, award, seasonal, actor, studio, or resolution pack
• the user wants to disable a few generated keys from a built-in default
• the user wants to move a default section, pin a default collection, or schedule a default file
• the user wants the built-in universe/timeline playlist pack

Do not use this skill when:

• the user wants a one-off custom builder query
• the user wants a hand-written overlay body
• the user wants a custom playlist with their own builder choice

Variable Types

Think in three buckets:

• key toggles
  • use_<key>
  • key-specific visibility overrides
• file-wide overrides
  • collection_order
  • schedule
  • libraries
  • radarr_add_missing
• structural/default-pack controls
  • use_separator
  • collection_section
  • data

Collection Defaults

Use collection defaults for:

• actor / director / writer / producer packs
• chart packs like IMDb, Trakt, TMDb, Letterboxd, Tautulli, anime charts
• genre, studio, country, decade, year, seasonal, streaming, awards, and similar built-in packs

Important rules:

• most default collection files use separators
• use_separator: false can be set at library level or per default call
• collection_section changes where that default family sorts in Plex
• data is the usual deep-tuning payload when a default supports richer custom input
• per-key schedule-style overrides often follow schedule_<key>
• do not invent data or append_data shapes without that default's page

Overlay Defaults

Use overlay defaults when:

• the user wants built-in resolution, audio, ratings, status, ribbon, studio, or similar packs

Important rules:

• overlay alignment and color variables are often shared across many overlay defaults
• per-key overlay toggles usually follow use_<key>
• overlapping default packs often expose weight_<key> to force one generated overlay to win
• builder_level belongs inside template_variables when a default overlay should target seasons or episodes
• poster rating defaults often assume matching rating-update operations already exist in config.yml
• originals_only: true on the streaming pack changes the source behavior, so call that out
• network and studio packs do not expose per-network or per-studio toggle lists
• do not invent raw overlays: bodies when the user only asked for a default call
• overlay scheduling happens at the library level with schedule_overlays, not per overlay file

Default Playlists

Use default playlists when:

• the user wants built-in timeline or universe playlists like MCU, Star Trek, Star Wars, Pokémon, or X-Men

Important rules:

• built-in default playlist calls belong under root playlist_files:
• the built-in default playlist assumes Movies and TV Shows unless libraries is overridden
• use_<key> works for enabling or disabling specific built-in playlists

Pushback Rules

Push back and route away when:

• the user asks for a custom collection builder query instead of a built-in pack
• the user wants raw overlay placement logic instead of a built-in overlay call
• the user tries to place defaults inside a standalone collection or overlay file
• the requested tweak is not documented for that default

Embedded Examples

Collection default with per-key and file-wide variables

libraries:
  TV Shows:
    collection_files:
      - default: imdb
        template_variables:
          use_popular: false
          use_lowest: false
          visible_library_top: true
          visible_home_top: true
          visible_shared_top: true
          collection_order: alpha
          schedule: weekly(wednesday)

Overlay default

libraries:
  Movies:
    overlay_files:
      - default: resolution
        template_variables:
          use_edition: false
          horizontal_align: left
          vertical_align: top
          back_color: "#00000000"

Overlay default with per-key priority

libraries:
  Movies:
    overlay_files:
      - default: ribbon
        template_variables:
          weight_IMDB: 200
          use_common: false

Collection default with deeper per-key overrides

libraries:
  Movies:
    collection_files:
      - default: seasonal
        template_variables:
          use_separator: false
          use_independence: false
          schedule_valentine: range(02/10-02/15)

Streaming pack

libraries:
  Movies:
    overlay_files:
      - default: streaming
        template_variables:
          originals_only: true
          use_disney: false
          weight_amazon: 170

Languages pack

libraries:
  Movies:
    overlay_files:
      - default: languages
        template_variables:
          languages:
            - en
            - ja
          use_subtitles: true
          style: square

Default playlist pack

playlist_files:
  - default: playlist
    template_variables:
      libraries: Movies, TV Shows
      use_mcu: true
      use_xmen: false
      radarr_add_missing: true

Local References

Read only what matches the request:

• references/cards/defaults--core.md
• references/cards/defaults--collections-deep.md
• references/cards/defaults--collection-packs.md
• references/cards/defaults--playlist-deep.md
• references/cards/defaults--guide.md
• references/cards/defaults--overlay-packs.md
• references/cards/defaults--ratings-pack.md
• references/cards/defaults--streaming-pack.md
• references/cards/defaults--resolution-pack.md
• references/cards/defaults--languages-pack.md
• references/cards/defaults--network-pack.md
• references/cards/defaults--studio-pack.md
• references/cards/defaults--overlay_variables.md
• references/cards/defaults--overlay_text_variables.md

Use these tiny examples first:

• examples/gold/gold-default-imdb-call.yml
• examples/gold/gold-default-resolution-call.yml
• examples/gold/gold-default-streaming-originals-call.yml
• examples/gold/gold-default-resolution-4k-library-call.yml
• examples/gold/gold-default-languages-subtitles-call.yml
• examples/gold/gold-default-network-episode-white-call.yml
• examples/gold/gold-default-studio-bigger-season-call.yml
• examples/gold/gold-default-ratings-episode-call.yml
• examples/gold/gold-default-ribbon-priority-call.yml
• examples/gold/gold-default-seasonal-data-call.yml
• examples/gold/gold-default-playlist-call.yml

Review Checklist

• is the default: call placed under the right file-reference list?
• are template_variables attached to the default call instead of being buried in the wrong place?
• is the request still a built-in default use case, or has it crossed into custom-file territory?
• if a playlist default is requested, is it placed at root playlist_files:?

Stopping Condition

Finish when:

• the default call is in the right file type
• key-specific versus file-wide behavior is clear
• any unsupported customization is called out instead of guessed