suno-curator

Audits and syncs a public Suno music catalog against its blog mirror.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill suno-curator-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: suno-curator
Source: https://github.com/franklinbaldo/skills/tree/main/suno-curator
Command: npx skills add https://github.com/franklinbaldo/skills --skill suno-curator-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about suno-curator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which Suno songs are missing from my blog?▼

Run the bundled audit script with node scripts/audit-catalog.mjs --repo . --format markdown from the blog checkout. It fetches the public Suno profile once, compares clips to posts by sunoId, and lists missingFromBlog entries.

How does the audit handle PT and EN versions of the same song?▼

A PT/EN pair sharing one sunoId is expected and not flagged as a duplicate. Duplicate detection uses the (sunoId, lang) pair, so only two posts in the same language for one clip are reported.

Can the audit run offline without calling the Suno API?▼

Yes. Pass --profile-json <snapshot.json> with a saved profile response to run the full comparison offline, which is useful for reproducible evaluation and for the bundled node --test suite.

Does this skill modify my Suno profile or playlists?▼

No. The skill reads the public Suno catalog only and never publishes, renames, deletes, or edits anything on Suno. All Suno-side changes are written into the final report as recommendations for the account owner.

Why does the audit report title drift for some posts?▼

Title drift compares the PT post title against the Suno clip title after NFC normalization and whitespace trimming. Suno titles often carry incidental trailing spaces, which are ignored, but genuine internal differences are flagged as review findings, never auto-overwritten.

What are the genre rules for music posts?▼

The genre field is a curated filter taxonomy: at most 5 labels, at most 40 characters each, with no colons, semicolons, or commas. The full Suno style prompt belongs verbatim in the sunoStyle field instead.