opencode-skills-collection 3.1.12 → 3.1.13

package/bundled-skills/developer-listening/SKILL.md

@@ -0,0 +1,232 @@
+---
+name: developer-listening
+description: "Monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord. Trigger phrases: \"developer listening\", \"monitor developer conversations\", \"track..."
+risk: unknown
+source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-listening
+source_repo: jonathimer/devmarketing-skills
+source_type: community
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
+---
+
+# Developer Listening
+## When to Use
+
+Use this skill when you need monitor what developers say about your brand, competitors, and the problems they're solving. Track mentions and conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter, and Discord. Trigger phrases: "developer listening", "monitor developer conversations", "track...
+
+
+Monitor developer conversations across platforms to understand sentiment, find engagement opportunities, and gather competitive intelligence.
+
+## Overview
+
+Developer listening is the practice of systematically monitoring what developers say about your brand, competitors, and the problems your product solves. Unlike traditional social listening, developer listening requires monitoring technical platforms where developers actually spend time: GitHub, Hacker News, Reddit programming communities, Stack Overflow, Twitter/X, and Discord servers.
+
+Effective developer listening helps you:
+- Understand how developers perceive your product
+- Find frustrated users who need help (and might churn)
+- Discover engagement opportunities before competitors
+- Gather unfiltered product feedback
+- Track competitive positioning in real conversations
+- Identify content gaps and documentation issues
+
+## Setting Up Your Monitoring Strategy
+
+### 1. Define Your Keyword Categories
+
+Before setting up monitoring, organize keywords into categories:
+
+**Brand Keywords:**
+- Your product name and common misspellings
+- Your company name
+- Key team members' names (for attribution)
+- Your GitHub org/repos
+- Your Twitter handles
+
+**Competitor Keywords:**
+- Direct competitor names
+- Competitor product features
+- Competitor pricing/plan names
+
+**Problem Keywords:**
+- Pain points your product solves
+- Error messages you help with
+- Workflow descriptions ("deploy to kubernetes", "manage API keys")
+- "How do I..." phrases relevant to your space
+
+**Buy Intent Keywords:**
+- "[category] recommendation"
+- "best [tool type] for [use case]"
+- "looking for [solution]"
+- "alternative to [competitor]"
+- "[competitor] vs"
+
+### 2. Set Up Monitoring Tools
+
+Choose a social listening tool that aggregates mentions across developer platforms (GitHub, Hacker News, Reddit, Stack Overflow, Twitter).
+
+**Recommended Keyword Structure:**
+- Create separate keywords for brand, competitors, and problem spaces
+- Use exact match for brand names to reduce noise
+- Use broader matching for problem keywords
+- Set up negative keywords to filter irrelevant mentions
+
+### 3. Platform-Specific Monitoring
+
+**GitHub:**
+- Monitor issues mentioning your product in other repos
+- Track discussions in relevant GitHub Discussions
+- Watch for your product in awesome-lists and comparison repos
+- Monitor stars/forks of competitor repos for traction signals
+
+**Hacker News:**
+- High-signal but low-volume
+- Comments often contain detailed technical feedback
+- "Show HN" and "Ask HN" posts reveal developer needs
+- Threads about competitors are engagement opportunities
+
+**Reddit:**
+- r/programming, r/webdev, r/devops, r/selfhosted, etc.
+- Subreddit-specific cultures require tailored responses
+- Question threads are high-intent opportunities
+
+**Stack Overflow:**
+- Monitor tags related to your product category
+- Questions reveal documentation gaps
+- Answers from competitors show their positioning
+
+**Twitter/X:**
+- Real-time sentiment and virality
+- Developer influencer conversations
+- Conference and event discussions
+- Complaint threads often go viral
+
+**Discord:**
+- Harder to monitor but high-signal
+- Join relevant community servers manually
+- Look for integration opportunities with popular servers
+
+## Sentiment Analysis and Prioritization
+
+### Prioritization Framework
+
+Not all mentions deserve equal attention. Prioritize based on:
+
+**High Priority (Respond within hours):**
+- Negative sentiment from existing users
+- Direct questions about your product
+- Complaints going viral
+- Competitor comparisons where you're losing
+- Buy-intent signals from ideal customer profiles
+
+**Medium Priority (Respond within 24-48 hours):**
+- Neutral mentions seeking recommendations
+- Feature requests in public forums
+- Documentation confusion
+- Competitor criticism (potential switchers)
+
+**Low Priority (Monitor and aggregate):**
+- General industry discussions
+- Competitor praise (learn from it)
+- Historical mentions for trend analysis
+
+### Sentiment Filtering
+
+Most monitoring tools offer sentiment filtering. Key queries to set up:
+
+- Negative sentiment mentions from the last 30 days
+- High-relevance mentions that haven't been engaged with yet
+- Platform-specific filters (Hacker News, Reddit, Twitter)
+
+## Finding Engagement Opportunities
+
+### Types of Engagement Opportunities
+
+**Frustrated Users:**
+- Complaining about your product = urgent support opportunity
+- Complaining about competitors = potential conversion
+- Complaining about the problem space = thought leadership opportunity
+
+**Questions and Recommendations:**
+- Direct questions about your product
+- "What tool should I use for X" threads
+- Comparison requests
+
+**Buy Intent Signals:**
+- "Looking for a [your category]"
+- "Evaluating [competitor] vs [competitor]"
+- "Need to migrate from [competitor]"
+- "Budget approved for [solution]"
+
+### Engagement Best Practices
+
+1. **Be helpful first, promotional second** - Answer the question before mentioning your product
+2. **Disclose affiliation** - "I work at [company]" builds trust
+3. **Match the platform culture** - HN hates marketing speak, Reddit values authenticity
+4. **Provide value even if they don't convert** - Good advice builds reputation
+5. **Don't argue with critics** - Acknowledge, fix if valid, move on
+
+## Competitive Intelligence from Conversations
+
+### What to Track
+
+**Competitor Mentions:**
+- Praise (what are they doing right?)
+- Criticism (opportunities for you)
+- Feature requests (what's missing?)
+- Churn signals ("migrating away from")
+
+**Positioning Shifts:**
+- How competitors describe themselves
+- Which use cases they emphasize
+- Pricing and packaging discussions
+
+**Community Sentiment:**
+- Overall vibe toward competitors
+- Developer trust levels
+- Support quality perception
+
+### Extracting Insights
+
+Track trends over time using your monitoring tool's analytics:
+
+- Sentiment trends for competitors over 90 days
+- Mention volume comparison between your brand and top competitors
+- Platform breakdown (where are conversations happening?)
+
+## Tools
+
+### Social Listening
+
+Use a monitoring tool that tracks developer platforms. Key capabilities to look for:
+- Multi-platform coverage (GitHub, HN, Reddit, Stack Overflow, Twitter)
+- Sentiment analysis
+- Keyword alerts and filtering
+- Analytics and trend tracking
+
+### Platform-Specific Tools
+
+**GitHub Search:**
+- Use `gh search issues` and `gh search repos` for GitHub-specific monitoring
+- Track issues mentioning your product in other repositories
+
+**Twitter/X Search:**
+- Advanced search operators for precise monitoring
+- Track specific accounts and hashtags
+- Tools like Typefully, TweetDeck, or Hootsuite for monitoring
+
+**Reddit:**
+- Native Reddit search with subreddit filters
+- Third-party tools like Syften or F5Bot for alerts
+
+## Related Skills
+
+- **competitor-tracking** - Systematic competitor analysis beyond conversation monitoring
+- **alternatives-pages** - Convert competitive insights into comparison content
+- **community-engagement** - Best practices for responding to developer conversations
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream source and local project context.
+- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
+- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/developer-newsletter/README.md

@@ -0,0 +1,84 @@
+# developer-newsletter
+
+**Build newsletters developers actually open.**
+
+## What It Does
+
+Guides you through creating and growing a developer newsletter. Covers content strategy, writing, subject lines, growth tactics, and avoiding spam filters.
+
+## When to Use
+
+- Starting a developer newsletter
+- Writing your next issue
+- Improving open/click rates
+- Growing your subscriber base
+- When you say "newsletter," "email marketing," "dev newsletter," or "email list"
+
+## Quick Start
+
+```
+/developer-newsletter
+
+I want to start a weekly newsletter about JavaScript performance.
+Target: frontend developers at mid to senior level.
+```
+
+The skill will:
+1. Load your developer audience context
+2. Help define your newsletter type and frequency
+3. Guide content mix and structure
+4. Optimize subject lines and deliverability
+
+## Key Frameworks
+
+### Content Mix (70-20-10)
+
+| Percentage | Content Type |
+|------------|--------------|
+| 70% | Value content (teach, inform, help) |
+| 20% | Product content (updates, features) |
+| 10% | Promotional (CTAs, asks) |
+
+### Subject Line Patterns
+
+What works:
+- Specific benefit: "Cut your build time by 40%"
+- Technical curiosity: "The JavaScript feature nobody uses"
+- Direct announcement: "v2.0 is here: async/await support"
+- Number + topic: "7 TypeScript tricks senior devs use"
+
+### Benchmarks
+
+| Metric | Target |
+|--------|--------|
+| Open rate | 30-50% |
+| Click rate | 5-15% |
+| Unsubscribe rate | <0.5% |
+
+## Files
+
+| File | Description |
+|------|-------------|
+| `SKILL.md` | Full skill instructions with templates |
+
+## Included Guidance
+
+- Frequency selection
+- Subject line testing framework
+- Code snippet formatting in email
+- Spam filter avoidance
+- Growth tactics (organic + referral)
+- ESP comparison
+
+## Tools
+
+- **[Octolens](https://octolens.com)** — Find trending topics for newsletter content
+- **Buttondown/Beehiiv** — Newsletter platforms
+- **SparkLoop** — Referral programs
+- **Mail-Tester** — Spam score checking
+
+## Related Skills
+
+- `developer-audience-context` — Know your readers
+- `devrel-content` — Source newsletter content
+- `community-building` — Community-driven content ideas

package/bundled-skills/developer-newsletter/SKILL.md

@@ -0,0 +1,376 @@
+---
+name: developer-newsletter
+description: When the user wants to create, write, or improve a newsletter for developer audiences. Trigger phrases include "newsletter," "email marketing," "developer email," "weekly digest," "dev newsletter," "email subscribers," "newsletter growth," or "email list."
+risk: unknown
+source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-newsletter
+source_repo: jonathimer/devmarketing-skills
+source_type: community
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
+---
+
+# Developer Newsletter
+## When to Use
+
+Use this skill when you need when the user wants to create, write, or improve a newsletter for developer audiences. Trigger phrases include "newsletter," "email marketing," "developer email," "weekly digest," "dev newsletter," "email subscribers," "newsletter growth," or "email list.".
+
+
+This skill helps you build and write newsletters that developers actually open, read, and look forward to receiving. Covers content strategy, writing, growth, and deliverability.
+
+---
+
+## Before You Start
+
+**Load your audience context first.** Read `.agents/developer-audience-context.md` to understand:
+
+- Who you're writing for (role, seniority, tech stack)
+- What content resonates (problems, interests)
+- Where else they consume content (to avoid duplicate effort)
+- Voice & tone (how casual/technical)
+
+If the context file doesn't exist, run the `developer-audience-context` skill first.
+
+---
+
+## Newsletter Strategy
+
+### Define Your Newsletter Type
+
+| Type | Description | Example |
+|------|-------------|---------|
+| **Product updates** | Changelog, new features, tips | Vercel's updates |
+| **Curated links** | Best content from around the web | TLDR, Bytes |
+| **Original content** | Your own articles, tutorials | Cassidy Williams |
+| **Community digest** | What happened in your community | Dev community roundups |
+| **Educational series** | Teaching a topic over time | Course-style newsletters |
+
+**Best practice**: Pick ONE primary type. You can mix in others, but have a clear identity.
+
+### Frequency Matrix
+
+| Frequency | Best For | Risk |
+|-----------|----------|------|
+| **Daily** | Curated links, news | Fatigue, hard to maintain |
+| **Weekly** | Most newsletters | Sweet spot for most |
+| **Bi-weekly** | Original content heavy | Can lose momentum |
+| **Monthly** | Product updates, digests | Easy to forget you exist |
+
+**Developer preference**: Weekly is the sweet spot. Developers are busy and inbox-protective.
+
+---
+
+## Content Mix Framework
+
+### The 70-20-10 Rule
+
+| Percentage | Content Type | Purpose |
+|------------|--------------|---------|
+| **70%** | Value content | Teach, inform, help |
+| **20%** | Product content | Updates, features, how-tos |
+| **10%** | Promotional | CTAs, asks, sales |
+
+### Content Categories
+
+Build a rotation of these:
+
+| Category | Examples |
+|----------|----------|
+| **Tutorials** | "How to implement X" |
+| **News analysis** | "What Y announcement means for you" |
+| **Tool/library roundups** | "5 libraries for handling Z" |
+| **Code snippets** | "Quick tip: better error handling" |
+| **Community highlights** | "Best from our Discord this week" |
+| **Industry takes** | "Why I think X is overhyped" |
+| **Behind the scenes** | "How we built feature Y" |
+| **Q&A** | "You asked, we answered" |
+
+---
+
+## Writing Developer Emails
+
+### Subject Line Framework
+
+What works for developers:
+
+| Pattern | Example | Why It Works |
+|---------|---------|--------------|
+| **Specific benefit** | "Cut your build time by 40%" | Concrete value |
+| **Technical curiosity** | "The JavaScript feature nobody uses" | Triggers curiosity |
+| **Direct announcement** | "v2.0 is here: async/await support" | Clear, newsworthy |
+| **Number + topic** | "7 TypeScript tricks senior devs use" | Scannable, specific |
+| **Question** | "Are you still using callbacks?" | Pattern interrupt |
+| **Breaking news** | "React 19 is out: what you need to know" | Timely, urgent |
+
+What doesn't work:
+
+| Avoid | Why |
+|-------|-----|
+| ALL CAPS | Spam signals |
+| "Quick question" | Manipulative |
+| Excessive emoji | Looks like marketing |
+| "You won't believe..." | Clickbait fatigue |
+| No subject line | Just... no |
+
+### Pre-header Text
+
+The preview text after the subject line. Use it.
+
+| Subject | Pre-header |
+|---------|------------|
+| "v2.0 is here" | "Plus: breaking changes to watch for" |
+| "This week in Node.js" | "fetch() drama, npm security, and a cool CLI" |
+
+### Email Structure
+
+```
+[Short personal intro - 1-2 sentences]
+
+[Main content sections with clear headers]
+
+[Code snippet if relevant]
+
+[Quick links section]
+
+[Sign-off with personality]
+```
+
+### Code in Email
+
+Code rendering is tricky in email. Options:
+
+| Approach | Pros | Cons |
+|----------|------|------|
+| **Inline code** (`backticks`) | Works everywhere | No highlighting |
+| **Plain text block** | Reliable | Ugly |
+| **Image of code** | Beautiful | Can't copy, accessibility issues |
+| **"View in browser" link** | Full formatting | Friction |
+| **Styled HTML tables** | Decent formatting | Complex, can break |
+
+**Recommendation**: Keep code short. Use inline code for small snippets, link to full examples.
+
+```html
+<pre style="background-color: #1e1e1e; color: #d4d4d4; padding: 16px; border-radius: 4px; font-family: 'Fira Code', monospace; font-size: 14px; overflow-x: auto;">
+const result = await fetch('/api/data');
+</pre>
+```
+
+---
+
+## Subject Line Testing
+
+### A/B Test Framework
+
+Test one variable at a time:
+
+| Variable | Version A | Version B |
+|----------|-----------|-----------|
+| **Length** | "TypeScript 5.0 features" | "7 TypeScript 5.0 features that will change how you write code" |
+| **Specificity** | "New features" | "Async imports, decorators, and 5 more" |
+| **Format** | Statement | Question |
+| **Personalization** | Generic | "[Name], your weekly digest" |
+| **Emoji** | None | One relevant emoji |
+
+### Subject Line Checklist
+
+Before sending:
+
+- [ ] Under 50 characters (mobile preview)
+- [ ] No spam trigger words (free, act now, limited time)
+- [ ] Specific, not vague
+- [ ] Matches email content (no bait and switch)
+- [ ] Would YOU open this?
+
+---
+
+## Growth Tactics
+
+### Organic Growth
+
+| Tactic | Implementation |
+|--------|----------------|
+| **Blog footer CTA** | "Get posts like this in your inbox" with inline form |
+| **Content upgrades** | "Download the full checklist" for email |
+| **Exit intent** | Popup when leaving (use sparingly) |
+| **Twitter/social mentions** | "I write about this weekly in my newsletter" |
+| **Documentation CTA** | Subscribe box in docs footer |
+| **Open source README** | Newsletter link in project README |
+| **Conference talks** | "Sign up for slides + bonus content" |
+
+### Referral Programs
+
+| Reward Tier | Reward Example |
+|-------------|----------------|
+| **1 referral** | Shoutout in newsletter |
+| **5 referrals** | Exclusive content / early access |
+| **10 referrals** | Swag (stickers, t-shirt) |
+| **25 referrals** | 1:1 call / premium access |
+
+### Cross-Promotion
+
+Partner with complementary newsletters:
+
+| Your Newsletter | Good Partners |
+|-----------------|---------------|
+| React-focused | TypeScript, Node.js, frontend newsletters |
+| DevOps | Cloud, Kubernetes, infrastructure newsletters |
+| AI/ML | Python, data science newsletters |
+
+Swap mentions, not full ads.
+
+---
+
+## Avoiding Spam Filters
+
+### Technical Setup
+
+| Requirement | What to Do |
+|-------------|------------|
+| **SPF** | Add DNS record authorizing your sender |
+| **DKIM** | Sign emails cryptographically |
+| **DMARC** | Policy for handling auth failures |
+| **Custom domain** | Send from `news@yourcompany.com`, not personal |
+| **Warm up** | Start with small sends, increase gradually |
+
+### Content Hygiene
+
+| Do | Don't |
+|-----|-------|
+| Plain text version | HTML only |
+| Reasonable image ratio | All images, no text |
+| Clear unsubscribe | Hidden or difficult unsub |
+| Consistent sending | Sporadic, unpredictable |
+| Clean list | Bounces, inactive, purchased |
+
+### Red Flag Words
+
+Avoid in subject lines and body:
+
+| Category | Words to Avoid |
+|----------|----------------|
+| **Urgency** | Act now, Limited time, Expires |
+| **Free stuff** | Free, No cost, No obligation |
+| **Money** | $$, Cash, Earn, Investment |
+| **Exaggeration** | Amazing, Incredible, Best ever |
+| **Spam classics** | Click here, Winner, Congratulations |
+
+---
+
+## Email Service Providers
+
+### Developer-Friendly Options
+
+| ESP | Best For | Dev Features |
+|-----|----------|--------------|
+| **Buttondown** | Simple, markdown-first | API, RSS import, minimal |
+| **ConvertKit** | Creator newsletters | Automations, landing pages |
+| **Mailchimp** | General purpose | Robust API, integrations |
+| **Resend** | Developer-first | React Email, great DX |
+| **Loops** | SaaS companies | Product-focused features |
+| **Beehiiv** | Growth-focused | Referrals, monetization |
+
+### DIY Options
+
+| Tool | Use Case |
+|------|----------|
+| **Resend + React Email** | Custom transactional + marketing |
+| **Postmark** | Reliability-focused |
+| **SendGrid** | Scale-focused |
+
+---
+
+## Metrics & Benchmarks
+
+### Key Metrics
+
+| Metric | Developer Newsletter Benchmark |
+|--------|-------------------------------|
+| **Open rate** | 30-50% (higher than B2C) |
+| **Click rate** | 5-15% |
+| **Unsubscribe rate** | <0.5% per send |
+| **Spam complaints** | <0.1% |
+| **List growth rate** | 5-10% monthly |
+
+### What to Track
+
+| Metric | What It Tells You |
+|--------|------------------|
+| **Open rate by subject** | Subject line effectiveness |
+| **Click rate by link** | Content resonance |
+| **Reply rate** | Engagement depth |
+| **Unsubscribe after send** | Content fit |
+| **Forward rate** | Shareability |
+| **Growth source** | Best acquisition channels |
+
+---
+
+## Newsletter Template
+
+```markdown
+Subject: [Specific, benefit-driven headline]
+Pre-header: [Teaser that complements subject]
+
+---
+
+Hey [first name],
+
+[1-2 sentence personal intro or hook]
+
+## [Main Section 1]
+
+[2-3 paragraphs with value]
+
+\`\`\`javascript
+// Quick code example if relevant
+\`\`\`
+
+## [Main Section 2]
+
+[Content]
+
+## Quick Links
+
+- [Link 1]: One-line description
+- [Link 2]: One-line description
+- [Link 3]: One-line description
+
+## From the Community
+
+[Highlight something from Discord/Twitter/GitHub]
+
+---
+
+[Personal sign-off]
+
+[Name]
+
+P.S. [Optional: extra CTA, fun fact, or teaser]
+```
+
+---
+
+## Tools
+
+| Tool | Use Case |
+|------|----------|
+| **[Octolens](https://octolens.com)** | Monitor developer conversations for newsletter content ideas. Track what topics are trending on HN, Reddit, and Twitter. |
+| **Buttondown/ConvertKit/Beehiiv** | Newsletter platforms |
+| **SparkLoop** | Referral program management |
+| **Mailmeteor/Email Octopus** | Budget-friendly sending |
+| **Mail-Tester** | Check spam score before sending |
+| **Litmus/Email on Acid** | Email rendering preview |
+
+---
+
+## Related Skills
+
+- `developer-audience-context` — Know who you're writing for
+- `devrel-content` — Source content for your newsletter
+- `community-building` — Generate community content
+- `developer-advocacy` — Build your personal brand alongside newsletter
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream source and local project context.
+- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
+- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.