opencode-skills-collection 3.1.11 → 3.1.13

package/bundled-skills/devrel-content/SKILL.md

@@ -0,0 +1,428 @@
+---
+name: devrel-content
+description: When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for...
+risk: unknown
+source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/devrel-content
+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
+---
+
+# DevRel Content
+## When to Use
+
+Use this skill when you need when the user wants to create technical content for developers including blog posts, tutorials, and documentation. Trigger phrases include "write a blog post," "technical article," "developer content," "tutorial," "devrel content," "dev blog," "technical writing," or "content for...
+
+
+This skill helps you create technical content that developers actually read: blog posts, tutorials, documentation, and thought leadership pieces that build trust and drive adoption.
+
+---
+
+## 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)
+- Their pain points (what problems resonate)
+- Verbatim language (how they describe things)
+- Voice & tone (how formal/technical to be)
+
+If the context file doesn't exist, run the `developer-audience-context` skill first.
+
+---
+
+## The DevRel Content Framework
+
+### Phase 1: Research & Validation
+
+Before writing anything, validate the topic is worth writing about.
+
+| Research Type | What to Do |
+|--------------|------------|
+| **Search intent** | Google your topic. What already ranks? What's missing? |
+| **Community signals** | Search Reddit, HN, Stack Overflow. Are developers asking about this? |
+| **Competitor gaps** | What have competitors written? What haven't they covered? |
+| **Internal data** | Support tickets, Discord questions, GitHub issues about this topic |
+| **Keyword research** | Use Ahrefs/SEMrush for search volume on technical terms |
+
+**Red flags** — Don't write if:
+- You're the only one who cares about this topic
+- 10 identical articles already exist
+- The topic is too broad ("Introduction to JavaScript")
+- The topic is too narrow (no search volume, no community interest)
+
+### Phase 2: Content Type Selection
+
+Choose the right format for your goal:
+
+| Content Type | Best For | Structure |
+|-------------|----------|-----------|
+| **Tutorial** | Teaching a specific skill | Step-by-step, code-heavy |
+| **Guide** | Covering a topic comprehensively | Sections, reference material |
+| **Comparison** | Helping with decisions | Table-based, pros/cons |
+| **Announcement** | Launching features/products | News lead, what/why/how |
+| **Thought leadership** | Building authority | Opinion, predictions, takes |
+| **Case study** | Social proof | Problem → Solution → Results |
+| **Troubleshooting** | Solving specific errors | Error → Cause → Fix |
+
+### Phase 3: Outline Structure
+
+Use this outline template:
+
+```markdown
+# [Title that promises specific value]
+
+## Hook (2-3 sentences)
+- State the problem or opportunity
+- Establish credibility ("We migrated 10,000 repos...")
+- Promise what the reader will learn
+
+## Context (optional)
+- Brief background if needed
+- Link to prerequisites
+
+## The Meat
+### Section 1: [First major concept]
+- Explanation
+- Code example
+- Common pitfall
+
+### Section 2: [Second major concept]
+- Explanation
+- Code example
+- Real-world application
+
+### Section 3: [Third major concept]
+- Explanation
+- Code example
+- Advanced tip
+
+## Putting It Together
+- Complete example
+- Working code
+
+## What's Next
+- Links to deeper content
+- Call to action (try the product, join Discord, etc.)
+```
+
+---
+
+## Writing Code Examples
+
+Code is the content. Get it right.
+
+### The Copy-Paste Test
+
+Every code example must:
+
+| Requirement | Why It Matters |
+|------------|----------------|
+| **Run without modification** | Developers will copy-paste. If it fails, you lose trust. |
+| **Include imports** | Don't assume they know which libraries to import. |
+| **Show output** | What should they see when it works? |
+| **Handle errors** | Real code has error handling. Show it. |
+| **Use real values** | No `foo`, `bar`, `example.com` unless necessary. |
+
+### Code Example Structure
+
+```markdown
+First, install the dependencies:
+
+\`\`\`bash
+npm install your-library axios
+\`\`\`
+
+Now create a file called `fetch-data.js`:
+
+\`\`\`javascript
+// fetch-data.js
+import { Client } from 'your-library';
+import axios from 'axios';
+
+const client = new Client({
+  apiKey: process.env.YOUR_API_KEY // Use environment variables
+});
+
+async function fetchUserData(userId) {
+  try {
+    const user = await client.users.get(userId);
+    console.log(`Fetched user: ${user.name}`);
+    return user;
+  } catch (error) {
+    console.error(`Failed to fetch user: ${error.message}`);
+    throw error;
+  }
+}
+
+// Example usage
+fetchUserData('user_123')
+  .then(user => console.log(user))
+  .catch(err => process.exit(1));
+\`\`\`
+
+Run it:
+
+\`\`\`bash
+YOUR_API_KEY=sk_test_xxx node fetch-data.js
+\`\`\`
+
+Expected output:
+
+\`\`\`
+Fetched user: Jane Developer
+{ id: 'user_123', name: 'Jane Developer', email: 'jane@example.dev' }
+\`\`\`
+```
+
+### Language-Specific Conventions
+
+| Language | Code Block | Package Install | Env Vars |
+|----------|-----------|-----------------|----------|
+| JavaScript/Node | `javascript` or `js` | `npm install` | `process.env.VAR` |
+| TypeScript | `typescript` or `ts` | `npm install` | `process.env.VAR` |
+| Python | `python` or `py` | `pip install` | `os.environ['VAR']` |
+| Go | `go` | `go get` | `os.Getenv("VAR")` |
+| Rust | `rust` | `cargo add` | `std::env::var("VAR")` |
+| Shell | `bash` or `shell` | N/A | `$VAR` |
+
+---
+
+## Technical Accuracy Checklist
+
+Run through before publishing:
+
+| Check | How to Verify |
+|-------|---------------|
+| **Code runs** | Copy-paste every snippet and run it |
+| **Versions match** | Are you using the current library version? |
+| **Links work** | Click every link |
+| **Commands work** | Run every CLI command |
+| **Screenshots current** | Do UI screenshots match the current product? |
+| **No deprecated APIs** | Check if any APIs used are deprecated |
+| **Security review** | No hardcoded secrets, SQL injection, etc. |
+| **Peer review** | Have an engineer read it for accuracy |
+
+---
+
+## SEO for Developer Content
+
+Developers use Google differently than consumers.
+
+### Developer Search Patterns
+
+| Pattern | Example Searches |
+|---------|-----------------|
+| **Error messages** | "TypeError: Cannot read property 'map' of undefined" |
+| **How to** | "how to deploy next.js to vercel" |
+| **Comparison** | "prisma vs typeorm 2024" |
+| **Best practices** | "typescript project structure best practices" |
+| **Alternatives** | "alternatives to firebase" |
+| **With** | "react with typescript tutorial" |
+
+### Technical SEO Checklist
+
+| Element | Best Practice |
+|---------|--------------|
+| **Title** | Include primary keyword, framework names, year if relevant |
+| **Meta description** | 150 chars, include keyword, promise specific outcome |
+| **H1** | Match or closely match title |
+| **H2s** | Include secondary keywords, make scannable |
+| **Code blocks** | Use proper syntax highlighting (helps featured snippets) |
+| **Internal links** | Link to related docs, tutorials, API reference |
+| **External links** | Link to official docs of tools mentioned |
+| **URL slug** | Lowercase, hyphens, include keyword |
+
+### Example Optimized Title
+
+| Bad | Good |
+|-----|------|
+| "Using Our API" | "How to Authenticate with the YourProduct API (Node.js)" |
+| "Database Guide" | "PostgreSQL Connection Pooling: Complete Guide with pgBouncer" |
+| "Getting Started" | "Getting Started with YourProduct: Your First API Call in 5 Minutes" |
+
+---
+
+## Content Quality Signals
+
+What separates great devrel content from mediocre:
+
+### Do This
+
+- **Show, don't tell** — Code over prose
+- **Address the "why"** — Not just how to do it, but when and why
+- **Acknowledge tradeoffs** — Nothing is perfect; developers respect honesty
+- **Link to sources** — Official docs, RFCs, related articles
+- **Include dates** — "Updated March 2024" or version numbers
+- **Progressive disclosure** — Start simple, add complexity
+- **Real examples** — Production scenarios, not just hello world
+
+### Don't Do This
+
+- **Wall of text** — Break up with code, headers, bullets
+- **Marketing speak** — "Best-in-class," "seamless," "revolutionary"
+- **Assuming knowledge** — Define acronyms, link to prerequisites
+- **Outdated content** — Nothing worse than a 2019 tutorial with deprecated APIs
+- **Buried lede** — Put the answer first, explanation second
+- **No code** — Developers came for code, not prose
+
+---
+
+## Content Templates
+
+### Blog Post Template
+
+```markdown
+# [Specific, keyword-rich title]
+
+[2-3 sentence hook: problem + promise]
+
+## The Problem
+
+[1 paragraph explaining the pain point]
+
+## The Solution
+
+[Brief explanation of your approach]
+
+### Step 1: [Action]
+
+[Explanation]
+
+\`\`\`language
+// Code
+\`\`\`
+
+### Step 2: [Action]
+
+[Explanation]
+
+\`\`\`language
+// Code
+\`\`\`
+
+### Step 3: [Action]
+
+[Explanation]
+
+\`\`\`language
+// Code
+\`\`\`
+
+## Complete Example
+
+\`\`\`language
+// Full working code
+\`\`\`
+
+## Troubleshooting
+
+### [Common Error 1]
+[Solution]
+
+### [Common Error 2]
+[Solution]
+
+## What's Next
+
+- [Link to deeper dive]
+- [Link to related tutorial]
+- [CTA: Try it yourself]
+```
+
+### Comparison Post Template
+
+```markdown
+# [Tool A] vs [Tool B]: [Specific Use Case] ([Year])
+
+[1 paragraph: Who this comparison is for and what you'll learn]
+
+## Quick Comparison
+
+| Feature | Tool A | Tool B |
+|---------|--------|--------|
+| [Feature 1] | | |
+| [Feature 2] | | |
+| [Feature 3] | | |
+
+## When to Choose [Tool A]
+
+- [Scenario 1]
+- [Scenario 2]
+- [Scenario 3]
+
+## When to Choose [Tool B]
+
+- [Scenario 1]
+- [Scenario 2]
+- [Scenario 3]
+
+## Deep Dive: [Specific Aspect]
+
+### Tool A Approach
+[Explanation + code]
+
+### Tool B Approach
+[Explanation + code]
+
+## Our Recommendation
+
+[Specific guidance based on use case]
+```
+
+---
+
+## Measuring Content Success
+
+### Metrics to Track
+
+| Metric | What It Tells You |
+|--------|------------------|
+| **Page views** | Reach (but vanity without context) |
+| **Time on page** | Engagement (are they reading?) |
+| **Scroll depth** | Did they read to the end? |
+| **Bounce rate** | Did they find what they needed? |
+| **Search rankings** | SEO performance |
+| **Backlinks** | Authority and reference value |
+| **Social shares** | Resonance (especially HN, Twitter, Reddit) |
+| **Conversion events** | Sign-ups, installs, docs clicks |
+
+### Content → Conversion Path
+
+Track the journey:
+1. Search/social → Blog post
+2. Blog post → Docs / quickstart
+3. Docs → Sign up / install
+4. Sign up → Activation (first success)
+
+---
+
+## Tools
+
+| Tool | Use Case |
+|------|----------|
+| **[Octolens](https://octolens.com)** | Monitor where your content gets shared (HN, Reddit, Twitter). Track competitor content performance. Find content ideas from developer conversations. |
+| **Grammarly / Hemingway** | Readability and grammar checking |
+| **Carbon / Ray.so** | Beautiful code screenshots |
+| **Excalidraw** | Technical diagrams |
+| **Loom** | Quick video walkthroughs |
+| **Ahrefs / SEMrush** | Keyword research and SEO tracking |
+| **Google Search Console** | Track search performance |
+
+---
+
+## Related Skills
+
+- `developer-audience-context` — Foundation for knowing your readers
+- `technical-tutorials` — Deep dive into step-by-step content
+- `developer-newsletter` — Distributing content via email
+- `developer-seo` — Technical SEO optimization
+- `hacker-news-strategy` — Sharing content on HN effectively
+
+## 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/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,700+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,891+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,700+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,891+ skills
 
 This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With 1,700+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,891+ skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -21,7 +21,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,700+ skills installed.
+This pattern avoids context overflow when you have 1,891+ skills installed.
 
 Manifest contract references:
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,700+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,891+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,700+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,891+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,700+ Agentic Skills`;
+- use a clean preview image that says `1,891+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,700+ skills from the skills directory
+- All 1,891+ skills from the skills directory
 
 ## When to Update
 

package/bundled-skills/docs/users/bundles.md

@@ -1061,4 +1061,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 1,700+ | Total Bundles: 59_
+_Last updated: June 2026 | Total Skills: 1,891+ | Total Bundles: 59_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,700+ skills instead of a narrow single-domain starter pack.
+- It includes 1,891+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/faq.md

@@ -411,7 +411,7 @@ Common fixes:
 
 ### My PR triggered the `skill-review` automated check. What is it?
 
-Since v8.0.0, GitHub automatically runs a `skill-review` workflow on any PR that adds or modifies a `SKILL.md` file. It reviews your skill against the quality bar and flags common issues — missing sections, weak triggers, or risky command patterns.
+Since v8.0.0, GitHub automatically runs a `skill-review` workflow on any PR that adds or modifies a `SKILL.md` file. It reviews your skill against the quality bar and flags common issues — missing sections, weak triggers, or risky command patterns. The workflow now uses Tessl Review; fork PRs may need maintainer manual review when GitHub withholds repository secrets.
 
 **If it reports findings:**
 

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,700+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,891+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Antigravity Awesome Skills (V13.5.0)
+# Getting Started with Antigravity Awesome Skills (V13.6.1)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,700+ specialized areas
+- **Domain expertise** across 1,891+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

package/bundled-skills/docs/users/usage.md

@@ -14,8 +14,8 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,700+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
-✅ **Made them available** to your AI assistant  
+✅ **Downloaded 1,891+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Made them available** to your AI assistant
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
 Think of it like installing a toolbox. You have all the tools now, but you need to **pick which ones to use** for each job.
@@ -34,13 +34,13 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,700+ tools (✅ done)
+- You installed a toolbox with 1,891+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
 ### What Bundles Are NOT
 
-❌ Separate skill downloads  
+❌ Separate skill downloads
 ❌ Invokable mega-skills like `@essentials` or `/web-wizard`
 ❌ Something most users need to activate during normal install
 ❌ A replacement for invoking the individual skills inside the bundle
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,700+ skills at once. Here's a sensible approach:
+Don't try to use all 1,891+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -257,7 +257,7 @@ Find your role in [bundles.md](bundles.md) and pick 5-10 skills from that bundle
 
 Keep the [CATALOG.md](../../CATALOG.md) open as reference. When you need something specific:
 
-> "I need to integrate Stripe payments"  
+> "I need to integrate Stripe payments"
 > → Search catalog → Find `@stripe-integration` → Use it!
 
 ---
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,700+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,891+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 
@@ -415,7 +415,7 @@ Now that you understand how to use skills:
 
 ### Tip 3: Be Specific in Prompts
 
-> Bad: "Use @react-patterns"  
+> Bad: "Use @react-patterns"
 > Good: "Use @react-patterns to build a modal component with animations"
 
 ### Tip 4: Reference File Paths

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ antigravity-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,700+ skills live here
+├── 📁 skills/                          ← 1,891+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,700+ total)
+│   └── ... (1,891+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,700+ SKILLS          │
+                    │  1,891+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,700+ total)                │
+│   └── ... (1,891+ total)                │
 └─────────────────────────────────────────┘
 ```
 
@@ -470,19 +470,19 @@ START HERE
 Day 1: Install skills
   │
   └─→ "Wow, @brainstorming helped me design my app!"
-  
+
 Day 3: Use 5 different skills
   │
   └─→ "These skills save me so much time!"
-  
+
 Week 1: Create first skill
   │
   └─→ "I shared my expertise as a skill!"
-  
+
 Week 2: Skill gets merged
   │
   └─→ "My skill is helping others! 🎉"
-  
+
 Month 1: Regular contributor
   │
   └─→ "I've contributed 5 skills and improved docs!"