u/DiabolikswordSecond

https://preview.redd.it/4vloff0zhdyg1.png?width=1918&format=png&auto=webp&s=bef8d88f260d3d4f82baf5582b899936d285e2a3

I've been selling digital products on Gumroad for a while now, and writing listings was always the part I hated most. Not because I can't write, but because a good listing needs like 6 different things at once: an emotional hook, SEO-optimized tags, the right title format, pricing logic, seasonal timing. It's a lot of context-switching for one product page.

So I built a Claude Skill called Listing Story Alchemist that handles all of it. You give it a product photo or a short description ("handmade macrame wall hanging, boho style"), and it generates a full 7-section listing package:

1. Story-driven product description (emotion-first, not "Introducing our...")
2. SEO title + description + 13 tags (platform-specific for Etsy and Gumroad)
3. A "2X Favorite" premium rewrite with stronger hooks and scarcity
4. A/B test variants (emotion-first vs benefit-first titles)
5. Seasonal angle for right now
6. Competitor analysis notes
7. Pricing suggestions with reasoning

It's specifically trained to avoid AI-sounding language. No "delve," no "elevate," no em dashes. Tags follow Etsy's 20-char limit and don't repeat title words.

It's free and open source: https://github.com/diabolikss-debug/Listing_Story_Alchemist

Works as a Claude Skill (drop the folder into your skills directory). The repo includes two full examples: a physical product (macrame) and a digital product (Notion template).

Happy to answer questions. Would love feedback from anyone who tries it on their own products.

https://preview.redd.it/h2we7cxcyjxg1.png?width=1904&format=png&auto=webp&s=9044852ca918451caae8443c94005bb20a267c9e

Hey everyone,

After months of producing rock songs with Suno for my YouTube channel,

I kept running into the same problems over and over:

- Generic prompts producing forgettable tracks

- Copyright concerns when trying to capture specific moods (saying

"in the style of [Artist]" is risky)

- Inconsistent vocal identity across songs

- Turkish lyrics getting mispronounced because of certain characters

- English versions feeling like literal translations instead of

proper adaptations

So I documented every solution I found and turned it into a Claude AI

skill that anyone can use. It's open-source under MIT license.

What it does:

The skill activates when you ask Claude to help create a rock song.

It then walks through the entire process:

1. Asks clarifying questions about theme, atmosphere, language
2. Suggests title options (single-word titles work best for AI music)
3. Writes complete lyrics with Suno structure tags
4. Generates a Suno-ready style prompt with all 9 components(genre, era, tempo, vocals, instruments, dynamics, duration,language, theme)
5. Provides production tips specific to that song

Subgenres covered:

Classic rock, hard rock, doom metal, stoner rock, post-rock, punk,

grunge, alternative indie, garage rock, shoegaze, sludge rock, and

post-grunge ballads. Each has detailed era/atmosphere/vocal

descriptions.

The copyright safety part:

This was the biggest motivator. The skill enforces strict rules:

- No artist or band names anywhere in outputs

- Era + geography + atmosphere references instead

(e.g., "early 1990s Pacific Northwest grunge atmosphere")

- Similarity check on lyrics when reference songs are mentioned

- All metaphors and imagery rewritten if too close to reference

Multilingual support:

Primary: English and Turkish (with detailed rules for each)

Secondary: Spanish, French, German, Italian, Portuguese

The Turkish-English adaptation methodology is documented separately,

because translating songs word-for-word doesn't work musically.

Repo: https://github.com/diabolikss-debug/ai-rock-songwriter-skill

Free to use, modify, or fork. The README has full installation

instructions and a real example output (Turkish/English bilingual

song).

Would love feedback from people producing AI music regularly. What's

missing? What subgenres should I add next? Are there language-specific

issues you've run into that the skill could address?