eyelock

Copy processed MP3s and WAVs to NAS storage. Use after Apple Music import or when re-archiving corrected files.

Move processed ZIPs to archive and clean up extraction folders. Use after album processing is complete.

Copy finished MP3s into Apple Music via the auto-import folder and verify the album lands correctly. Use once metadata is finalized and the user wants tracks added to their library — e.g. "add this to Apple Music" or "import these tracks" — even if they don't say "auto-import" explicitly. Also use to diagnose a bad import, e.g. "it showed up as separate tracks instead of one album."

Inspect and update MP3 tags: genre, artist, album, track count, compilation flag. Use when checking or fixing music file metadata — including diagnostic questions like "why do these show up as separate tracks" or "is this folder's metadata consistent," not just explicit tag-editing requests.

End-to-end processing of downloaded music purchases: extract ZIPs, verify metadata, import to Apple Music, archive to NAS, clean up. Use when processing new music downloads.

Reclaim local disk by offloading cloud-backed Apple Music downloads. Audit iCloud status, build an offload playlist that protects your DJ crates and lossless files, then Remove Download. Use when the Mac is low on disk.

Find music release ZIPs in Downloads and classify each as MP3 or WAV by inspecting archive contents (never filenames), matching pairs by release name. Use to see what's available to process — e.g. "what did I just buy" or "what's in my downloads" — even if the user doesn't mention ZIPs or file formats directly.

Check that all media-management paths (Downloads, Apple Music, NAS archive, rekordbox-mcp) are resolvable via env var or config.json, and help the user fix any that are missing. Use when paths seem not configured, when a skill fails to resolve a path, when explicitly asked to set up/configure the plugin, or when asked where its config lives or how path resolution works.

Development workflow for the ynh codebase. Build, test, lint, and format in the right order.

Maintain ynh vendor adapters against current vendor plugin specs. Use when updating adapters, checking spec compliance, or adding new vendor support.

Workflow for compressing prompt and instruction files using LLM-powered techniques, with backup management and restore.

Interactive wizard to create a ynh harness from scratch. Walks through naming, vendor selection, artifact scaffolding, and installation.

Guide graduation from a personal harness to a team setup with delegation. Creates a team harness that delegates to personal harnesses.

Guided walkthrough for using ynd inspect to bootstrap a project's AI skills and agents from its codebase signals.

Project scaffolding skill

Code quality checks

TermQ release procedures. Load when executing any release — stable, beta, or hotfix. Covers versioning, tagging, monitoring, and verification.

TermQ development context. Load at session start and when working on TermQ. Covers project structure, module layout, toolchain rules, worktree workflow, settings architecture, and debugging (TermQLogger categories, log streaming, TERMQ_DEBUG mode).

TermQ code quality gate. Load when running verification checks before committing. Defines the four checks that must all pass with zero errors.

TermQ commit, branch, and PR conventions. Load when creating commits, branches, or pull requests.

TermQ localization workflows. Load when performing any localization task — extracting strings, translating, validating, auditing, or syncing language files.

Sparkle auto-update system for TermQ. Load when working on release workflows, appcast generation, update signing, or debugging update failures. Covers the full update pipeline from signing through delivery.

TermQ Swift code style and patterns. Load when writing or reviewing Swift code. Covers Swift 6 concurrency, error handling, memory management, UI components, and testing.

TermQ logging privacy rules. Load when writing or reviewing any code that logs data. Terminal output is user data — treat it as sensitive regardless of context.

Interactive guide to help you choose the right Claude Code artifact type (command, skill, agent, rule, or plan) based on your needs. Asks targeted questions about purpose, interaction model, tool requirements, and context persistence to recommend the best fit.

Create Toolkit artifacts (agents, commands, skills, rules) with proper structure and frontmatter. Use when users want to contribute a new Toolkit artifact.

Create a new working plan from template with proper frontmatter and structure. Use when users want to start exploring a new idea or architectural decision.

Interactive helper for creating, updating, and managing session handover documents. Guides users through proper context capture for session continuity across stateless AI conversations.

Frictionless setup - detects your context (Toolkit repo, project with Toolkit, or new project) and sets up the right workspace structure automatically.

Validate frontmatter metadata in handovers, plans, and scripts following Toolkit standards. Performs frictionless validation with hard stops for critical issues and suggestions for optional improvements.