What problem does it solve? Keeping a personal blog's music posts in sync with a public Suno catalog is error-prone: clips go missing, metadata drifts, duplicate posts appear, and genre tags violate the site's taxonomy. This Skill audits the drift deterministically and guides safe, read-only-on-Suno curation. ## Core Features & Use Cases - Deterministic catalog audit: A bundled Node.js script fetches the public Suno profile, compares clips to blog posts by sunoId (including tracks[] renditions), and reports missing clips, blog-only IDs, same-language duplicates, metadata gaps, genre violations, and title drift. - Four scoped session modes: Sync run, metadata pass, catalog report, and deep dive keep mechanical maintenance separate from editorial judgment. - Strict safety boundaries: Reads Suno only, writes only to the blog repository, treats API data as untrusted, and records Suno-side changes as recommendations rather than performing them. - Use Case: Run the audit against a checkout of franklinbaldo.github.io to find three public Suno songs missing from the blog, then create flat PT/EN post stubs with source-backed lyrics, duration, and curated genre labels. ## Quick Start Ask the agent to run the Suno catalog audit against the current blog checkout and report which public songs are missing from the blog.