bitwize-music-studio/claude-ai-music-skills / skills/promo-reviewer
promo-reviewer
VerifiedReviews and iterates on social media copy in album promo/ files. Use after populating promo templates and before release to polish platform-specific posts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| platform-rules.md | markdown | 5.6 KB |
platform-rules.md
View on GitHub# Platform Rules Reference
Character limits, hashtag conventions, and tone guidelines for each social media platform. Used by the promo-reviewer skill during post review.
---
## Platform Limits
| Platform | Char Limit | Hashtag Range | Hashtag Max | Key Constraint |
|----------|-----------|---------------|-------------|----------------|
| Twitter/X | 280 | 1-2 | 5 | Per-tweet limit; threads: 280/tweet |
| Instagram | 2,200 | 15-20 | 30 | First 125 chars visible before "more" |
| TikTok | 4,000 | 3-5 | 10 | Under 150 chars ideal for visibility |
| Facebook | 63,206 | 3-5 | 10 | First 2-3 lines visible before "See more" |
| YouTube | 5,000 | 3-5 | 15 | First 2-3 lines visible in collapsed view |
| Campaign | N/A | N/A | N/A | Strategy doc — no platform limits |
---
## Twitter/X Rules
### Character Counting
- **Hard limit**: 280 characters per tweet
- URLs count as 23 characters (t.co shortening)
- Emojis count as 2 characters
- Hashtags count toward the 280 limit
- Mentions (@name) count toward the 280 limit
### Thread Rules
- Each tweet in a thread must be standalone under 280 chars
- First tweet should hook — it's what people see in timeline
- Number tweets for clarity (1/, 2/, 3/)
- Last tweet: call to action + link
### Hashtag Convention
- 1-2 hashtags per tweet (optimal engagement)
- More than 5 looks spammy, reduces engagement
- Never start a tweet with a hashtag (algorithm penalty)
- Place tags in the tweet body, not in a reply thread
- Rotate tags — using the same set every tweet triggers spam detection
- Music hashtags: #NewMusic, #NowPlaying, genre-specific
### Tags to Avoid
- #MusicPromotion, #SoundCloudPromotion — attracts bots, not listeners
- #FollowBack, #Like4Like — spam signals that tank credibility
- #MusicIsLife, #Beats — too generic, zero discovery value
### Tone
- Concise, punchy, conversational
- Personality allowed — don't sound like a press release
- Questions and polls drive engagement
- Emojis OK but don't overdo
---
## Instagram Rules
### Character Counting
- **Limit**: 2,200 characters per caption
- **Visible preview**: First ~125 characters before "more" tap
- Put the hook in those first 125 characters
- Line breaks count as characters
### Hashtag Convention
- **Optimal**: 15-20 hashtags
- **Maximum**: 30 hashtags (hard limit, post fails above this)
- Place hashtags as a separate block after the caption
- Separate with line breaks or dots for visual spacing
- Mix popular + niche hashtags for reach + targeting
### Hashtag Block Format
```
.
.
.
#NewMusic #HipHop #IndieMusic #MusicRelease #NowPlaying
#AIMusic #NewAlbum #StreamNow #MusicProduction #IndieArtist
```
### Tone
- Visual storytelling — pair with strong image/video
- Longer captions OK if engaging
- Personal, behind-the-scenes angle works well
- Call to action: "Link in bio", "Save this post"
---
## TikTok Rules
### Character Counting
- **Limit**: 4,000 characters
- **Visible without tap**: ~150 characters
- Keep captions short — video is the content
- Under 150 chars = fully visible = better engagement
### Hashtag Convention
- 3-5 hashtags
- Include 1-2 trending/discovery hashtags
- Music-specific: #NewMusic, #MusicTok, genre tags
- Don't use hashtags that are too broad (#fyp is debated)
### Tone
- Casual, authentic, unpolished feel
- Speak like a person, not a brand
- Humor and personality win
- Direct address: "You need to hear this"
---
## Facebook Rules
### Character Counting
- **Limit**: 63,206 characters (effectively unlimited)
- **Visible preview**: First 2-3 lines before "See more"
- Hook must be in those first lines
- Longer storytelling posts perform well
### Hashtag Convention
- 3-5 hashtags (Facebook is less hashtag-driven)
- Place at end of post
- Use for categorization more than discovery
- Don't over-hashtag — looks out of place on Facebook
### Tone
- Longer storytelling acceptable
- More formal than Twitter/TikTok but still personal
- Community-building language
- Questions drive comments and engagement
- Share the story behind the music
---
## YouTube Rules
### Character Counting
- **Description limit**: 5,000 characters
- **Visible preview**: First 2-3 lines (above "Show more")
- Hook + key links in first 2-3 lines
- Rest of description: credits, timestamps, links
### Description Structure
```
[Hook — what the video/track is about]
[Streaming links]
[Credits and details]
[Timestamps if applicable]
[Social links]
#NewMusic #Genre #ArtistName
```
### Hashtag Convention
- 3-5 hashtags
- Displayed above the video title (first 3)
- Use genre + discovery tags
- Don't exceed 15 (diminishing returns)
### Tone
- Informative and organized
- Include credits, collaborator info
- Timestamps for longer videos
- SEO-aware: keywords in first 2 lines
---
## Cross-Platform Guidelines
### Consistency
- Core message should be the same across platforms
- Adapt length and tone to each platform
- Streaming links in every release post
- Album name and artist name always included
### Placeholder Detection
Flag any remaining template placeholders:
- `[Album Name]` — should be replaced with actual album name
- `[Streaming Link]` — needs real URL or "link in bio"
- `[Genre]` — should be specific genre tag
- `[Date]` — should be actual date
- `[Post copy]` — section needs real content
### Common Issues
- **Over char limit**: Shorten or split into thread (Twitter)
- **Too few hashtags**: Add relevant ones (Instagram especially)
- **Too many hashtags**: Trim to platform optimal range
- **Missing call to action**: Add "Listen now", "Stream", "Link in bio"
- **No streaming link**: Add link or "link in bio" reference
- **Generic copy**: Make specific to this album/track
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |