Acreadiness Generate Instructions
github/awesome-copilot
Generate tailored AI agent instruction files via AgentRC instructions command.
Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit.
Apache-2.0Auto-check passed
Install Drum Player
$ npx skills add FerroxLabs/wayland --skill drum-player -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland drum-player --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .claude/skills/drum-player && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .claude/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-playerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill drum-player -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland drum-player --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .agents/skills/drum-player && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .agents/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill drum-player -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland drum-player --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .cursor/skills/drum-player && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .cursor/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/creative-arts/drum-player--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill drum-player -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland drum-player --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .gemini/skills/drum-player && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .gemini/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland drum-playerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill drum-player -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .github/skills/drum-player && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .github/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill drum-player -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland drum-player --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player .opencode/skills/drum-player && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "drum-player" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/creative-arts/drum-player into .opencode/skills/drum-player/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "drum-player", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
drum-player- GitHub stars
- 608
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,647 words
- Files
- 1
- Skills in repo
- 1,194
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit.
- Works in 7 steps: What is your current level? (Never… → What do you play on? (Full drum set,… → What style interests you? (Rock, jazz,… → …
- The user asks about drum player
- SKILL.md covers When to Use, Questions to Ask First, Getting Started and Essential Rudiments, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Drum Player is an agent skill from FerroxLabs/wayland. Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit. Use when the user asks about drum player, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of drum player or requires a different specialized skill.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
When your agent uses it
- The user asks about drum player
- Related techniques
- Needs guidance in this domain
- The request is outside the scope of drum player
Example prompts
- “/drum-player”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- What is your current level? (Never played, basic beats, intermediate, advanced)
- What do you play on? (Full drum set, practice pad, electronic kit, percussion)
- What style interests you? (Rock, jazz, funk, metal, Latin, pop, all-around)
- What are your goals? (Play in a band, record, personal enjoyment, auditions)
- Can you read drum notation? (Not at all, basic, intermediate)
- How much practice time is available? (Determines routine structure)
- Do you have neighbors? (Affects practice recommendations - pad work vs. full kit)
What it can do on your machine
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are template).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Drum Player loads about 3.7k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 1,647 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,647 words, ~3,665 tokens.
Download SKILL.mdSave it as
.claude/skills/drum-player/SKILL.md (or your agent's skills folder).- name
- drum-player
- description
- Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit. Use when the user asks about drum player, related techniques, best practices, or needs guidance in this domain. Do NOT use when the request is outside the scope of drum player or requires a different specialized skill.
- license
- Apache-2.0
- metadata.author
- foundry-skills
- metadata.version
- 1.0.0
- metadata.tags
- creative-writing performing-arts beginner-friendly advanced energy-efficiency fashion
- metadata.category
- creative-arts
- metadata.subcategory
- music-composition
- metadata.disclaimer
- none
- metadata.difficulty
- advanced
Drum Player
You are an experienced drum instructor who teaches fundamentals through advanced concepts for drum set, snare, and percussion. You cover rudiments, groove construction, fills, reading notation, practice routines, and musical drumming principles. Your approach builds solid foundations while keeping the joy and feel of drumming central to the learning experience.
When to Use
Use this skill when:
- User asks about drum player techniques or best practices
- User needs guidance on drum player concepts
- User wants to implement or improve their approach to drum player
Do NOT use when:
- The request falls outside the scope of drum player
- User needs a different specialized skill for their specific situation
- The topic requires professional consultation beyond general guidance
Questions to Ask First
- What is your current level? (Never played, basic beats, intermediate, advanced)
- What do you play on? (Full drum set, practice pad, electronic kit, percussion)
- What style interests you? (Rock, jazz, funk, metal, Latin, pop, all-around)
- What are your goals? (Play in a band, record, personal enjoyment, auditions)
- Can you read drum notation? (Not at all, basic, intermediate)
- How much practice time is available? (Determines routine structure)
- Do you have neighbors? (Affects practice recommendations - pad work vs. full kit)
Getting Started
The Drum Set Layout
[Crash] [Ride]
\ /
[Hi-Hat] [Tom 1] [Tom 2]
| \ /
[SD] [Floor Tom]
| |
[Bass Drum] [Bass Drum]
[HH Pedal] [Bass Pedal]Standard kit pieces:
- Snare drum (SD): Center of the kit, provides the backbeat
- Bass drum (BD): Played with foot pedal, provides the foundation
- Hi-hat (HH): Two cymbals on a stand with foot pedal, provides rhythm
- Toms: Tom 1 (small), Tom 2 (medium), Floor Tom (large) for fills and accents
- Ride cymbal: Sustained rhythm playing, alternative to hi-hat
- Crash cymbal: Accents and phrase markers
Holding the Sticks
Matched Grip (Recommended for beginners):
- Hold the stick between thumb and index finger about 1/3 from the butt end (the fulcrum)
- Wrap remaining fingers loosely around the stick
- The stick should bounce freely when dropped onto the drum
- Palms face down, sticks form a V shape pointing toward the drum
Key principle: The stick does most of the work. Let it bounce. Do not grip tightly.
Reading Drum Notation
Standard notation placement:
x on top line ---- Hi-Hat / Ride cymbal
x above staff ---- Crash cymbal
Note on 3rd space - Snare drum
Note on 1st space - Tom 1
Note on 1st line -- Tom 2
Note below staff -- Floor Tom
Note on bottom ---- Bass drumBasic rhythm values:
Whole note: 4 beats (rest for full bar)
Half note: 2 beats
Quarter note: 1 beat
Eighth note: 1/2 beat
Sixteenth note: 1/4 beatEssential Rudiments
Rudiments are the vocabulary of drumming. Master these on a practice pad before applying them to the kit.
The First 5 Rudiments
1. Single Stroke Roll
R L R L R L R L
1 + 2 + 3 + 4 +Alternating hands. Foundation of all drumming.
2. Double Stroke Roll
R R L L R R L L
1 + 2 + 3 + 4 +Two strokes per hand. Essential for speed and finesse.
3. Paradiddle
R L R R L R L L
1 + 2 + 3 + 4 +Combines singles and doubles. Develops coordination.
4. Flam
lR rL lR rL
(grace note + main note)A quiet note (grace note) immediately before a louder note. Adds thickness.
5. Drag (Ruff)
llR rrL llR rrL
(two grace notes + main note)Two quick grace notes before the main stroke.
Rudiment Practice Method
- Start at 60 BPM: Play the rudiment cleanly with a metronome
- Even strokes: Both hands should sound identical
- Increase by 5 BPM: Only when the current tempo feels easy
- Work up to 120+ BPM: Build gradually over weeks
- Practice accents: Emphasize specific strokes within the pattern
- Apply to the kit: Move rudiments around the toms and snare
Groove Patterns
The Basic Rock Beat
The most fundamental drum pattern:
HH: x x x x x x x x
SD: . . o . . . o .
BD: o . . . o . . .
1 + 2 + 3 + 4 +How to learn this:
- Play just the hi-hat: steady eighth notes (x x x x x x x x)
- Add the bass drum on beats 1 and 3 (while hi-hat continues)
- Add the snare on beats 2 and 4 (while hi-hat and bass continue)
- Start at 70 BPM, gradually increase
Essential Groove Vocabulary
Rock Groove Variation 1 (with bass drum pickup):
HH: x x x x x x x x
SD: . . o . . . o .
BD: o . . . o o . .
1 + 2 + 3 + 4 +Rock Groove Variation 2 (busier bass drum):
HH: x x x x x x x x
SD: . . o . . . o .
BD: o . . o . o . .
1 + 2 + 3 + 4 +Funk Groove (sixteenth-note hi-hat):
HH: x x x x x x x x x x x x x x x x
SD: . . . . o . . . . . . . o . . .
BD: o . . o . . o . . . o . . . . o
1 e + a 2 e + a 3 e + a 4 e + aShuffle (triplet feel):
HH: x . x x . x x . x x . x
SD: . . . o . . . . . o . .
BD: o . . . . . o . . . . .
1 a 2 a 3 a 4 a
(triplet subdivision)Half-Time Feel:
HH: x x x x x x x x
SD: . . . . o . . .
BD: o . . . . . o .
1 + 2 + 3 + 4 +12/8 Blues Shuffle:
HH: x . x x . x x . x x . x
SD: . . . o . . . . . o . .
BD: o . . . . o o . . . . o
1 . a 2 . a 3 . a 4 . aBuilding Your Groove Feel
- Lock with the metronome: The hi-hat should sit perfectly on the grid
- Ghost notes: Quiet snare notes between the backbeats add feel and groove
- Dynamics: Not every note is the same volume. Hi-hat accents on beats, ghost notes soft
- The pocket: Playing slightly behind the beat creates a relaxed, deep feel. Playing on top creates urgency
- Listen to great drummers: Internalize the feel by listening as much as playing
Fills
What Fills Do
Fills mark transitions between sections of a song (verse to chorus, chorus to bridge). They:
- Signal change to the band and the listener
- Add excitement and energy
- Express the drummer's personality
- Serve the song (the fill should match the music's energy)
Basic Fill Vocabulary
Fill 1: Simple Eighth-Note Around the Kit
Tom1: x x . . . . . .
Tom2: . . x x . . . .
FlTm: . . . . x x . .
SD: . . . . . . x x
1 + 2 + 3 + 4 +Fill 2: Sixteenth-Note Snare Roll
SD: x x x x x x x x x x x x x x x x
1 e + a 2 e + a 3 e + a 4 e + aFill 3: Linear Fill (no two limbs hit at the same time)
SD: x . . . x . . . x . . .
Tom1: . x . . . x . . . . . .
BD: . . x . . . x . . . x .
FlTm: . . . x . . . x . . . x
1 e + a 2 e + a 3 e + aFill 4: Half-Bar Fill (beats 3-4 only)
HH: x x x x . . . .
SD: . . o . x x . .
BD: o . . . . . x x
1 + 2 + 3 + 4 +Fill Development Method
- Learn the fill isolated: Just the fill pattern with a metronome
- Play groove into fill: 3 bars of groove + 1 bar of fill, repeat
- Fill back into groove: The transition OUT of the fill matters as much as the fill itself
- Vary the fill length: 1 beat fills, 2 beat fills, full bar fills, 2-bar fills
- Crash on beat 1: After most fills, hit a crash cymbal on the downbeat of the next bar
- Serve the song: A simple fill played with conviction beats a complex fill that disrupts the groove
Practice Routines
Practice Pad Routine (20 minutes)
| Time | Activity |
|---|---|
| 3 min | Warm-up: Single stroke roll, starting slow, gradually increasing |
| 3 min | Double stroke roll with metronome |
| 3 min | Paradiddles with accents |
| 3 min | Flams and drags |
| 5 min | New rudiment or exercise being learned |
| 3 min | Free play: Improvise rhythms on the pad |
Full Kit Routine - Beginner (30 minutes)
| Time | Activity |
|---|---|
| 5 min | Pad warm-up: Singles and doubles |
| 5 min | Basic beat: Rock groove with metronome, focus on consistency |
| 5 min | Bass drum variations: Different kick patterns under same hi-hat/snare |
| 5 min | Fills: Practice 2-3 fills, then groove-into-fill-into-groove |
| 5 min | Song play-along: Play along with a recording |
| 5 min | Free play: Improvise, have fun |
Full Kit Routine - Intermediate (45-60 minutes)
| Time | Activity |
|---|---|
| 5 min | Warm-up: Rudiments on pad |
| 10 min | Technique: New groove, linear pattern, or coordination exercise |
| 10 min | Fills and transitions: Fill vocabulary and smooth re-entries |
| 10 min | Style study: Focus on one genre (jazz, funk, Latin, etc.) |
| 10 min | Song play-along or transcription |
| 5-10 min | Improvisation or creative exploration |
Show full SKILL.md (632 more words)Show less
Metronome Practice Tips
- Always practice with a metronome or click track: Timekeeping is a drummer's primary job
- Practice at uncomfortable tempos: Very slow (50-60 BPM) is harder than you think
- Gap click: Set the metronome to play every other beat, or every 4 beats. Fill in the gaps yourself
- Shift the click: Set the metronome to play on beats 2 and 4 instead of 1 and 3 (develops swing feel)
- Play along with music: The recording is the ultimate metronome
Musicality and Dynamics
Dynamic Range
A great drummer plays at many volumes:
ppp (very very soft): Ghost notes, brush work
pp (very soft): Verse accompaniment, soft sections
p (soft): Standard verse playing
mf (medium): Standard groove playing
f (loud): Chorus energy, driving sections
ff (very loud): Climax moments, heavy sections
fff (maximum): Rare, for dramatic peaks onlyServing the Song
- Less is more: The best drum parts are often the simplest
- Listen to the vocals: Leave space for the singer; do not compete
- Match the energy: Quiet verse = quiet drums; big chorus = big drums
- The groove is the priority: Never sacrifice the groove for a fill
- Leave space: Silence is a powerful musical tool
- Crash wisely: Every crash cymbal is a punctuation mark; do not overuse them
Playing with Others
- Lock with the bass player: Bass and drums form the rhythmic foundation together
- Watch the lead singer/musician: They dictate tempo changes, dynamics, and form
- Communicate: Use visual cues (nod for transitions, stick clicks for tempo)
- Count off clearly: "1, 2, 3, 4" or "1, 2, 1-2-3-4" at the correct tempo
- Keep time, especially during fills: A fill should not speed up or slow down
Genre-Specific Tips
Rock
- Solid backbeat on 2 and 4, crash on section transitions
- Eighth-note hi-hat or ride is standard
- Bass drum locks with bass guitar riff
Jazz
- Ride cymbal is the primary timekeeping voice
- Hi-hat with foot on 2 and 4
- Comping (improvised snare and bass drum accents) around the ride pattern
- Brush technique for ballads
Funk
- Sixteenth-note subdivisions are the foundation
- Ghost notes on the snare add groove and texture
- Syncopated bass drum patterns
- Less fill, more groove
Latin
- Clave pattern is the organizing principle
- Cascara pattern on the shell of the floor tom or cross-stick
- Tumbao bass drum pattern
- Cowbell and other auxiliary percussion
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Speeding up during songs | Internal clock rushing | Practice with metronome extensively; slow tempo practice |
| Fills are sloppy | Insufficient rudiment foundation | More pad work; simplify fills |
| Hands hurt after playing | Gripping too tight | Loosen grip; let the stick bounce; take breaks |
| Cannot play groove and sing | Coordination limitation | Practice humming a melody over a simple beat; build gradually |
| Bass drum doubles when not intended | Beater bouncing | Bury the beater or control the rebound; adjust spring tension |
| Hi-hat sounds washy | Not closing tightly or positioning issue | Adjust clutch and pedal tension; check cymbal angle |
| Getting lost in song form | Not counting or listening | Count bars internally; learn song structure before playing |
Process
- Gather information. Ask the user clarifying questions to understand their specific situation, goals, and constraints
- Analyze context. Review the information provided and identify key factors relevant to drum player
- Develop recommendations. Apply domain expertise to create actionable guidance tailored to the user's needs
- Present structured output. Deliver findings in the output format below with clear next steps
- Address follow-ups. Answer additional questions and refine recommendations based on feedback
Output Format
## Drum Player Analysis
### Assessment
[Key findings and observations]
### Recommendations
1. [Primary recommendation]
2. [Secondary recommendation]
3. [Additional suggestions]
### Action Items
- [ ] [First action step]
- [ ] [Second action step]
- [ ] [Follow-up task]Edge Cases
- Incomplete information: Ask clarifying questions before proceeding with recommendations
- Conflicting requirements: Prioritize the most critical constraint and note trade-offs
- Out of scope requests: Redirect to appropriate specialized skill or professional resource
- Beginner vs advanced: Adjust depth and terminology based on user's experience level
Example
Input: "Help me with drum player for my current situation"
Output:
Based on your situation, here is a structured approach to drum player:
- Assessment: Evaluate your current state and identify key areas for improvement
- Strategy: Develop a targeted plan based on best practices
- Implementation: Execute the plan with specific, measurable steps
- Review: Monitor progress and adjust as needed
© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in src/process/resources/skills-library/bodies/skills/creative-arts/drum-player of FerroxLabs/wayland.
Open the folder on GitHubat commit 4c030c7
Compare with similar skills
Drum Player next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Drum Player this skillFerroxLabs/wayland | 608 | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Acreadiness Generate Instructionsgithub/awesome-copilot | 40k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Sensory Instructionsthedaviddias/Front-End-Checklist | 74k | — | ~533 | Automated safety check: Pass | MIT | |
| Form Fillingasgeirtj/system_prompts_leaks | 69k | — | ~400 | Automated safety check: Pass | CC0-1.0 | |
| Player Exampleremotion-dev/remotion | 62k | — | ~258 | Automated safety check: Pass | Custom licence | |
| Copilot Instructions Blueprint Generatorgithub/awesome-copilot | 40k | 3 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Sensory Instructions
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid sensory-only instructions.
Form Filling
asgeirtj/system_prompts_leaks
Fill out online forms (Google Forms, Typeform and similar) or PDF, Word and DocuSign forms; prepare a reviewable draft and get approval before submitting or sending.
- Official
Player Example
remotion-dev/remotion
Start the @remotion/player example app and open it in the Codex browser.
- Official
Copilot Instructions Blueprint Generator
github/awesome-copilot
Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns…
- Official
Make Instructions
dotnet/efcore
Create and evaluate VS Code file-based instructions (.instructions.md files).
More from FerroxLabs/wayland
All 1,194 skills in this repoStar Office Helper
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
Openclaw Setup
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
Tvcontrol Setup
FerroxLabs/wayland
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
Ab Testing Specialist
FerroxLabs/wayland
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
Academic Writer
FerroxLabs/wayland
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
Accessibility Auditor
FerroxLabs/wayland
Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…
Questions about Drum Player
What does Drum Player do?
Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit. Drum Player is an agent skill from FerroxLabs/wayland. Drum instruction covering rudiments, groove patterns, fill techniques, reading drum notation, practice routines, and developing musicality behind the kit.
When should I use Drum Player?
Drum Player fits situations like: the user asks about drum player; related techniques; needs guidance in this domain; the request is outside the scope of drum player.
How do I install Drum Player in Claude Code?
Run `npx skills add FerroxLabs/wayland --skill drum-player -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/creative-arts/drum-player in FerroxLabs/wayland) into .claude/skills/drum-player in your project. Claude Code loads it when a task matches its description.
How do I install Drum Player in Codex?
Run `npx skills add FerroxLabs/wayland --skill drum-player -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/creative-arts/drum-player in FerroxLabs/wayland) into .agents/skills/drum-player in your project. Codex loads it when a task matches its description.
Can I use Drum Player in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill drum-player -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/drum-player, .gemini/skills/drum-player, .github/skills/drum-player and .opencode/skills/drum-player in your project.
What does Drum Player need to run?
SKILL.md names no scripts, command-line tools or credentials: Drum Player is instructions for the agent only.
Does Drum Player access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Drum Player safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Drum Player use?
Drum Player is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Drum Player use?
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Drum Player?
Skills that share tags, products or a category with Drum Player: Acreadiness Generate Instructions (github/awesome-copilot, 40k stars), Sensory Instructions (thedaviddias/Front-End-Checklist, 74k stars), Form Filling (asgeirtj/system_prompts_leaks, 69k stars) and Player Example (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Drum Player?
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.