opencode-skills-collection 3.1.12 → 3.1.14

package/bundled-skills/developer-audience-context/SKILL.md

@@ -0,0 +1,271 @@
+---
+name: developer-audience-context
+description: When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer...
+risk: unknown
+source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-audience-context
+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 Audience Context
+## When to Use
+
+Use this skill when you need when the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include "developer persona," "target developers," "who are our developers," "developer...
+
+
+This skill helps you create and maintain `.agents/developer-audience-context.md` — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.
+
+---
+
+## Before You Start
+
+Check if `.agents/developer-audience-context.md` exists:
+
+- **If it exists**: Read it and offer to update specific sections
+- **If it doesn't exist**: Create the directory and file, then walk through each section
+
+---
+
+## Two Ways to Build Context
+
+### Option 1: Auto-Draft from Codebase (Recommended)
+
+Analyze existing materials to draft an initial version:
+
+1. **README.md** — Product description, features, getting started
+2. **Documentation** — `/docs`, API reference, tutorials
+3. **Landing pages** — `index.html`, marketing copy
+4. **package.json / pyproject.toml** — Dependencies reveal ecosystem
+5. **GitHub Issues** — Common questions, frustrations, use cases
+6. **Existing blog posts** — Technical content, tutorials
+
+After drafting, walk through each section to validate and fill gaps.
+
+### Option 2: Start from Scratch
+
+Ask questions section-by-section. Don't advance until the current section is complete.
+
+---
+
+## The 10 Sections to Capture
+
+### 1. Product Overview
+
+| Field | What to capture |
+|-------|-----------------|
+| Product name | Official name and any aliases |
+| One-liner | "We help [developers] do [X] without [Y]" |
+| Category | API, SDK, CLI, SaaS, open source library, infrastructure |
+| Core technology | Languages, frameworks, platforms supported |
+| Pricing model | Free/open source, freemium, usage-based, seat-based |
+
+### 2. Developer Persona
+
+Not "developers" generically — get specific:
+
+| Field | What to capture |
+|-------|-----------------|
+| Primary role | Backend, frontend, full-stack, DevOps, data, ML, mobile |
+| Seniority | Junior, mid, senior, staff, lead, architect |
+| Company size | Solo, startup, scale-up, enterprise |
+| Industry verticals | Fintech, healthtech, e-commerce, gaming, B2B SaaS |
+| Tech stack | Languages, frameworks, cloud providers they use |
+| Decision authority | Individual contributor, team lead, buyer, influencer |
+
+**Ask**: "Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?"
+
+### 3. Where They Hang Out
+
+Developers research before they buy. Know where:
+
+| Channel | Specifics to capture |
+|---------|---------------------|
+| Communities | Specific subreddits, Discord servers, Slack groups |
+| Social | Twitter/X hashtags, LinkedIn groups |
+| Content | Blogs they read, newsletters they subscribe to, podcasts |
+| Events | Conferences, meetups, hackathons |
+| Code | GitHub topics, Stack Overflow tags |
+
+**Pro tip**: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.
+
+### 4. Problems & Pain Points
+
+Capture the actual problems, not your solution's features:
+
+| Level | What to capture |
+|-------|-----------------|
+| Functional | "I can't do X" / "X takes too long" / "X is error-prone" |
+| Emotional | Frustration, anxiety, embarrassment, fear |
+| Situational | When does the pain occur? What triggers the search? |
+
+**Ask**: "What's the #1 frustration that brings developers to you?"
+
+**Research**: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.
+
+### 5. Current Alternatives
+
+What are developers using today instead of you?
+
+| Alternative type | Examples |
+|-----------------|----------|
+| Direct competitors | Tools that solve the same problem |
+| DIY / build it yourself | Custom scripts, internal tools |
+| Indirect solutions | Workarounds, manual processes |
+| Do nothing | Live with the pain |
+
+For each alternative, capture:
+- Why developers choose it
+- What's frustrating about it
+- What would make them switch
+
+### 6. Key Differentiators
+
+What makes you different — in developer terms:
+
+| Differentiator type | Example |
+|--------------------|---------|
+| Technical | "10x faster," "No dependencies," "Type-safe" |
+| DX (Developer Experience) | "5-minute setup," "Great docs," "First-class CLI" |
+| Ecosystem | "Works with X," "Built for Y framework" |
+| Philosophy | "Open source," "Privacy-first," "Local-first" |
+
+**Warning**: Avoid marketing fluff. Developers see through "best-in-class" and "enterprise-grade." Use specific, provable claims.
+
+### 7. Verbatim Developer Language
+
+Capture exact phrases developers use — not polished marketing copy:
+
+| Category | Examples |
+|----------|----------|
+| Describing the problem | "This is such a pain," "I wish I could just..." |
+| Describing your product | How they explain it to others |
+| Objections | "But what about...", "I'm worried that..." |
+| Praise | Testimonials, tweets, GitHub comments |
+
+**Sources**: GitHub issues, Twitter mentions, Hacker News comments, support tickets, sales calls, community Slack/Discord.
+
+### 8. Technical Trust Signals
+
+What proof points matter to developers:
+
+| Signal type | Examples |
+|-------------|----------|
+| Adoption | GitHub stars, npm downloads, Docker pulls |
+| Quality | Test coverage, security audits, uptime SLA |
+| Community | Contributors, Discord members, forum activity |
+| Credibility | Backed by X, used by Y, created by Z |
+| Transparency | Open source, public roadmap, changelog |
+
+### 9. Conversion Actions
+
+What does success look like at each stage?
+
+| Stage | Primary action | Secondary actions |
+|-------|---------------|-------------------|
+| Awareness | Star repo, follow on Twitter | Read blog post, share content |
+| Consideration | Clone repo, read docs | Watch demo, join Discord |
+| Trial | Sign up, install SDK | Complete quickstart, make first API call |
+| Activation | Reach "Hello World" moment | Integrate into real project |
+| Conversion | Upgrade to paid | Add team members, expand usage |
+
+### 10. Voice & Tone
+
+How should you sound when talking to these developers?
+
+| Dimension | Spectrum |
+|-----------|----------|
+| Formality | Casual ← → Professional |
+| Technicality | Accessible ← → Deep technical |
+| Personality | Neutral ← → Opinionated |
+| Humor | Serious ← → Playful |
+
+**Examples**:
+- Stripe → Professional, precise, clean
+- Vercel → Modern, confident, developer-first
+- Supabase → Friendly, accessible, community-driven
+- Tailwind → Opinionated, direct, practical
+
+---
+
+## Output Format
+
+Save to `.agents/developer-audience-context.md` with this structure:
+
+```markdown
+# Developer Audience Context
+
+Last updated: [DATE]
+
+## Product Overview
+[Section content]
+
+## Developer Persona
+[Section content]
+
+## Where They Hang Out
+[Section content]
+
+## Problems & Pain Points
+[Section content]
+
+## Current Alternatives
+[Section content]
+
+## Key Differentiators
+[Section content]
+
+## Verbatim Developer Language
+[Section content]
+
+## Technical Trust Signals
+[Section content]
+
+## Conversion Actions
+[Section content]
+
+## Voice & Tone
+[Section content]
+```
+
+---
+
+## Maintenance
+
+Update this document when:
+
+- You learn something new from user research
+- You find great verbatim quotes
+- Your positioning or differentiation changes
+- You expand to new developer segments
+
+---
+
+## Tools
+
+| Tool | Use case |
+|------|----------|
+| **[Octolens](https://octolens.com)** | Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter. Essential for capturing verbatim language, finding pain points, and understanding where your developers hang out. |
+| **GitHub Search** | Find how developers describe problems in issues |
+| **Twitter Advanced Search** | Find discussions about your space |
+| **Google Alerts** | Track mentions of competitors and problem keywords |
+
+---
+
+## Related Skills
+
+After establishing context, these skills will reference it:
+
+- `devrel-content` — Writing content that resonates
+- `hacker-news-strategy` — Engaging on HN authentically
+- `developer-onboarding` — Optimizing time-to-value
+- `developer-seo` — Targeting the right technical queries
+- `competitor-tracking` — Understanding your competitive landscape
+
+## 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-audience-context/references/example-apitest.md

@@ -0,0 +1,175 @@
+# Developer Audience Context
+
+Last updated: 2024-01-15
+
+---
+
+## Product Overview
+
+| Field | Value |
+|-------|-------|
+| **Product name** | Checkmate (fictional example) |
+| **One-liner** | We help backend developers write API tests without learning a new DSL |
+| **Category** | CLI + Open source library |
+| **Core technology** | TypeScript, works with any Node.js project |
+| **Pricing model** | Open source core, paid cloud dashboard for teams |
+
+---
+
+## Developer Persona
+
+| Field | Value |
+|-------|-------|
+| **Primary role** | Backend / Full-stack |
+| **Seniority** | Mid to Senior (2-8 years experience) |
+| **Company size** | Startup to Scale-up (10-500 employees) |
+| **Industry verticals** | B2B SaaS, Fintech, E-commerce |
+| **Tech stack** | Node.js, TypeScript, Express/Fastify, PostgreSQL, REST APIs |
+| **Decision authority** | Individual contributor who influences tooling decisions |
+
+**Day-in-the-life**:
+> Sarah is a senior backend engineer at a Series B fintech startup. She spends most of her day writing and reviewing API code. She knows they should have better test coverage but the existing test setup is brittle and slow. Every time she tries to add tests, she spends more time fighting the test framework than writing actual tests. She's evaluated Postman and other tools but doesn't want to maintain tests in a separate GUI. She wants tests that live in her codebase and run in CI.
+
+---
+
+## Where They Hang Out
+
+| Channel | Specific places |
+|---------|-----------------|
+| **Reddit** | r/node, r/typescript, r/webdev, r/ExperiencedDevs |
+| **Discord/Slack** | Reactiflux, TypeScript Community, various company Slacks |
+| **Twitter/X** | #typescript, #nodejs, follows @sindresorhus, @maaboroosh, @benloeb |
+| **Newsletters** | Node Weekly, JavaScript Weekly, bytes.dev |
+| **Podcasts** | Syntax.fm, JS Party, The Changelog |
+| **Blogs** | Dev.to, Kent C. Dodds, Testing JavaScript |
+| **Conferences** | NodeConf, TSConf, local JavaScript meetups |
+| **GitHub** | Topics: testing, api-testing, typescript |
+| **Stack Overflow** | Tags: node.js, typescript, api-testing, jest, vitest |
+
+---
+
+## Problems & Pain Points
+
+### Functional problems
+- Existing test setups are slow and flaky
+- Learning curve for testing frameworks is steep
+- Mocking APIs and databases is painful
+- Tests don't catch the bugs that actually matter
+- CI runs take forever because of integration tests
+
+### Emotional pain
+- Embarrassment when production bugs could have been caught by tests
+- Frustration with test maintenance overhead
+- Anxiety about shipping without confidence
+- Guilt about skipping tests due to time pressure
+
+### Trigger moments
+- Just shipped a bug that tests would have caught
+- New team member asks "where are the tests?"
+- CI is taking 20+ minutes
+- Tried to refactor code and broke everything
+
+**#1 frustration that brings developers to us**:
+> "I want to test my APIs but I don't want to spend a week learning a new framework and setting up fixtures. Just let me write tests that look like the code I'm already writing."
+
+---
+
+## Current Alternatives
+
+| Alternative | Why devs choose it | What's frustrating | Switching triggers |
+|-------------|-------------------|-------------------|-------------------|
+| **Jest + Supertest** | Already using Jest, Supertest is simple | Slow, verbose setup, bad TypeScript support | Speed issues, TypeScript errors |
+| **Postman/Insomnia** | Visual, easy to start | Tests live outside codebase, hard to version control | Need tests in CI, team scaling |
+| **Playwright/Cypress** | Powerful, good DX | Overkill for API testing, slow | Just need API tests, not E2E |
+| **Build it themselves** | Full control | Maintenance burden, reinventing the wheel | Team grows, need standards |
+| **Do nothing** | No time investment | Bugs in production, no confidence | Major incident, new compliance requirement |
+
+---
+
+## Key Differentiators
+
+| Type | Our claim | Proof |
+|------|-----------|-------|
+| **Technical** | 10x faster than Jest+Supertest | Benchmark: 500 tests in 2s vs 20s |
+| **DX** | Zero-config TypeScript support | Just `npm install`, no setup |
+| **Ecosystem** | Works with your existing test runner | Vitest, Jest, Node test runner |
+| **Philosophy** | Tests should look like your code | No DSL, just TypeScript |
+
+---
+
+## Verbatim Developer Language
+
+### How they describe the problem
+> "Testing APIs shouldn't be this hard"
+> "I just want to make a request and check the response"
+> "Why do I need 50 lines of setup for one test?"
+> "Our test suite takes 15 minutes to run"
+
+### How they describe our product
+> "It's like if fetch() was designed for testing"
+> "Finally, API tests that don't suck"
+> "The TypeScript support is *chef's kiss*"
+
+### Common objections
+> "What about when I need to mock the database?"
+> "Will this work with our existing Jest setup?"
+> "We're already invested in Postman"
+> "Is this maintained? I don't want to depend on an abandoned project"
+
+### Praise / testimonials
+> "Migrated 200 tests in an afternoon. CI went from 12 minutes to 90 seconds." — @devname on Twitter
+> "Best testing DX I've experienced in 10 years of backend work." — GitHub issue #142
+
+**Sources**: GitHub issues, Twitter mentions, Hacker News launch thread, support Discord
+
+---
+
+## Technical Trust Signals
+
+| Signal | Current value |
+|--------|---------------|
+| **GitHub stars** | 3,200 |
+| **npm downloads** | 45k/week |
+| **Contributors** | 28 |
+| **Community size** | Discord: 1,200 members |
+| **Notable users** | Vercel, Linear, Cal.com |
+| **Backed by** | YC W24 |
+
+---
+
+## Conversion Actions
+
+| Stage | Primary action | Secondary actions |
+|-------|---------------|-------------------|
+| **Awareness** | Star repo | Read blog post, follow on Twitter |
+| **Consideration** | Read docs/quickstart | Watch 5-min demo, join Discord |
+| **Trial** | `npm install checkmate` | Run first test |
+| **Activation** | Migrate 1 existing test | Add to CI |
+| **Conversion** | Sign up for cloud dashboard | Add team members |
+
+**"Hello World" moment**:
+> Developer runs their first test and sees it pass in <100ms. They think "wait, that's it?" Then they look at the TypeScript autocomplete and realize they get full type safety on their API responses.
+
+---
+
+## Voice & Tone
+
+| Dimension | Our position (1-5) |
+|-----------|-------------------|
+| Casual ← → Professional | 2 (casual but competent) |
+| Accessible ← → Deep technical | 4 (assume backend knowledge) |
+| Neutral ← → Opinionated | 4 (we have opinions about testing) |
+| Serious ← → Playful | 3 (occasional humor, not try-hard) |
+
+**Voice inspiration** (brands/people to emulate):
+- Tailwind (opinionated but practical)
+- Vitest (modern, fast, developer-first)
+- tRPC (TypeScript-native thinking)
+
+**Words we use**:
+- Fast, simple, TypeScript-native, zero-config, real tests
+- "Just works", "designed for", "built by developers"
+
+**Words we avoid**:
+- Enterprise-grade, best-in-class, revolutionary, game-changing
+- Anything that sounds like marketing fluff

package/bundled-skills/developer-audience-context/references/template.md

@@ -0,0 +1,152 @@
+# Developer Audience Context
+
+Last updated: [DATE]
+
+---
+
+## Product Overview
+
+| Field | Value |
+|-------|-------|
+| **Product name** | |
+| **One-liner** | We help [developers] do [X] without [Y] |
+| **Category** | API / SDK / CLI / SaaS / Open source library / Infrastructure |
+| **Core technology** | |
+| **Pricing model** | Free / Open source / Freemium / Usage-based / Seat-based |
+
+---
+
+## Developer Persona
+
+| Field | Value |
+|-------|-------|
+| **Primary role** | Backend / Frontend / Full-stack / DevOps / Data / ML / Mobile |
+| **Seniority** | Junior / Mid / Senior / Staff / Lead / Architect |
+| **Company size** | Solo / Startup / Scale-up / Enterprise |
+| **Industry verticals** | |
+| **Tech stack** | |
+| **Decision authority** | Individual contributor / Team lead / Buyer / Influencer |
+
+**Day-in-the-life**:
+> [Describe your ideal developer's typical day and challenges]
+
+---
+
+## Where They Hang Out
+
+| Channel | Specific places |
+|---------|-----------------|
+| **Reddit** | r/ |
+| **Discord/Slack** | |
+| **Twitter/X** | # hashtags, @accounts |
+| **Newsletters** | |
+| **Podcasts** | |
+| **Blogs** | |
+| **Conferences** | |
+| **GitHub** | Topics: |
+| **Stack Overflow** | Tags: |
+
+---
+
+## Problems & Pain Points
+
+### Functional problems
+- [ ]
+
+### Emotional pain
+- [ ]
+
+### Trigger moments
+- [ ]
+
+**#1 frustration that brings developers to us**:
+>
+
+---
+
+## Current Alternatives
+
+| Alternative | Why devs choose it | What's frustrating | Switching triggers |
+|-------------|-------------------|-------------------|-------------------|
+| | | | |
+| | | | |
+| Build it themselves | | | |
+| Do nothing | | | |
+
+---
+
+## Key Differentiators
+
+| Type | Our claim | Proof |
+|------|-----------|-------|
+| **Technical** | | |
+| **DX** | | |
+| **Ecosystem** | | |
+| **Philosophy** | | |
+
+---
+
+## Verbatim Developer Language
+
+### How they describe the problem
+>
+
+### How they describe our product
+>
+
+### Common objections
+>
+
+### Praise / testimonials
+>
+
+**Sources**: GitHub issues, Twitter, Hacker News, support tickets, sales calls
+
+---
+
+## Technical Trust Signals
+
+| Signal | Current value |
+|--------|---------------|
+| **GitHub stars** | |
+| **npm/PyPI downloads** | |
+| **Docker pulls** | |
+| **Contributors** | |
+| **Community size** | Discord: / Slack: |
+| **Notable users** | |
+| **Backed by** | |
+
+---
+
+## Conversion Actions
+
+| Stage | Primary action | Secondary actions |
+|-------|---------------|-------------------|
+| **Awareness** | | |
+| **Consideration** | | |
+| **Trial** | | |
+| **Activation** | | |
+| **Conversion** | | |
+
+**"Hello World" moment**:
+> [What's the moment developers feel they've succeeded?]
+
+---
+
+## Voice & Tone
+
+| Dimension | Our position (1-5) |
+|-----------|-------------------|
+| Casual ← → Professional | |
+| Accessible ← → Deep technical | |
+| Neutral ← → Opinionated | |
+| Serious ← → Playful | |
+
+**Voice inspiration** (brands/people to emulate):
+-
+
+**Words we use**:
+-
+
+**Words we avoid**:
+-

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

@@ -0,0 +1,80 @@
+# developer-churn
+
+**Why developers leave and how to win them back** — understanding, preventing, and recovering from churn.
+
+## What It Does
+
+Helps you understand the real reasons developers churn, build early warning systems to identify at-risk users, conduct effective exit interviews, and run win-back campaigns that respect developer intelligence.
+
+## When to Use
+
+- Churn rate is higher than you'd like
+- Need to understand why developers are leaving
+- Building an at-risk user detection system
+- Creating win-back campaigns
+- When you say "why developers leave," "churn rate," "at-risk users," or "win-back"
+
+## Quick Start
+
+```
+/developer-churn
+
+Help me understand why developers are churning from our API product.
+We've had 15% churn last month and I need to figure out the causes.
+```
+
+## The 6 Reasons Developers Churn
+
+| Reason | Actionable? | Your Move |
+|--------|-------------|-----------|
+| DX Issues | Yes | Fix docs, SDKs, quickstarts |
+| Pricing Friction | Yes | Adjust pricing, add free tier |
+| Superior Alternatives | Partially | Compete on value, not FUD |
+| Project Death | No | Accept it, move on |
+| Integration Failure | Yes | Add integrations, improve guides |
+| Involuntary (Payment) | Yes | Better dunning, card updater |
+
+## Key Principles
+
+1. **Developers don't leave because of price — they leave because of friction**
+2. **Support tickets are warning signs, not engagement**
+3. **Don't try to win back project-death churners**
+4. **Lead with value in win-back, not discounts**
+5. **Fix involuntary churn first — it's often 20-40% of total**
+
+## Files
+
+| File | Description |
+|------|-------------|
+| `SKILL.md` | Full skill instructions |
+
+## At-Risk Detection
+
+Build a health score from:
+- API call trends (30%)
+- Login frequency (20%)
+- Feature adoption (20%)
+- Support sentiment (15%)
+- Billing health (15%)
+
+## Templates Included
+
+- Exit survey email
+- Exit interview questions
+- Win-back sequence (3 emails)
+- Dunning sequence (4 emails)
+- At-risk alert format
+
+## Tools
+
+- **[Octolens](https://octolens.com)** — Monitor competitor switches and developer sentiment
+- **Segment** — Usage tracking for health scores
+- **Amplitude** — Cohort retention analysis
+- **Stripe** — Dunning management
+
+## Related Skills
+
+- `developer-audience-context` — Understand alternatives
+- `developer-email-sequences` — Re-engagement emails
+- `competitor-tracking` — Monitor competitive landscape
+- `developer-onboarding` — Prevent churn at the source