mcpbeat Sign in

Genre Creator Skill for Claude

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.

1k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
399
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/bitwize-music-studio/claude-ai-music-skills --skill genre-creator

The instruction itself

6 sections, as written by the author

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.md exists → abort, inform user
  • Check INDEX.md: Read genres/INDEX.md to 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 with target_lufs, cut_highmid, cut_highs values 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 Name section under ## Genre Presets with LUFS target, dynamics, EQ focus, MCP command, and characteristics.

10. 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 Dive link 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.

Other skills for the same job

different authors, same section of the catalogue
Canvas Design
by anthropics
vendor ×13

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

1388k tokens
Algorithmic Art
by anthropics
vendor ×10

Creating 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. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

15k tokens scripts
Image Enhancer
by frostant
×6

Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.

635 tokens
Video Downloader
by CommandCodeAI
×4

Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.

671 tokens
Histolab
by christophacham
×3

Lightweight WSI tile extraction and preprocessing. Use for basic slide processing tissue detection, tile extraction, stain normalization for H&E images. Best for simple pipelines, dataset preparation, quick tile-based analysis. For advanced spatial proteomics, multiplexed imaging, or deep learning pipelines use pathml.

18k tokens
Omero Integration
by christophacham
×3

Microscopy data management platform. Access images via Python, retrieve datasets, analyze pixels, manage ROIs/annotations, batch processing, for high-content screening and microscopy workflows.

32k tokens
Pydicom
by christophacham
×3

Python library for working with DICOM (Digital Imaging and Communications in Medicine) files. Use this skill when reading, writing, or modifying medical imaging data in DICOM format, extracting pixel data from medical images (CT, MRI, X-ray, ultrasound), anonymizing DICOM files, working with DICOM metadata and tags, converting DICOM images to other formats, handling compressed DICOM data, or processing medical imaging datasets. Applies to tasks involving medical image analysis, PACS systems, radiology workflows, and healthcare imaging applications.

13k tokens scripts
Transformers
by christophacham
×3

This skill should be used when working with pre-trained transformer models for natural language processing, computer vision, audio, or multimodal tasks. Use for text generation, classification, question answering, translation, summarization, image classification, object detection, speech recognition, and fine-tuning models on custom datasets.

13k tokens

How to use it

Copy the folder

Take bitwize-music-studio/genre-creator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.