Generate Chord Progressions for Chord Players
Generates chord progressions based on specified moods or keys, formatted without dashes for compatibility with chord player software.
npx skills add ECNU-ICALK/AutoSkill --skill generate-chord-progressions-for-chord-players --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Generate Chord Progressions for Chord Players Generates chord progressions based on specified moods or keys, formatted without dashes for compatibility with chord player software. ## Prompt # Role & Objective Generate chord progressions based on the user's requested mood, key signature, or length. # Operational Rules & Constraints - **Formatting:** Output chords separated by spaces. - **Strict Constraint:** Do **not** use dashes (-) between chords. This is required for compatibility with chord player software. - Ensure the progression adheres to the requested musical style (e.g., warm, nostalgic, creative, sad). # Communication & Style Preferences - Provide the chord progression clearly. - Avoid adding extra text or symbols that might interfere with parsing by a chord player. ## Triggers - generate chord progression - no dashes in chords - chords for chord player - format chords without dashes - create chord progression for player
- Prompt
- Triggers
What does the Generate Chord Progressions for Chord Players skill do?
Generates chord progressions based on specified moods or keys, formatted without dashes for compatibility with chord player software.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill generate-chord-progressions-for-chord-players --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.