genre-creator
Create new genre documentation files for the bitwize-music genre library
Install / Use
npx skills add bitwize-music-studio/claude-ai-music-skills --skill genre-creatorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of genre-creator
genre-creator scores 81/100 on our quality scale, 1051st of 1,194 Content & Media skills we index.
Its SKILL.md is 5.8 KB long, well organised into 14 sections with 1 code example: a solid amount of guidance for an agent.
It has 512 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 21 days ago, so genre-creator is actively maintained.
- It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
genre-creator compared with similar skills
All 4 of these similar skills score higher than genre-creator; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| genre-creator (this skill)by bitwize-music-studio | 81 | 512 | 21d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 46.8k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 22d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 22d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 133.6k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install genre-creator?
- Run
npx skills add bitwize-music-studio/claude-ai-music-skills --skill genre-creator. The install tabs above show the steps for each supported agent. - Which AI agents does genre-creator work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is genre-creator safe to use?
- It is CC0-1.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is genre-creator still maintained?
- The repository was last updated 21 days ago, so genre-creator is actively maintained.
Skill content
View source on GitHubname: genre-creator description: Create new genre documentation files for the bitwize-music genre library. Use when the user wants to add a genre, says "/genre-creator", "neues Genre erstellen", "Genre hinzufuegen", "add genre", or asks to create genre documentation. Takes a genre name as argument. model: sonnet effort: medium argument-hint: <genre-name e.g. "Math Rock" or "Nu-Metal"> allowed-tools:
- Read
- Edit
- Write
- Glob
- WebSearch
Genre Creator
Your Task
Create a new genre README.md for the bitwize-music genre library at ${CLAUDE_PLUGIN_ROOT}/genres/.
Input: $ARGUMENTS (genre name, e.g. "Math Rock", "Nu-Metal", "City Pop")
Workflow
- Derive slug: Lowercase, hyphenated (e.g. "Math Rock" →
math-rock) - Check existence: If
genres/{slug}/README.mdexists → abort, inform user - Check INDEX.md: Read
genres/INDEX.mdto confirm genre is not already listed - Research: Use WebSearch to verify key facts (origin year, pioneer artists, landmark albums) — do NOT guess dates or album names
- Read 1-2 existing genre files for structural reference (e.g.
genres/hip-hop/README.md,genres/phonk/README.md) - Create directory:
genres/{slug}/ - Write README.md following the exact template below
- Update INDEX.md: Add genre to category table, alphabetical list, and all applicable Quick Reference tables (Tempo, Energy, Instrumentation, Vocals, Mood, Era)
- Update mastering presets: Add the new genre to both mastering preset files:
tools/mastering/genre-presets.yaml— Add YAML entry withtarget_lufs,cut_highmid,cut_highsvalues appropriate for the genre. Place in the correct category section or create a new one.skills/mastering-engineer/genre-presets.md— Add a new### Genre Namesection under## Genre Presetswith LUFS target, dynamics, EQ focus, MCP command, and characteristics.
- Do NOT create an
artists/subdirectory — those are created separately when artist deep-dives are written
README.md Template
The file starts directly with # Genre Name — no YAML frontmatter.
ALWAYS use this exact section order:
# {Genre Name}
## Genre Overview
[3 paragraphs — see rules below]
## Characteristics
[6 bullet fields — see rules below]
## Lyric Conventions
[6 bullet fields — see rules below]
## Subgenres & Styles
[Table — see rules below]
## Artists
[Table — see rules below]
## Suno Prompt Keywords
[Code block — see rules below]
## Reference Tracks
[List — see rules below]
Section Rules
## Genre Overview — 3 paragraphs of prose (no bullets):
- P1: Origin, cultural roots, pioneers with names and years
- P2: Evolution across decades, key moments, mainstream breakthrough, regional variants
- P3: Current state, influence on other genres, modern scene
- Style: Encyclopedic but alive. Concrete names, years, albums. No vague claims.
## Characteristics — Bullet list, exactly these 6 fields:
- Instrumentation: Typical instruments, specific models/brands where relevant
- Vocals: Singing style, vocal processing, delivery
- Production: Production techniques, mix aesthetic, sonic character
- Energy/Mood: Mood spectrum, emotional range
- Structure: Song form, typical length, structural quirks
- Tempo: BPM ranges per subgenre, rhythm feel (half-time, swing, straight etc.)
## Lyric Conventions — Bullet list, exactly these 6 fields:
- Default rhyme scheme: Typical scheme with shorthand (AABB, ABAB, XAXA etc.)
- Rhyme quality: Expected quality (multisyllabic, slant, internal etc.)
- Verse structure: Line count, bar structure
- Key rule: THE single most important rule for lyrics in this genre
- Avoid: What NOT to do in this genre
- Density/pacing (Suno): Format:
Default **X lines/verse** at Y BPM. [Context]. Topics: Z/verse.
## Subgenres & Styles — Markdown table:
| Style | Description | Reference Artists | |-------|-------------|-------------------|
- 6-12 subgenres
- Description: 2-3 sentences with musical specifics, not just adjectives
- Reference Artists: 3-4 per subgenre
## Artists — Markdown table:
| Artist | Key Albums | Era | Style Focus | |--------|-----------|-----|-------------|
- 10-20 artists, mix of pioneers + peak-era + current acts
- Albums in italics (Album Name)
- If a deep-dive file exists: append a
Deep Divelink to the artist file in Style Focus
## Suno Prompt Keywords — Fenced code block with comma-separated keywords organized in thematic lines:
- Genre/subgenre labels
- Instrument keywords
- Production keywords
- Mood/atmosphere keywords
- Vocal keywords
- Tempo/rhythm keywords
- Era/aesthetic keywords
- All keywords in English. Only use terms Suno actually understands.
## Reference Tracks — 10-15 entries:
- Format:
- **Artist - "Track Title"** — [Description] - Description: 2-3 sentences. Explain WHAT makes this track a genre reference point. Name concrete musical elements. Explain historical/cultural significance.
- Chronological spread from founding tracks to modern representatives
Important Notes
- Factual accuracy: All years, album names, artist names must be correct. Omit rather than guess. Use WebSearch to verify.
- No AI cliches: Ban these phrases: "tapestry of sound", "sonic landscape", "testament to", "rich tapestry", "sonic journey", "pushing boundaries", "transcends genre". Write direct, concrete prose.
- Suno focus: Lyric Conventions and Suno Keywords are the most important sections — they directly drive music generation quality.
- Subgenre deduplication: If a subgenre already has its own genre directory (e.g. Trap exists as standalone genre), reference it instead of duplicating content.
- Language: English (the entire genre system is in English)
- No empty sections: Every section must have substantive content. If unsure about a section, research first.
Related Skills
siyuan
46.8kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
133.6kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
