musical-dna▌
jwynia/agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Extract descriptive musical characteristics from any artist or band without using their name, building a vocabulary of sonic qualities for AI music generation, music description, or creative recombination. Replace "sounds like [Artist]" with specific, technique-focused descriptions.
Musical DNA Analysis
Purpose
Extract descriptive musical characteristics from any artist or band without using their name, building a vocabulary of sonic qualities for AI music generation, music description, or creative recombination. Replace "sounds like [Artist]" with specific, technique-focused descriptions.
Core Principle
How, not who. Describe techniques, approaches, and sonic qualities rather than referencing artists. This enables:
- Ethical AI music generation
- Precise communication about sound
- Creative recombination of elements
- Genre-independent vocabulary
Quick Reference: Six Dimensions
| Dimension | What to Analyze |
|---|---|
| Rhythmic Foundation | Drums, tempo, bass lines, time signatures |
| Harmonic Architecture | Chords, modes, progressions, melodies |
| Instrumental Techniques | Playing styles, effects, timbres |
| Production Aesthetics | Recording feel, mix, spatial treatment |
| Genre Fusion | Influence integration, innovation points |
| Energy Architecture | Song structure, dynamics, emotional trajectory |
Analysis Process
Step 1: Select Representative Tracks
Choose 3-5 tracks that capture:
- Their most recognizable sound
- Range across their catalog
- Both typical and boundary-pushing examples
Step 2: Systematic Deconstruction
Work through each dimension, focusing on specific techniques and approaches.
Step 3: Extract Prompt-Ready Phrases
Convert observations into standalone descriptive phrases that work without artist context.
Dimension 1: Rhythmic Foundation
Drum Character
- Kit composition: Acoustic, electronic, hybrid, sampled
- Stick technique: Brushes, rods, mallets, standard sticks
- Snare approach: Rim shots, ghost notes, cross-stick, tight vs. ringy
- Kick pattern: Four-on-floor, syncopated, polyrhythmic, sparse
- Hi-hat work: Open/closed patterns, 16th note rides, swung
- Fill style: Busy, minimal, tom-heavy, snare rolls
Time & Tempo
- Time signatures: 4/4, 3/4, 6/8, odd meters (5/4, 7/8)
- Tempo range: Locked BPM or flexible? Fast, mid, slow?
- Subdivision emphasis: 8ths, 16ths, triplets, swung
- Polyrhythmic layering: Multiple meters happening simultaneously
Bass Line DNA
- Technique: Fingered, picked, slapped, synth, upright
- Role: Rhythmic anchor vs. melodic counterpoint
- Range: Sub-bass heavy, mid-focused, full range
- Kick relationship: Locked, complementary, independent
Example Phrases:
- "Driving 8th-note hi-hat over syncopated kick"
- "Slapped bass with muted ghost notes"
- "Swung triplet feel at 95 BPM"
Dimension 2: Harmonic Architecture
Chord Progressions
- Major/minor balance: Predominantly one or mixed?
- Modal inflections: Dorian darkness, Mixolydian brightness
- Chromatic movement: Smooth voice leading, sudden shifts
- Chord density: Triads, 7ths, extended (9ths, 11ths, 13ths)
- Harmonic rhythm: Slow changes (1/bar) or rapid (2+/bar)
Tonal Centers
- Key preferences: Sharp keys, flat keys, open-string friendly
- Modulation: None, gradual, sudden, frequent
- Scale choices: Natural minor, harmonic minor, pentatonic, modes
- Dissonance tolerance: Clean resolution, lingering tension
Melodic Contour
- Range: Wide intervals or narrow
- Movement: Stepwise, leaping, arpeggiated
- Phrase length: Short punchy or long flowing
- Repetition balance: Hooks vs. development
Example Phrases:
- "Minor key with Dorian 6th inflection"
- "Slow harmonic rhythm, one chord per 4 bars"
- "Wide interval leaps in vocal melody"
Dimension 3: Instrumental Techniques
Guitar Approaches
- Pickup selection: Bridge (bright), neck (warm), split
- Tone shaping: Treble-forward, mid-scoop, bass-heavy
- Technique: Fingerpicking, flatpicking, hybrid, percussive
- Tuning: Standard, drop D, open tunings, baritone
Effects Chain
- Distortion type: Overdrive, fuzz, high-gain, clean
- Time-based: Reverb (room, hall, plate), delay (analog, digital, tape)
- Modulation: Chorus, phaser, flanger, tremolo, vibrato
- Pitch: Octave, harmonizer, whammy
- Dynamics: Compression (heavy, light, none)
Other Instruments
- Keys/synth: Analog warmth, digital precision, organ, piano
- Percussion: Auxiliary (tambourine, shaker), world instruments
- Brass/strings: Section vs. solo, dry vs. lush
- Electronics: Samples, loops, glitches, synthesis
Example Phrases:
- "Neck pickup through mild tube overdrive"
- "Slap-back delay with plate reverb"
- "Fingerpicked acoustic with percussive body hits"
Dimension 4: Production Aesthetics
Spatial Characteristics
- Environment feel: Professional studio, live room, bedroom, outdoor
- Reverb treatment: Dry, intimate, expansive, cavernous
- Stereo field: Wide, narrow, mono-compatible
- Depth staging: Everything forward, layered front-to-back
Mix Philosophy
- Prominence hierarchy: Drums-first, vocal-forward, guitar-heavy
- Frequency allocation: Each instrument's spectral home
- Dynamic range: Compressed, dynamic, limiting
- Clarity vs. saturation: Pristine separation vs. glued warmth
Sonic Texture
- Signal path: Clean, saturated, distorted, degraded
- High frequency: Bright, airy, rolled-off, harsh
- Low end: Tight, boomy, sub-heavy, absent
- Midrange: Scooped, present, honky, balanced
Example Phrases:
- "Bedroom recording aesthetic with lo-fi saturation"
- "Drum-forward mix with tight low end"
- "Vintage tape warmth with rolled-off highs"
Dimension 5: Genre Fusion Analysis
Influence Mapping
- Primary foundation: The dominant genre base (60%+)
- Secondary elements: Strong secondary influence (20-30%)
- Tertiary accents: Occasional flavor (10% or less)
Integration Methods
- Temporal placement: Genre X in verses, genre Y in choruses
- Instrumental assignment: Drums from A, guitars from B
- Transition approach: Seamless blend vs. jarring contrast
- Era mixing: Vintage techniques + modern production
Innovation Points
- Boundary crossing: Where conventions are broken
- Novel combinations: Unexpected genre marriages
- Signature fusion: Their unique contribution
Example Phrases:
- "Math rock precision over post-punk foundation"
- "Hip-hop production sensibility applied to folk songwriting"
- "Grunge dynamics with shoegaze texture"
Dimension 6: Energy Architecture
Song Structure
- Intro character: Atmospheric, punchy, fade-in, cold start
- Verse energy: Pulled back, driving, building
- Chorus intensity: Lift, explosion, subtle shift
- Bridge/breakdown: Contrast, climax, reflection
- Outro approach: Fade, stop, resolve, evolve
Dynamic Range
- Intensity curves: Gradual build, sudden shifts, flat line
- Peak placement: Early, middle, late, multiple
- Release patterns: Sudden drop, gradual decay
Emotional Trajectory
- Mood arc: Single state, journey, oscillation
- Tension cycles: Build-release frequency
- Climax character: Cathartic, devastating, transcendent
Example Phrases:
- "Slow build across 4 minutes to explosive final chorus"
- "Sudden dynamic drops creating tension"
- "Verse-chorus contrast via density rather than volume"
Documentation Template
One-Sentence DNA
[Rhythmic approach] + [harmonic character] + [instrumental signature] + [production aesthetic]
Example: "Syncopated post-punk drumming over minor modal progressions, angular clean guitar with chorus effect, dry room recording with bass-forward mix"
Detailed Breakdown
## Rhythmic Signature
- Time feel:
- Drum character:
- Bass approach:
- Syncopation style:
## Harmonic DNA
- Chord tendencies:
- Scale preferences:
- Progression patterns:
## Instrumental Character
- Guitar tone/technique:
- Effects signature:
- Other key instruments:
## Production Fingerprint
- Recording aesthetic:
- Mix characteristics:
- Sonic texture:
## Genre Fusion Map
- Primary foundation:
- Secondary elements:
- Innovation points:
## Energy Architecture
- Typical structure:
- Dynamic range:
- Build patterns:
Extractable Prompt Elements
List 5-10 standalone phrases usable in AI generation:
- "..."
- "..."
Ethical Guidelines
Do
- Combine elements from multiple analyses
- Focus on techniques and approaches
- Build reusable vocabulary
- Create novel fusions
Don't
- Copy complete profiles directly
- Replicate signature riffs/melodies
- Use as "sounds like [Artist]" substitute
- Claim to reproduce specific artists
Anti-Patterns
1. The Name Drop
Pattern: Using artist names as shorthand instead of technique descriptions. "Sounds like Radiohead" instead of describing the actual sonic qualities. Why it fails: Defeats the entire purpose. Artist names are black boxes that convey different things to different people and may produce copyright issues in AI generation. Fix: Never use artist names in final output. For every "sounds like X," unpack what that actually means in terms of rhythm, harmony, production, etc.
2. The Single Dimension
Pattern: Analyzing only one dimension (usually rhythm or production) while ignoring others. Producing incomplete profiles. Why it fails: Musical identity emerges from interaction of all dimensions. A rhythmic profile without harmonic context is useless for generation. Fix: Force yourself through all six dimensions. Even if an artist seems "about the guitar sound," their rhythmic choices matter.
3. The Genre Substitute
Pattern: Describing music by genre labels instead of techniques. "Post-punk" instead of describing what makes it post-punk. Why it fails: Genre labels are contested categories, not techniques. AI systems need concrete instructions, not genre negotiations. Fix: Treat genre labels as starting points requiring unpacking. What rhythmic, harmonic, and production choices define this genre for this artist?
4. The Representative Track Trap
Pattern: Analyzing one famous song and extrapolating to entire catalog. Missing range and evolution. Why it fails: Artists vary. Their most famous song may not be representative. Analysis from one track produces narrow profiles. Fix: Analyze 3-5 tracks from different periods and modes. Look for both constants and variations.
5. The Technical Overdose
Pattern: Including so much technical detail that prompts become unusable. Every possible parameter specified. Why it fails: AI generation systems can't process unlimited context. Overly detailed prompts get truncated or confuse the model. Fix: Distill to 5-10 essential phrases. Prioritize what makes this artist distinct rather than comprehensive.
Integration Points
Inbound:
- From listening to music you want to analyze
Outbound:
- To AI music generation prompts
- To
lyric-diagnosticfor complete song analysis
Complementary:
lyric-diagnostic: Lyrical analysis (words)- This skill: Musical analysis (sounds)
How to use musical-dna on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add musical-dna
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches musical-dna from GitHub repository jwynia/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate musical-dna. Access the skill through slash commands (e.g., /musical-dna) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★27 reviews- ★★★★★Evelyn Gonzalez· Dec 24, 2024
Useful defaults in musical-dna — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Shikha Mishra· Dec 8, 2024
We added musical-dna from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Fatima Desai· Dec 8, 2024
Registry listing for musical-dna matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Nov 27, 2024
Useful defaults in musical-dna — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Yuki Yang· Nov 27, 2024
musical-dna reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Layla Taylor· Nov 15, 2024
We added musical-dna from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Pratham Ware· Oct 18, 2024
Registry listing for musical-dna matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Yuki Martin· Oct 18, 2024
We added musical-dna from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Nikhil Iyer· Oct 6, 2024
musical-dna reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Layla Abebe· Sep 25, 2024
musical-dna has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 27