nightingale-karaoke▌
aradotso/trending-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Skill by ara.so — Daily 2026 Skills collection.
Nightingale Karaoke Skill
Skill by ara.so — Daily 2026 Skills collection.
Nightingale is a self-contained, ML-powered karaoke application written in Rust (Bevy engine). It scans a local music folder, separates vocals from instrumentals (UVR Karaoke model or Demucs), transcribes lyrics with word-level timestamps (WhisperX), and plays back with synchronized highlighting, real-time pitch scoring, player profiles, and GPU shader / video backgrounds. Everything — ffmpeg, Python, PyTorch, ML models — is bootstrapped automatically on first launch.
Installation
Pre-built Binary (Recommended)
Download the latest release from the Releases page for your platform and run it.
macOS only — remove quarantine after extracting:
xattr -cr Nightingale.app
Build from Source
Prerequisites:
- Rust 1.85+ (edition 2024)
- Linux additionally needs:
libasound2-dev libudev-dev libwayland-dev libxkbcommon-dev
git clone https://github.com/rzru/nightingale
cd nightingale
# Development build
cargo build --release
# Run directly
./target/release/nightingale
Release Packaging
# Linux / macOS
scripts/make-release.sh
# Windows (PowerShell)
powershell -ExecutionPolicy Bypass -File scripts/make-release.ps1
Outputs a .tar.gz (Linux/macOS) or .zip (Windows) ready for distribution.
First Launch / Bootstrap
On first run, Nightingale downloads and configures:
ffmpegbinaryuv(Python package manager)- Python 3.10 via uv
- PyTorch + WhisperX + audio-separator in a virtual environment
- UVR Karaoke ONNX model and WhisperX
large-v3model
This takes 2–10 minutes depending on network speed. A progress screen is shown in-app.
To force re-bootstrap at any time:
./nightingale --setup
Bootstrap completion is marked by ~/.nightingale/vendor/.ready.
CLI Flags
| Flag | Description |
|---|---|
--setup |
Force re-run of the first-launch bootstrap (re-downloads vendor deps) |
Keyboard & Gamepad Controls
Navigation
| Action | Keyboard | Gamepad |
|---|---|---|
| Move | Arrow keys | D-pad / Left stick |
| Confirm | Enter | A (South) |
| Back | Escape | B (East) / Start |
| Switch panel | Tab | — |
| Search | Type to filter | — |
Playback
| Action | Keyboard | Gamepad |
|---|---|---|
| Pause / Resume | Space | Start |
| Exit to menu | Escape | B (East) |
| Toggle guide vocals | G | — |
| Guide volume up/down | + / - | — |
| Cycle background | T | — |
| Cycle video flavor | F | — |
| Toggle microphone | M | — |
| Next microphone | N | — |
| Toggle fullscreen | F11 | — |
Configuration
Main Config
Located at ~/.nightingale/config.json. Edit directly or via in-app settings.
{
"music_folder": "/home/user/Music",
"separator": "uvr",
"guide_vocal_volume": 0.3,
"background_theme": "plasma",
"video_flavor": "nature",
"default_profile": "Alice"
}
separator options: "uvr" (default, preserves backing vocals) | "demucs"
background_theme options: "plasma", "aurora", "waves", "nebula", "starfield", "video", "source_video"
video_flavor options: "nature", "underwater", "space", "city", "countryside"
Profiles
Located at ~/.nightingale/profiles.json:
{
"profiles": [
{
"name": "Alice",
"scores": {
"blake3_hash_of_song": {
"stars": 4,
"score": 87250,
"played_at": "2026-03-18T21:00:00Z"
}
}
}
]
}
Pixabay Video Backgrounds (Dev)
API key is embedded in release builds. For local development, create .env at project root:
# .env
PIXABAY_API_KEY=$PIXABAY_API_KEY
The release script (make-release.sh) sources .env automatically.
Data Storage Layout
~/.nightingale/
├── cache/ # Per-song stems, transcripts, lyrics (keyed by blake3 hash)
├── config.json # App settings
├── profiles.json # Player profiles and per-song scores
├── videos/ # Pre-downloaded Pixabay video backgrounds
├── sounds/ # Sound effects
├── vendor/
│ ├── ffmpeg # ffmpeg binary
│ ├── uv # uv binary
│ ├── python/ # Python 3.10
│ ├── venv/ # ML virtualenv (WhisperX, Demucs, audio-separator)
│ ├── analyzer/ # Python analyzer scripts
│ └── .ready # Bootstrap completion marker
└── models/
├── torch/ # Demucs model weights
├── huggingface/ # WhisperX large-v3 weights
└── audio_separator/ # UVR Karaoke ONNX model
Cache keys are blake3 hashes of the source file — re-analysis only triggers if the file changes or is manually invalidated.
Supported File Formats
Audio: .mp3, .flac, .ogg, .wav, .m4a, .aac, .wma
Video: .mp4, .mkv, .avi, .webm, .mov, .m4v
Video files: audio track is extracted, vocals separated, original video plays as background automatically.
Hardware Acceleration
PyTorch backend is auto-detected:
| Backend | Device | Notes |
|---|---|---|
| CUDA | NVIDIA GPU | Fastest; ~2–5 min/song |
| MPS | Apple Silicon | macOS; WhisperX alignment falls back to CPU |
| CPU | Any | Always works; ~10–20 min/song |
UVR Karaoke model uses ONNX Runtime with CUDA (NVIDIA) or CoreML (Apple Silicon) automatically.
Processing Pipeline
Audio/Video file
│
▼
UVR Karaoke (ONNX) or Demucs (PyTorch)
│ vocals.ogg + instrumental.ogg
▼
LRCLIB API ──▶ Synced lyrics fetch (if available)
│
▼
WhisperX large-v3 ──▶ Transcription + word-level timestamps
│
▼
Bevy App (Rust)
- Plays instrumental audio
- Synchronized word highlighting
- Real-time pitch detection & scoring
- GPU shader / video backgrounds
- Scoreboards per profile
Code Patterns
Adding a New Background Theme (Bevy System)
// In your Bevy plugin, register a new background variant
use bevy::prelude::*;
#[derive(Component)]
pub struct MyCustomBackground;
pub fn spawn_custom_background(mut commands: Commands) {
commands.spawn((
MyCustomBackground,
// ... your background components
));
}
pub struct CustomBackgroundPlugin;
impl Plugin for CustomBackgroundPlugin {
fn build(&self, app: &mut App) {
app.add_systems(OnEnter(AppState::Playing), spawn_custom_background);
}
}
Extending Config Deserialization
use serde::{Deserialize, Serialize};
#[derive(Debug, Clone, Serialize, Deserialize)]
pub struct NightingaleConfig {
pub music_folder: String,
#[serde(default = "default_separator")]
pub separator: StemSeparator,
#[serde(default = "default_guide_volume")]
pub guide_vocal_volume: f32,
}
#[derive(Debug, Clone, Serialize, Deserialize, Default)]
#[serde(rename_all = "lowercase")]
pub enum StemSeparator {
#[default]
Uvr,
Demucs,
}
fn default_guide_volume() -> f32 { 0.3 }
fn default_separator() -> StemSeparator { StemSeparator::Uvr }
// Load config
fn load_config() -> NightingaleConfig {
let path = dirs::home_dir()
.unwrap()
.join(".nightingale/config.json");
let raw = std::fs::read_to_string(&path).unwrap_or_default();
serde_json::from_str(&raw).unwrap_or_default()
}
Triggering Re-analysis Programmatically
use std::fs;
use How to use nightingale-karaoke 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 nightingale-karaoke
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches nightingale-karaoke from GitHub repository aradotso/trending-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 nightingale-karaoke. Access the skill through slash commands (e.g., /nightingale-karaoke) 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.7★★★★★66 reviews- ★★★★★Hana Jain· Dec 28, 2024
We added nightingale-karaoke from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Carlos Thomas· Dec 24, 2024
I recommend nightingale-karaoke for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★James Brown· Dec 20, 2024
Solid pick for teams standardizing on skills: nightingale-karaoke is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Dec 16, 2024
nightingale-karaoke reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Nikhil Rao· Dec 16, 2024
nightingale-karaoke fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Diego Huang· Dec 12, 2024
nightingale-karaoke reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ren Martin· Dec 8, 2024
Keeps context tight: nightingale-karaoke is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Charlotte Dixit· Dec 4, 2024
We added nightingale-karaoke from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ava Rao· Nov 27, 2024
nightingale-karaoke has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★James Taylor· Nov 15, 2024
nightingale-karaoke reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 66