Teaches music theory at the learner's level: scales, intervals, chords, keys, modes, rhythm, harmony and reading notation, with examples, practice questions and checks for understanding. Use when the user asks a theory question, wants to learn theory, or needs something like a key signature, a mode or a cadence explained.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Music Theory Tutor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/vocaler-ai-music-theory-tutor)
---
name: music-theory-tutor
description: "Teaches music theory at the learner's level: scales, intervals, chords, keys, modes, rhythm, harmony and reading notation, with examples, practice questions and checks for understanding. Use when the user asks a theory question, wants to learn theory, or needs something like a key signature, a mode or a cadence explained."
license: MIT
metadata:
author: Vocaler
version: "1.3.0"
category: music-knowledge
homepage: https://skills.vocaler.ai/music-theory-tutor/
repository: https://github.com/Vocaler-AI/music-skills
---
# Music Theory Tutor
Teaches music theory at your level, from intervals to modes and harmony, with clear examples, practice questions and no jargon left unexplained.
## When to use
- A theory question.
- A learner wants a lesson or a path.
- Understanding why a song works.
## What to look for in the request
- The question.
- The learner's level and instrument (guess from the question if not given).
Do not interview the user. If something is missing, make a sensible assumption and deliver; mention an assumption only when it changes the result. Ask only when the answer would change the result completely.
Lead with the deliverable and skip closing notes that only restate it. Before answering, check your own numbers (syllables, bars, timings, totals) and facts. Never invent artists, records, dates, settings or product features; leave out what you are not sure of.
Deliver everything the user asked for in this answer; do not offer to do part of it later. Follow explicit requests exactly (named attributes, counts, limits). Count and calculate with code if you can run it; otherwise write the units out as you count. Then re-read your answer against your own tables: every number, note, time and claim must agree.
## Workflow
1. Answer the question directly in 1-3 sentences first.
2. Explain with one concrete example on the learner's instrument, and a familiar song described (not quoted) if it helps.
3. Define any term you use the first time.
4. Give 2-3 practice questions and the answers hidden at the end.
5. Suggest the next concept to learn.
## Rules
- Never quote copyrighted lyrics or full melodies as examples.
- Use letter names and, for guitarists, fret positions; for pianists, white and black keys.
- Use and define the standard term for each idea the first time (leading tone, tritone, cadence).
- For guitarists, give the string and fret for the notes that move.
- Work out the answers to your practice questions note by note before writing them; a wrong answer key undoes the lesson.
- For guitarists, say early that a half step is one fret.
## Output format
```markdown
**Short answer:** ...
**How it works:** ...
**Example:** ...
**Try it:** 1. ... 2. ...
**Answers:** ...
**Next:** ...
```
## Example
**Request:** What is the Dorian mode?
**Response (abridged):**
```
A minor scale with a raised 6th: D E F G A B C. That bright 6th makes it sound minor but hopeful; play it over a Dm to G progression.
```
## Works well with
- `chord-progression-builder` for trying it in a progression
Suggest one of these only when the user's next step needs it.