DJ — On-demand journal-track composer

DJ — On-demand journal-track composer

A nested swiss-knife reference for composing one music track per project journal entry. Use this when the user asks for music tied to what they've been working on — "make a track for today's journal", "give me a bossa nova for last week", "the journal mentioned X — try a piece in style Y".

This skill assumes you already have file/bash/skills capabilities. It does not install or configure any media provider — it discovers what is available in your skills catalog and composes via whichever skill matches the user's saved presets.

When to load this skill

• User asks for music tied to a specific project, journal date, or session.
• User asks what genre would fit the project's mood.
• User asks why a previous track sounded the way it did, or wants another take on the same journal entry.

If the request is ambiguous (which journal? which genre? which project?), ask first. Don't guess and burn a generation call.

Preflight — find a usable provider

Before composing, you need to know what providers you can actually reach. Run this the first time the user asks for music in a session, and re-run when the request would use a media path you haven't tried this session.

Step A — enumerate available media-creation skills. Look in your skills catalog for skills tagged media-creation. If your catalog only shows name + description, the description still mentions "media-creation" for tagged skills — grep that.

If you want the canonical list, walk the configured skills paths shown by the skills catalog:

for path in <skills paths from skills(action="info")>; do
  for skill in "$path"/*/SKILL.md; do
    [ -f "$skill" ] || continue
    grep -l -E '(^|, )media-creation(,|]| )' "$skill" 2>/dev/null
  done
done

For each one, the skill itself is the source of truth on what providers it talks to and what env-var key it expects. For MiniMax specifically, load the sibling Swiss Knife minimax-cli reference (../minimax-cli/SKILL.md); it is the canonical provider reference and explains how to scan TUI presets recursively, pick the declared MiniMax slot, export it without printing the key, and match the region.

Step B — cross-check against the user's saved presets. Each media-creation skill expects an API key. Scan ~/.lingtai-tui/presets/**/*.json recursively for each preset's manifest.llm provider + api_key_env (slot name) — the sibling ../minimax-cli/SKILL.md §3 carries the canonical JSONC-safe scanner; reuse it rather than re-implementing the comment-stripper here. The saved keys themselves live in ~/.lingtai-tui/.env; list key names only, never values: