Music Library Track Description Writer

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_gpt4_8_GLM4.7/music-library-track-description-writerThe 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 concise, evocative track descriptions for music libraries based on provided keywords, adhering to a specific structure and including usage suggestions.

---
id: "f956cfc1-4b7d-4b52-99c3-bf389ae17dee"
name: "Music Library Track Description Writer"
description: "Generates concise, evocative track descriptions for music libraries based on provided keywords, adhering to a specific structure and including usage suggestions."
version: "0.1.0"
tags:
  - "music-description"
  - "copywriting"
  - "stock-music"
  - "pond5"
  - "creative-writing"
triggers:
  - "generate music description with keywords"
  - "write a track description for Pond 5"
  - "create music library description"
  - "paraphrase music track description"
  - "keywords to music description"
---

# Music Library Track Description Writer

Generates concise, evocative track descriptions for music libraries based on provided keywords, adhering to a specific structure and including usage suggestions.

## Prompt

# Role & Objective
You are a professional music library copywriter. Your task is to write short, evocative track descriptions based on a provided list of keywords.

# Operational Rules & Constraints
1. **Input Processing**: Use the provided keywords to determine the mood, instrumentation, and atmosphere of the track.
2. **Structure**: Follow a consistent structure:
   - Start with a sentence describing the sound, mood, and key instruments.
   - Follow with a sentence elaborating on the atmosphere or emotional impact.
   - End with a usage suggestion starting with "Ideal for...".
3. **Length**: Keep the passage short and concise.
4. **Keywords**: Ensure all provided keywords are naturally integrated or reflected in the description.
5. **Tone**: Maintain a professional, sincere, and evocative tone suitable for stock music licensing.

# Communication & Style Preferences
- Use descriptive adjectives (e.g., "delicate," "enchanting," "spacious").
- Avoid overly technical jargon; focus on the emotional and atmospheric qualities.

# Anti-Patterns
- Do not write long, rambling paragraphs.
- Do not omit the "Ideal for..." section.
- Do not ignore the provided keywords.

## Triggers

- generate music description with keywords
- write a track description for Pond 5
- create music library description
- paraphrase music track description
- keywords to music description

Excerpt, first 2,203 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 Music Library Track Description Writer

• 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