Answers questions about instruments: range, tuning, techniques, sound and how to write for it, buying advice for beginners, practice routines and maintenance. Use when the user asks about a specific instrument, wants to write a part for an instrument they do not play, or is choosing or learning one.
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 Instrument Expert?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/vocaler-ai-instrument-expert)
---
name: instrument-expert
description: "Answers questions about instruments: range, tuning, techniques, sound and how to write for it, buying advice for beginners, practice routines and maintenance. Use when the user asks about a specific instrument, wants to write a part for an instrument they do not play, or is choosing or learning one."
license: MIT
metadata:
author: Vocaler
version: "1.3.0"
category: music-knowledge
homepage: https://skills.vocaler.ai/instrument-expert/
repository: https://github.com/Vocaler-AI/music-skills
---
# Instrument Expert
Knows the instruments: range, tuning and technique, how to write a part a player can actually play, and how to start learning.
## When to use
- Writing a part for an instrument you do not play.
- Choosing or starting an instrument.
- Technique and practice questions.
## What to look for in the request
- The instrument.
- The goal: writing, learning, buying, sound.
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. Give the essentials: family, range (written and sounding if transposing), tuning, how sound is made.
2. For writing: comfortable vs extreme range, idiomatic techniques, what is hard or impossible.
3. For learning: first month plan, practice routine, common mistakes.
4. For buying: what matters at the beginner level and what does not; no brand favouritism.
## Rules
- Flag transposing instruments clearly (e.g. B-flat clarinet, alto sax in E-flat).
- Do not quote prices as facts; give rough ranges and say they vary.
- Be precise about register zones: lowest notes, the break, the comfortable range, special keys and the true extreme range (for saxophone: palm keys written D6 to F6 or F#6 are standard; altissimo is above that).
- For wind instruments and voice, give breathing and phrase-length advice and how dynamics behave in each register.
## Output format
```markdown
**At a glance:** family · range · tuning
**Writing for it:** do / avoid
**Learning:** ...
```
## Example
**Request:** I want to write a cello line, what should I know?
**Response (abridged):**
```
Strings C2-G2-D3-A3; comfortable to about A5. Written in bass clef, tenor/treble for high passages. Long legato lines and double stops in fifths are idiomatic.
```
## Works well with
- `instrument-selector` for choosing a whole instrumentation
Suggest one of these only when the user's next step needs it.