promo-writer
关于
The promo-writer skill generates native, platform-specific social media copy (for Twitter, Instagram, etc.) from album themes, track concepts, and lyrics. It populates a `promo/` directory with ready-to-review content, ensuring each platform gets tailored text. Use it after lyrics are written and before release to fill promotional templates.
快速安装
Claude Code
推荐npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skillsgit clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/promo-writer在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Promo Writer Skill
Generate social media copy for album promotion across Twitter/X, Instagram, TikTok, Facebook, and YouTube. Produces native-feeling content for each platform from album context — themes, track concepts, and streaming lyrics.
Purpose
Populate the promo/ directory with platform-specific copy ready for review. Each platform gets content shaped to its format, tone, and conventions — not the same text cross-posted everywhere.
When to Use
- After track concepts and lyrics are written (need material to pull from)
- Before release — generate copy to fill promo/ templates
- User says "write promo copy", "create social media posts", or "fill in the promo templates"
- When promo/ files exist but are still template placeholders
Position in Workflow
Lyrics Written → Promo Videos (optional) → **[Promo Writer]** → [Promo Review] → Release
Between content completion and promo-reviewer. The promo-reviewer polishes what this skill generates.
Supporting Files
- copy-formulas.md — Hook formulas, CTA templates, post structures, hashtag recipes
- /reference/promotion/social-media-best-practices.md — Platform strategy and content guidance
- /skills/promo-reviewer/platform-rules.md — Character limits and hashtag rules
Workflow
1. Album Resolution
Resolve the album from arguments:
Use MCP find_album with the album name from $ARGUMENTS. If no album specified, check get_session for last album context.
Verify readiness:
- Album must have track concepts written
- At least some tracks should have streaming lyrics (for quotable hooks)
- If no streaming lyrics exist, warn: "No streaming lyrics found — using track concepts only. Hooks will be less specific."
2. Data Gathering
Gather album context in batch to minimize round-trips:
- Album data:
get_album_full(album_slug, "concept,streaming,musical-direction")— album narrative + track content - Track list: from album data — all track names, concepts, statuses
- Streaming lyrics: from album data sections — pull quotable hooks from streaming lyrics (NOT Suno lyrics, which contain phonetic spellings)
- User preferences:
load_override("promotion-preferences.md")— tone, platform priorities, messaging themes, hashtag preferences, AI positioning
Critical: Use streaming lyrics for quotable hooks. Suno lyrics contain phonetic spellings (bit-wize, Luh-rock-uh) that must never appear in public-facing copy.
3. Generate Campaign Strategy (campaign.md)
Generate campaign.md first — it's the strategy foundation that informs all platform copy.
Content to generate:
| Section | What to Write |
|---|---|
| Campaign Overview | Album name, release date (or TBD), primary platform, campaign duration |
| Key Messages | 3 core messages derived from album themes — the "why should anyone care" |
| Target Audience | 2-3 audience segments based on genre and themes |
| Schedule | Pre-release, release week, post-release calendar with specific content types |
| Hashtags | Primary (discovery + genre) and secondary (album-specific, AI if applicable) |
Derive key messages from album data:
- What is the album about? → Message 1 (concept hook)
- What makes it different? → Message 2 (unique angle)
- Why listen now? → Message 3 (urgency/relevance)
Present to user for approval before proceeding to platform copy.
4. Language Selection
Before generating any copy, determine the output language(s).
If override exists with a ## Language section in promotion-preferences.md, use that preference without asking.
Otherwise, ask:
What language(s) should the promo copy be written in?
[1] English (default)
[2] German (Deutsch)
[3] French (Français)
[4] Spanish (Español)
[5] Bilingual — two languages per post (e.g., DE + EN, FR + EN)
[6] Other — tell me which language(s)
Bilingual mode: When two languages are selected, each post gets both versions stacked in the same code block, separated by a --- divider. The primary language comes first, the secondary language second. Hashtags stay in English (international discovery).
Override file addition ({overrides}/promotion-preferences.md):
## Language
- Primary: de
- Secondary: en
- Mode: bilingual
Store the selected language(s) and apply to all generated copy in this session.
5. Platform Selection
If platform specified in arguments, generate only that platform.
If override exists, follow platform priority list and skip list from promotion-preferences.md.
Otherwise, ask:
Which platforms should I generate copy for?
[A] All platforms (Twitter, Instagram, TikTok, Facebook, YouTube)
[1] Twitter/X
[2] Instagram
[3] TikTok
[4] Facebook
[5] YouTube
6. Per-Platform Generation
For each selected platform, generate native content following the structures in copy-formulas.md and best practices from the reference guide.
Read the promo template for the platform first (templates/promo/{platform}.md or existing promo/{platform}.md) to match the expected heading structure.
Per-platform content to generate:
Twitter/X (twitter.md)
- Release announcement tweet (1-2 tweets or thread)
- Per-track promo tweets (one per track — hook + concept + link placeholder)
- Behind-the-scenes tweet (process/making-of angle)
- Engagement tweet (question or poll)
- Each tweet: show character count, verify under 280
- 1-2 hashtags per tweet, never starting with a hashtag
Instagram (instagram.md)
- Release announcement caption (hook in first 125 chars)
- 2-3 track highlight captions (story angle, personal)
- Behind-the-scenes caption
- Hashtag block (15-20 tags, separated from caption)
- Show character count for each caption
TikTok (tiktok.md)
- Release announcement caption (under 150 chars)
- Per-track captions (short, casual, under 150 chars)
- Behind-the-scenes caption
- 3-5 hashtags per post
- Note: video content does the heavy lifting — captions are secondary
Facebook (facebook.md)
- Release announcement (longer storytelling format, 150-300 words)
- Track highlight posts (2-3, with personal angle)
- Behind-the-scenes story post
- 3-5 hashtags per post, at end
YouTube (youtube.md)
- Album/track description template (hook in first 2-3 lines)
- Credits section
- Social links section
- 3-5 hashtags
7. Present for Approval
Present each platform's generated copy with metrics:
## Twitter/X — Generated Copy
### Release Announcement
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Generated tweet text]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Chars: 187/280 | Hashtags: 2 | Status: Within limits
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
### Track 01: [Track Name]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Generated tweet text]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Chars: 214/280 | Hashtags: 2 | Status: Within limits
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[... more posts ...]
Actions:
[A] Approve all — write to promo/twitter.md
[R] Revise specific posts — tell me which ones and what to change
[N] Next platform — skip this platform
8. Write Approved Copy
Write approved copy to the promo/ directory in the album path:
{content_root}/artists/{artist}/albums/{genre}/{album}/promo/
Match the file structure expected by promo-reviewer:
- Use
##and###headings to delineate sections - Put post copy inside ``` code blocks
- Include any platform-specific metadata (character counts not written to file)
If promo/ directory doesn't exist, create it. If files already exist, ask before overwriting:
promo/twitter.md already has content. Overwrite? [Y/n]
9. Summary and Next Steps
After all platforms are written:
## Promo Copy Generated
| Platform | Posts | Status |
|----------|-------|--------|
| Campaign | 1 | Written |
| Twitter | 8 | Written |
| Instagram | 5 | Written |
| TikTok | 6 | Written |
| Facebook | 4 | Written |
| YouTube | 1 | Written |
Files written to: {album_path}/promo/
Next steps:
1. Review and polish: /bitwize-music:promo-reviewer <album-name>
2. Replace [Streaming Link] placeholders with actual URLs when available
3. When ready to release: /bitwize-music:release-director <album-name>
Content Rules
Streaming Lyrics Only
Pull quotable hooks from streaming lyrics sections. Never use Suno lyrics — they contain phonetic spellings meant for the AI, not human readers.
Campaign First
Always generate campaign.md before platform copy. The strategy document establishes key messages, audience, and schedule that inform every platform's content.
Native Content
Each platform gets content shaped to its conventions:
- Twitter: punchy, under 280 chars, 1-2 hashtags
- Instagram: visual-first, hook in first 125 chars, hashtag block
- TikTok: ultra-casual, under 150 chars, video does the work
- Facebook: storytelling, longer form, community-building
- YouTube: informative, structured, SEO-aware
Never write the same text for multiple platforms.
Match Promo-Reviewer Structure
The promo-reviewer skill expects specific file structure:
##headings for major sections###headings for individual posts- Post copy inside ``` code blocks
- This structure enables section-by-section review
Hashtag Rules
Follow the researched best practices:
- Twitter: 1-2 per tweet, never start with hashtag, rotate sets
- Instagram: 15-20 per post, separate block, mix volume levels
- TikTok: 3-5 per post, include trending if applicable
- Facebook: 3-5, at end, for categorization
- YouTube: 3-5, first 3 shown above title
- Never use: #MusicPromotion, #SoundCloudPromotion, #FollowBack, #Like4Like
Language Handling
- Write all copy in the language(s) selected in Step 4
- Bilingual mode: Primary language first,
---divider, secondary language second — both in the same code block - Twitter exception: Bilingual mode uses separate tweets per language (one tweet per language, or thread), NOT stacked in one tweet — 280 chars is too tight for two languages
- Hashtags: Always in English for international discovery, regardless of copy language
- Quoted lyrics: Keep in original language with a brief translation in parentheses if the copy language differs
- Platform notes (Notes section at bottom of each file): Always in English for consistency
Override Respect
If promotion-preferences.md override exists:
- Follow tone and voice preferences
- Respect platform skip list
- Apply messaging theme preferences (always/never mention)
- Use hashtag preferences (always include, avoid list)
- Follow AI positioning guidance
- Follow language preferences (primary, secondary, mode)
Remember
- Read copy-formulas.md at invocation — it has the hook formulas and post structures
- Streaming lyrics only — never Suno phonetic lyrics in public copy
- Campaign.md first — strategy before platform copy
- Language before platforms — determine output language(s) before generating any copy
- Present before writing — show generated copy with metrics for approval
- Native per platform — different tone, length, structure for each
- Match promo-reviewer format — headings + code blocks for section-by-section review
- Check override — load
promotion-preferences.mdfor tone, platforms, messaging, language - Suggest promo-reviewer next — always end with the recommendation to review
- Placeholder links — use
[Streaming Link]where real URLs will go - Preserve album voice — the copy should feel consistent with the album's themes and tone
- Hashtags in English — always English hashtags for discovery, even when copy is in another language
Your deliverable: Populated promo/ directory with platform-specific copy ready for review.
Workflow integration: You fill the gap between content completion and promo-reviewer — generating what was previously a manual creative step.
GitHub 仓库
相关推荐技能
content-collections
元Content Collections 是一个 TypeScript 优先的构建工具,可将本地 Markdown/MDX 文件转换为类型安全的数据集合。它专为构建博客、文档站和内容密集型 Vite+React 应用而设计,提供基于 Zod 的自动模式验证。该工具涵盖从 Vite 插件配置、MDX 编译到生产环境部署的完整工作流。
polymarket
元这个Claude Skill为开发者提供完整的Polymarket预测市场开发支持,涵盖API调用、交易执行和市场数据分析。关键特性包括实时WebSocket数据流,可监控实时交易、订单和市场动态。开发者可用它构建预测市场应用、实施交易策略并集成实时市场预测功能。
creating-opencode-plugins
元该Skill帮助开发者创建OpenCode插件,用于接入命令、文件、LSP等25+种事件。它提供了插件结构、事件API规范和JavaScript/TypeScript实现模式,适合需要拦截操作、扩展功能或自定义事件处理的场景。开发者可通过它快速构建响应式模块来增强OpenCode AI助手的能力。
sglang
元SGLang是一个专为LLM设计的高性能推理框架,特别适用于需要结构化输出的场景。它通过RadixAttention前缀缓存技术,在处理JSON、正则表达式、工具调用等具有重复前缀的复杂工作流时,能实现极速生成。如果你正在构建智能体或多轮对话系统,并追求远超vLLM的推理性能,SGLang是理想选择。
