
marketing
by nicepkg
๐ 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command โ instant domain expertise. Marketing, SEO, Trading, Video, PM workflows included.
SKILL.md
name: marketing description: Create comprehensive marketing content for themes, plugins, and web products. Generates organized folder structure with product descriptions, feature highlights, social media posts, email campaigns, video scripts, sales materials, and brand assets. Use when creating promotional content, announcements, or sales copy.
Marketing Skill for Theme & Plugin Agency
Writing Style Guidelines
Tone & Voice (Non-Negotiable)
Be Human, Not AI:
- Write like a helpful colleague, not a marketing robot
- Use natural language that sounds like a real person wrote it
- Avoid buzzwords: "revolutionary", "game-changing", "seamless", "leverage", "synergy"
- Skip filler words: "basically", "essentially", "simply", "just"
- No excessive punctuation (!!!) or ALL CAPS for emphasis
Emoji Policy:
- Maximum ONE emoji per piece of content (or none)
- Use only when it adds clarity, not decoration
- Prefer text over emoji for important information
What to Avoid:
โ "๐ This REVOLUTIONARY plugin will TRANSFORM your workflow!! ๐ฅ"
โ
"This plugin handles form submissions automatically, so you can focus on your actual work."
โ "Simply leverage our seamless integration to unlock game-changing results!"
โ
"Connect it to your email list in two clicks. New subscribers sync automatically."
Folder Structure
When creating marketing content for a product, create this folder structure:
marketing/
โโโ 01-slides/ # Visual presentation content
โ โโโ product-overview-slides.md
โ โโโ feature-breakdown-slides.md
โ โโโ use-case-slides.md
โ โโโ free-vs-pro-comparison.md
โโโ 02-video-scripts/ # Video content
โ โโโ 01-product-overview.md # 2-3 min explainer
โ โโโ 02-installation-setup.md # Tutorial
โ โโโ 03-feature-demos.md # Feature walkthroughs
โ โโโ short-ads.md # 15s, 30s, 60s scripts
โ โโโ shot-list-template.md # Production notes
โโโ 03-website-copy/ # Website content
โ โโโ landing-page.md # Full landing page
โ โโโ features.md # Feature highlights
โ โโโ product-description.md # Marketplace descriptions
โ โโโ faq-content.md # FAQ section
โ โโโ feature-pages/ # Individual feature pages
โ โโโ [feature-name].md
โโโ 04-email-sequences/ # Email campaigns
โ โโโ welcome-sequence.md # Onboarding emails
โ โโโ feature-announcement.md # New feature emails
โ โโโ free-to-pro-upgrade.md # Upgrade campaigns
โ โโโ re-engagement.md # Win-back emails
โโโ 05-social-media/ # Social content (separate files per platform)
โ โโโ twitter-posts.md # Twitter/X content
โ โโโ linkedin-posts.md # LinkedIn content
โ โโโ facebook-posts.md # Facebook content
โ โโโ instagram-captions.md # Instagram content
โโโ 06-sales-materials/ # Sales enablement
โ โโโ one-pager.md # Quick sales sheet
โ โโโ objection-handling.md # Sales FAQ responses
โ โโโ feature-comparison-chart.md # Competitive comparison
โ โโโ roi-calculator-content.md # Value justification
โ โโโ testimonials.md # Customer quotes
โโโ 07-brand-assets/ # Brand guidelines
โ โโโ persona-profiles.md # Target customer profiles
โ โโโ messaging-guide.md # Voice and messaging
โ โโโ seo-keywords.md # Keywords and meta content
โโโ README.md # Index and quick reference
Instructions
1. Always Start with Personas
Before creating content, define 3-5 target personas in 07-brand-assets/persona-profiles.md:
## Persona: [Name]
### Demographics
- Role, Age, Team Size, Industry, Technical Level
### Goals
- What they want to achieve
### Pain Points
- Problems they face (be specific, not generic)
### Why Product Appeals
- Feature-to-benefit mapping
### Key Message
> "One sentence that resonates with this persona"
### Content They Respond To
- Types of content that work
2. Product Descriptions
Lead with benefits, not features:
โ "Includes auto-moderation feature"
โ
"Stop spam automatically โ so you can focus on growing your community"
Power words to use wisely: effortless, powerful, stunning, instant, automatic Words to avoid: revolutionary, game-changing, seamless, leverage, synergy, cutting-edge
3. Feature Highlights
Transform every feature into a benefit using:
- "so you can..."
- "which means..."
**What It Does:**
[Feature description - plain language]
**The Benefit:**
[Outcome] โ so you can [user benefit].
**Why It Matters:**
- [Feature detail], which means [benefit]
- [Feature detail], so you can [benefit]
4. Screenshots & Visuals
Requirements:
- Use real screenshots from local development environment
- Show actual product UI, not mockups
- Annotate with arrows or highlights for clarity
- Crop to relevant area (no full-screen captures)
- Ensure no sensitive data visible
- Use consistent browser/window size
Before creating visual content, ask:
"Do you have a local development setup where we can capture real screenshots? I'll need access to take authentic product images."
5. Video Scripts
Structure for each video:
## Video Details
- Title, Duration, Purpose, Tone, Target
## Script
### INTRO (0:00 - 0:XX)
**VISUAL:** [Description]
**NARRATOR:** "[Script - conversational, not salesy]"
**ON-SCREEN TEXT:** "[Text overlay]"
### [SECTION NAME] (X:XX - X:XX)
...
## Production Notes
- Visual style
- Music suggestions (upbeat but not overwhelming)
- Screenshots needed (from local dev environment)
6. Social Media (Separate Files Per Platform)
Twitter/X: (twitter-posts.md)
- Hook in first line
- 1-2 key benefits
- One emoji maximum (or none)
- Thread format for longer content
LinkedIn: (linkedin-posts.md)
- Professional tone
- Problem โ Solution format
- Statistics and proof points
- No emoji or one maximum
Facebook: (facebook-posts.md)
- Community-focused
- Storytelling approach
- Engagement questions
Instagram: (instagram-captions.md)
- Visual-first (describe image needed)
- Short, punchy captions
- Carousel/Reel ideas included
7. Email Campaigns
Structure each email file with multiple templates:
- Subject line variations (A/B test)
- Full email body (human tone, not salesy)
- CTA options (clear, action-oriented)
8. Sales Materials
One-Pager: Print-ready summary with:
- Problem/Solution (lead with the problem they feel)
- Key features (3-5 max)
- Results/Stats (real numbers when possible)
- Pricing
- CTA
Objection Handling: For each objection:
- Understand (clarifying questions)
- Acknowledge (validate concern genuinely)
- Address (provide information)
- Confirm (check if resolved)
9. Pricing Messaging
Always include accurate pricing from product page:
| License | Price | Sites |
|---------|-------|-------|
| Single | $XX/yr | 1 site |
| 5 License | $XX/yr | 5 sites |
| Developer | $XX/yr | Unlimited |
Quality Checklist
Before completing, verify:
Content Quality
- Personas defined
- All folders created
- Pricing accurate
- Benefits (not just features)
- "so you can..." language used
- Social media split by platform
- Objection handling complete
- README index updated
Tone Check
- Human tone (not robotic/AI-sounding)
- No excessive emojis (max 1 per piece)
- No buzzwords (revolutionary, seamless, etc.)
- No filler words (basically, simply, etc.)
- Reads like a helpful colleague wrote it
- Direct and respectful of reader's time
Visual Content
- Screenshots requested from local dev environment
- No stock photos where real product images should be
- All visuals annotated clearly
- No sensitive data visible
Score
Total Score
Based on repository quality metrics
SKILL.mdใใกใคใซใๅซใพใใฆใใ
ใฉใคใปใณในใ่จญๅฎใใใฆใใ
100ๆๅญไปฅไธใฎ่ชฌๆใใใ
GitHub Stars 100ไปฅไธ
1ใถๆไปฅๅ ใซๆดๆฐ
10ๅไปฅไธใใฉใผใฏใใใฆใใ
ใชใผใใณIssueใ50ๆชๆบ
ใใญใฐใฉใใณใฐ่จ่ชใ่จญๅฎใใใฆใใ
1ใคไปฅไธใฎใฟใฐใ่จญๅฎใใใฆใใ
Reviews
Reviews coming soon
