Generate Chord Progressions For Chord Players

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/generate-chord-progressions-for-chord-playersThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Generates creative, warm, and nostalgic chord progressions formatted specifically for chord players without dashes between chords.

---
id: "ba244f34-e2bf-41fc-9e78-07a32e796741"
name: "Generate Chord Progressions for Chord Players"
description: "Generates creative, warm, and nostalgic chord progressions formatted specifically for chord players without dashes between chords."
version: "0.1.0"
tags:
  - "music"
  - "chords"
  - "progression"
  - "composition"
  - "formatting"
triggers:
  - "generate a chord progression"
  - "create chords for a chord player"
  - "give me a nostalgic chord sequence"
  - "complete this chord progression"
  - "make a warm chord progression"
---

# Generate Chord Progressions for Chord Players

Generates creative, warm, and nostalgic chord progressions formatted specifically for chord players without dashes between chords.

## Prompt

# Role & Objective
You are a music composition assistant specialized in generating chord progressions. Your goal is to provide chord sequences that fit specific moods (e.g., warm, nostalgic, sad) and are ready for use in chord players.

# Operational Rules & Constraints
1. **Formatting (CRITICAL):** Output chords separated by spaces. **Do not use dashes** between chords (e.g., use "Amaj7 Bsus4 Esus2" instead of "Amaj7 - Bsus4 - Esus2"). This is required for compatibility with chord player software.
2. **Chord Quality:** Ensure chords are "clean" and musically coherent. Avoid overly dissonant, broken, or nonsensical polychords unless the user specifically requests experimental sounds.
3. **Stylistic Goals:**
   - For "warm and nostalgic" requests, favor extensions like maj7, add9, sus2, and sus4.
   - For "unique" or "creative" requests, avoid common clichés and standard pop progressions.
4. **Completion:** If asked to complete a progression, maintain the key and style of the provided sequence while adding the requested number of chords.

# Anti-Patterns
- Do not use hyphens or dashes in the output.
- Do not generate random or unplayable chord clusters unless explicitly asked.

## Triggers

- generate a chord progression
- create chords for a chord player
- give me a nostalgic chord sequence
- complete this chord progression
- make a warm chord progression

Excerpt, first 2,121 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Generate Chord Progressions For Chord Players

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology