agentsclimarketplace

Song storyteller

Skill kosbushe/song-storyteller/skills/song-storyteller

Research and write a vivid, fact-checked story about any song in the reader's language, beginning with a clear explanation of what the song is really about. Use when a user provides a song title, artist, lyrics excerpt, recording link, remix, cover, traditional song, or instrumental work and asks for its meaning, translation context, origin, production story, cultural impact, disputed legend, or a music-magazine-style feature.From its SKILL.md

Install
npx -y skills add kosbushe/song-storyteller --skill song-storyteller

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

7.0 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Song Storyteller

Create a compact music feature that makes the reader hear a familiar song differently. Lead with meaning, then tell only the verified history that deepens it. Never replace missing evidence with a beautiful invention.

Before researching, read these references completely:

Understand the request

Accept a title and artist, a recording link, or both. Respect the specified recording, remix, live performance, adaptation, or cover.

Reply in the user's language unless they request another language. Preserve official titles, names, and essential terms in their original script, adding transliteration only when it helps identification or pronunciation.

If the title identifies several plausible works or the version materially changes the story, ask one short question. Otherwise begin without ceremony.

Workflow

1. Identify the work

  • Verify the artist, title, original language, writers, first recording, release context, and requested version.
  • Distinguish the lyricist, composer, performer, producer, translator, adapter, remixer, and cover artist.
  • For traditional or disputed works, describe the uncertainty instead of assigning a convenient author.

2. Establish the meaning first

Before researching biography or chart history, write an internal three-sentence answer:

  1. Who is speaking, and to whom?
  2. What situation, desire, or conflict unfolds?
  3. What might a listener miss because of language, music, title, cultural distance, or a popular misconception?

When the song's language differs from the response language, or the song is widely misunderstood, open with a natural equivalent of "Do you understand what this song is really about?" Answer immediately. Do not hide the meaning merely to manufacture suspense.

For an instrumental work, replace lyrical meaning with the work's dramatic idea, program, function, or historically supported emotional frame. Do not invent a narrative the composer never supplied.

3. Research across languages

Use web research for every new story. Search in the song's original language, the response language, and a useful bridge language when needed. Follow the research ladder in Multilingual research.

Build a private evidence dossier before drafting:

  1. Creator testimony about origin or meaning, if it exists.
  2. Images, idioms, grammar, dialect, or cultural references essential to understanding the song.
  3. Verified creation and release chronology.
  4. A musical, vocal, or production choice that changes how the words are perceived.
  5. Necessary biographical, political, religious, regional, or genre context.
  6. A popular legend and its evidence status, if relevant.
  7. One central surprise that changes the listening experience, plus one backup.

Seek independent confirmation for claims carrying the story. Several pages repeating one anecdote do not count as several sources.

4. Separate evidence from interpretation

Classify each important claim privately:

  • Confirmed: directly supported by a strong source.
  • Probable: supported by converging evidence but not settled.
  • Interpretation: inferred from words, music, performance, or context.
  • Legend: widely repeated but unverified or disproved.

Express those distinctions naturally in the article. Never write "the artist meant" without direct support.

5. Find one story

Choose one conflict or paradox: listeners understand the song backward; seductive music carries bleak words; a translation changed its cultural life; a private crisis became a public ritual; a production accident became part of the meaning.

Use this invisible structure:

  1. Meaning-first question and plain answer.
  2. Why the sound, language, or common story masks that meaning.
  3. One verified creation scene or history.
  4. Two to four essential images, expressions, or musical details.
  5. One turn that changes how the reader hears the song.
  6. A calm ending that returns to the meaning with new evidence.

Do not turn the structure into a list of visible headings unless the user asks for a guide rather than an article.

6. Explain without flattening

  • Explain who speaks, who is addressed, what changes, and what remains unsaid.
  • Resolve idioms, wordplay, register, dialect, pronouns, code-switching, and unreliable narration.
  • Contrast the emotional information in the music with the words.
  • Use concise paraphrase instead of line-by-line translation.
  • Quote only the shortest phrase necessary for analysis. Never reproduce full lyrics or long consecutive passages.
  • Keep meaningful ambiguity when the original keeps it. Translation should clarify possibilities, not choose one without evidence.

7. Write, compress, and cite

Write with the confidence and curiosity of an excellent music columnist without imitating a named writer. Default to 700–1,100 words or roughly 3–6 minutes of reading. Follow the user's requested length when given.

Never output the Unicode em dash U+2014. Use only the short en dash (U+2013) wherever a dash is needed. Before publishing, search the complete draft for U+2014 and replace every occurrence.

Place descriptive links beside the claims they support. Link to the interview, archive, paper, or article itself, never a search results page.

Cut at least 15 percent from the first draft. Remove repeated conclusions, irrelevant biography, decorative chart facts, empty transitions, and any detail that does not improve the meaning, sound, or cultural story.

8. Final check

  • The meaning is clear by the end of the second paragraph.
  • Every load-bearing fact has an appropriate source.
  • Creator testimony, analysis, and audience interpretation remain distinct.
  • No scene, thought, dialogue, motive, or causal link has been invented.
  • The surprise changes the song rather than merely displaying trivia.
  • The prose sounds natural when read aloud in the response language.
  • The text contains no U+2014 em dashes; every dash is the short U+2013 en dash.
  • The conclusion gives the reader a reason to listen again.

Output

Return:

  1. A precise, inviting headline without clickbait.
  2. A meaning-first opening paragraph.
  3. One continuous magazine-style story with inline sources.
  4. A short "Listen again" block, translated into the response language, with two concrete details.
  5. An uncertainty note only when a disputed point materially affects the story.

Do not add a separate bibliography when the important sources are already linked in context.

What ships with it: 4 files

9.9 KB alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.