More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Genre Creator: Genre Documents That Producers Can Use

    1

    Author a complete genre documentation file for a music genre library: researched overview, characteristics, lyric conventions, subgenres, artists, keywords, and reference tracks.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Genre Creator: Genre Documents That Producers Can Use

    Genre Creator: Genre Documents That Producers Can Use

    Example session with this skill installed

    Document darksynth for our genre library. Synthwave already has its own entry — do not duplicate it.

    • Read your context and instructions
    • Compiled the genre creator

    Darksynth — genre document produced with the skill

    Setup: slug darksynth derived; index check shows no existing entry; synthwave already has its own document, so it is referenced, not duplicated.

    Research (verified by search, not memory): origin pinned to the early 2010s, French producers, landmark releases with years verified. No year guessed; anything unverifiable was omitted.

    Document: overview in three paragraphs — origin and pioneers, evolution across the decade, current scene and influence. Characteristics nail the instrumentation (analog-style basses, gated reverb drums) and the tempo band (90–110 BPM, half-time feel). Lyric conventions set the key rule (atmosphere over narrative — sparse, imagistic lines) and density (8 lines/verse at 100 BPM, tied to the tempo band so the number means something). Subgenres differentiated by musical specifics, not adjectives; artists table runs pioneers to current acts with albums in italics; production keywords grouped by theme and checked against the tool — dead keywords dropped. Reference tracks run chronologically from the 2012 pioneers to current acts, each annotated with the specific production element that makes it canonical.

    Integration: index updated (category table, alphabetical list, quick-reference tables) and loudness presets noted. The document is done when a producer can go from reading it to writing a genre-correct prompt without asking a follow-up question. Rubric score: 9/10 — one point held back because one reference track's annotation was refined once during review; the final wording names the production element, not the track's fame.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A genre document is a production tool disguised as an encyclopedia entry: musicians and producers use it to write lyrics and production prompts that actually sound like the genre. This skill builds one from a genre name, with factual accuracy enforced by research, not memory. Before writing, the load-bearing facts are verified by web search — origin year, pioneer artists, landmark albums, BPM ranges — and what cannot be verified is omitted, because a wrong year poisons everything downstream that cites it. The slug is derived, the index is checked so a subgenre with its own entry is referenced instead of duplicated, and one or two existing genre files are read for house style, then closed.

    The document spine runs in order, each section feeding the next: a three-paragraph overview, six-field characteristics, six-field lyric conventions (including the key rule and the production-critical density/pacing), a 6–12 row subgenre table, a 10–20 row artist table, grouped production keywords containing only terms the tool understands, and 10–15 reference tracks with chronological spread and annotations naming what each track teaches. Integration updates the index and loudness presets. A worked example documents darksynth end to end, with a scoring rubric gating delivery at 8/10.

    • It cannot verify a fact the research cannot settle; unverifiable facts are omitted, not guessed.
    • It does not duplicate a subgenre that already has its own entry — it references it.
    • It covers the document and the index; it does not write lyrics or production prompts itself — it makes them possible.
    • Production keywords must be verified against the current tool; terms change meaning over time.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Because a wrong year in a genre doc poisons everything downstream that cites it — lyrics, prompts, and other documents that trust this one. An omitted fact is a gap a producer can see; a guessed fact is a lie a producer cannot.

    Because synthwave already has its own document. Duplicating it creates two copies that drift apart, and the drift is what the next producer trips over. Reference it; let one document own each genre.

    The annotation: what the listener should hear in it that teaches them the genre — concrete musical elements, historical significance. A famous track that is famous for other reasons is not a reference track, whatever its fame.

    New in Writing & Content