[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4PXTRJBWJGD9EM5CDPYA1":3,"skill-same:01M7A4PXTRJBWJGD9EM5CDPYA1":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A4PXTRJBWJGD9EM5CDPYA1","devrel-content",null,"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...","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdevrel-content\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: devrel-content\ndescription: 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...\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdevrel-content\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# DevRel Content\n## When to Use\n\nUse 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...\n\n\nThis skill helps you create technical content that developers actually read: blog posts, tutorials, documentation, and thought leadership pieces that build trust and drive adoption.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Who you're writing for (role, seniority, tech stack)\n- Their pain points (what problems resonate)\n- Verbatim language (how they describe things)\n- Voice & tone (how formal\u002Ftechnical to be)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## The DevRel Content Framework\n\n### Phase 1: Research & Validation\n\nBefore writing anything, validate the topic is worth writing about.\n\n| Research Type | What to Do |\n|--------------|------------|\n| **Search intent** | Google your topic. What already ranks? What's missing? |\n| **Community signals** | Search Reddit, HN, Stack Overflow. Are developers asking about this? |\n| **Competitor gaps** | What have competitors written? What haven't they covered? |\n| **Internal data** | Support tickets, Discord questions, GitHub issues about this topic |\n| **Keyword research** | Use Ahrefs\u002FSEMrush for search volume on technical terms |\n\n**Red flags** — Don't write if:\n- You're the only one who cares about this topic\n- 10 identical articles already exist\n- The topic is too broad (\"Introduction to JavaScript\")\n- The topic is too narrow (no search volume, no community interest)\n\n### Phase 2: Content Type Selection\n\nChoose the right format for your goal:\n\n| Content Type | Best For | Structure |\n|-------------|----------|-----------|\n| **Tutorial** | Teaching a specific skill | Step-by-step, code-heavy |\n| **Guide** | Covering a topic comprehensively | Sections, reference material |\n| **Comparison** | Helping with decisions | Table-based, pros\u002Fcons |\n| **Announcement** | Launching features\u002Fproducts | News lead, what\u002Fwhy\u002Fhow |\n| **Thought leadership** | Building authority | Opinion, predictions, takes |\n| **Case study** | Social proof | Problem → Solution → Results |\n| **Troubleshooting** | Solving specific errors | Error → Cause → Fix |\n\n### Phase 3: Outline Structure\n\nUse this outline template:\n\n```markdown\n# [Title that promises specific value]\n\n## Hook (2-3 sentences)\n- State the problem or opportunity\n- Establish credibility (\"We migrated 10,000 repos...\")\n- Promise what the reader will learn\n\n## Context (optional)\n- Brief background if needed\n- Link to prerequisites\n\n## The Meat\n### Section 1: [First major concept]\n- Explanation\n- Code example\n- Common pitfall\n\n### Section 2: [Second major concept]\n- Explanation\n- Code example\n- Real-world application\n\n### Section 3: [Third major concept]\n- Explanation\n- Code example\n- Advanced tip\n\n## Putting It Together\n- Complete example\n- Working code\n\n## What's Next\n- Links to deeper content\n- Call to action (try the product, join Discord, etc.)\n```\n\n---\n\n## Writing Code Examples\n\nCode is the content. Get it right.\n\n### The Copy-Paste Test\n\nEvery code example must:\n\n| Requirement | Why It Matters |\n|------------|----------------|\n| **Run without modification** | Developers will copy-paste. If it fails, you lose trust. |\n| **Include imports** | Don't assume they know which libraries to import. |\n| **Show output** | What should they see when it works? |\n| **Handle errors** | Real code has error handling. Show it. |\n| **Use real values** | No `foo`, `bar`, `example.com` unless necessary. |\n\n### Code Example Structure\n\n```markdown\nFirst, install the dependencies:\n\n\\`\\`\\`bash\nnpm install your-library axios\n\\`\\`\\`\n\nNow create a file called `fetch-data.js`:\n\n\\`\\`\\`javascript\n\u002F\u002F fetch-data.js\nimport { Client } from 'your-library';\nimport axios from 'axios';\n\nconst client = new Client({\n  apiKey: process.env.YOUR_API_KEY \u002F\u002F Use environment variables\n});\n\nasync function fetchUserData(userId) {\n  try {\n    const user = await client.users.get(userId);\n    console.log(`Fetched user: ${user.name}`);\n    return user;\n  } catch (error) {\n    console.error(`Failed to fetch user: ${error.message}`);\n    throw error;\n  }\n}\n\n\u002F\u002F Example usage\nfetchUserData('user_123')\n  .then(user => console.log(user))\n  .catch(err => process.exit(1));\n\\`\\`\\`\n\nRun it:\n\n\\`\\`\\`bash\nYOUR_API_KEY=sk_test_xxx node fetch-data.js\n\\`\\`\\`\n\nExpected output:\n\n\\`\\`\\`\nFetched user: Jane Developer\n{ id: 'user_123', name: 'Jane Developer', email: 'jane@example.dev' }\n\\`\\`\\`\n```\n\n### Language-Specific Conventions\n\n| Language | Code Block | Package Install | Env Vars |\n|----------|-----------|-----------------|----------|\n| JavaScript\u002FNode | `javascript` or `js` | `npm install` | `process.env.VAR` |\n| TypeScript | `typescript` or `ts` | `npm install` | `process.env.VAR` |\n| Python | `python` or `py` | `pip install` | `os.environ['VAR']` |\n| Go | `go` | `go get` | `os.Getenv(\"VAR\")` |\n| Rust | `rust` | `cargo add` | `std::env::var(\"VAR\")` |\n| Shell | `bash` or `shell` | N\u002FA | `$VAR` |\n\n---\n\n## Technical Accuracy Checklist\n\nRun through before publishing:\n\n| Check | How to Verify |\n|-------|---------------|\n| **Code runs** | Copy-paste every snippet and run it |\n| **Versions match** | Are you using the current library version? |\n| **Links work** | Click every link |\n| **Commands work** | Run every CLI command |\n| **Screenshots current** | Do UI screenshots match the current product? |\n| **No deprecated APIs** | Check if any APIs used are deprecated |\n| **Security review** | No hardcoded secrets, SQL injection, etc. |\n| **Peer review** | Have an engineer read it for accuracy |\n\n---\n\n## SEO for Developer Content\n\nDevelopers use Google differently than consumers.\n\n### Developer Search Patterns\n\n| Pattern | Example Searches |\n|---------|-----------------|\n| **Error messages** | \"TypeError: Cannot read property 'map' of undefined\" |\n| **How to** | \"how to deploy next.js to vercel\" |\n| **Comparison** | \"prisma vs typeorm 2024\" |\n| **Best practices** | \"typescript project structure best practices\" |\n| **Alternatives** | \"alternatives to firebase\" |\n| **With** | \"react with typescript tutorial\" |\n\n### Technical SEO Checklist\n\n| Element | Best Practice |\n|---------|--------------|\n| **Title** | Include primary keyword, framework names, year if relevant |\n| **Meta description** | 150 chars, include keyword, promise specific outcome |\n| **H1** | Match or closely match title |\n| **H2s** | Include secondary keywords, make scannable |\n| **Code blocks** | Use proper syntax highlighting (helps featured snippets) |\n| **Internal links** | Link to related docs, tutorials, API reference |\n| **External links** | Link to official docs of tools mentioned |\n| **URL slug** | Lowercase, hyphens, include keyword |\n\n### Example Optimized Title\n\n| Bad | Good |\n|-----|------|\n| \"Using Our API\" | \"How to Authenticate with the YourProduct API (Node.js)\" |\n| \"Database Guide\" | \"PostgreSQL Connection Pooling: Complete Guide with pgBouncer\" |\n| \"Getting Started\" | \"Getting Started with YourProduct: Your First API Call in 5 Minutes\" |\n\n---\n\n## Content Quality Signals\n\nWhat separates great devrel content from mediocre:\n\n### Do This\n\n- **Show, don't tell** — Code over prose\n- **Address the \"why\"** — Not just how to do it, but when and why\n- **Acknowledge tradeoffs** — Nothing is perfect; developers respect honesty\n- **Link to sources** — Official docs, RFCs, related articles\n- **Include dates** — \"Updated March 2024\" or version numbers\n- **Progressive disclosure** — Start simple, add complexity\n- **Real examples** — Production scenarios, not just hello world\n\n### Don't Do This\n\n- **Wall of text** — Break up with code, headers, bullets\n- **Marketing speak** — \"Best-in-class,\" \"seamless,\" \"revolutionary\"\n- **Assuming knowledge** — Define acronyms, link to prerequisites\n- **Outdated content** — Nothing worse than a 2019 tutorial with deprecated APIs\n- **Buried lede** — Put the answer first, explanation second\n- **No code** — Developers came for code, not prose\n\n---\n\n## Content Templates\n\n### Blog Post Template\n\n```markdown\n# [Specific, keyword-rich title]\n\n[2-3 sentence hook: problem + promise]\n\n## The Problem\n\n[1 paragraph explaining the pain point]\n\n## The Solution\n\n[Brief explanation of your approach]\n\n### Step 1: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n### Step 2: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n### Step 3: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n## Complete Example\n\n\\`\\`\\`language\n\u002F\u002F Full working code\n\\`\\`\\`\n\n## Troubleshooting\n\n### [Common Error 1]\n[Solution]\n\n### [Common Error 2]\n[Solution]\n\n## What's Next\n\n- [Link to deeper dive]\n- [Link to related tutorial]\n- [CTA: Try it yourself]\n```\n\n### Comparison Post Template\n\n```markdown\n# [Tool A] vs [Tool B]: [Specific Use Case] ([Year])\n\n[1 paragraph: Who this comparison is for and what you'll learn]\n\n## Quick Comparison\n\n| Feature | Tool A | Tool B |\n|---------|--------|--------|\n| [Feature 1] | | |\n| [Feature 2] | | |\n| [Feature 3] | | |\n\n## When to Choose [Tool A]\n\n- [Scenario 1]\n- [Scenario 2]\n- [Scenario 3]\n\n## When to Choose [Tool B]\n\n- [Scenario 1]\n- [Scenario 2]\n- [Scenario 3]\n\n## Deep Dive: [Specific Aspect]\n\n### Tool A Approach\n[Explanation + code]\n\n### Tool B Approach\n[Explanation + code]\n\n## Our Recommendation\n\n[Specific guidance based on use case]\n```\n\n---\n\n## Measuring Content Success\n\n### Metrics to Track\n\n| Metric | What It Tells You |\n|--------|------------------|\n| **Page views** | Reach (but vanity without context) |\n| **Time on page** | Engagement (are they reading?) |\n| **Scroll depth** | Did they read to the end? |\n| **Bounce rate** | Did they find what they needed? |\n| **Search rankings** | SEO performance |\n| **Backlinks** | Authority and reference value |\n| **Social shares** | Resonance (especially HN, Twitter, Reddit) |\n| **Conversion events** | Sign-ups, installs, docs clicks |\n\n### Content → Conversion Path\n\nTrack the journey:\n1. Search\u002Fsocial → Blog post\n2. Blog post → Docs \u002F quickstart\n3. Docs → Sign up \u002F install\n4. Sign up → Activation (first success)\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor where your content gets shared (HN, Reddit, Twitter). Track competitor content performance. Find content ideas from developer conversations. |\n| **Grammarly \u002F Hemingway** | Readability and grammar checking |\n| **Carbon \u002F Ray.so** | Beautiful code screenshots |\n| **Excalidraw** | Technical diagrams |\n| **Loom** | Quick video walkthroughs |\n| **Ahrefs \u002F SEMrush** | Keyword research and SEO tracking |\n| **Google Search Console** | Track search performance |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Foundation for knowing your readers\n- `technical-tutorials` — Deep dive into step-by-step content\n- `developer-newsletter` — Distributing content via email\n- `developer-seo` — Technical SEO optimization\n- `hacker-news-strategy` — Sharing content on HN effectively\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# DevRel Content\n## When to Use\n\nUse 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...\n\n\nThis skill helps you create technical content that developers actually read: blog posts, tutorials, documentation, and thought leadership pieces that build trust and drive adoption.\n\n---\n\n## Before You Start\n\n**Load your audience context first.** Read `.agents\u002Fdeveloper-audience-context.md` to understand:\n\n- Who you're writing for (role, seniority, tech stack)\n- Their pain points (what problems resonate)\n- Verbatim language (how they describe things)\n- Voice & tone (how formal\u002Ftechnical to be)\n\nIf the context file doesn't exist, run the `developer-audience-context` skill first.\n\n---\n\n## The DevRel Content Framework\n\n### Phase 1: Research & Validation\n\nBefore writing anything, validate the topic is worth writing about.\n\n| Research Type | What to Do |\n|--------------|------------|\n| **Search intent** | Google your topic. What already ranks? What's missing? |\n| **Community signals** | Search Reddit, HN, Stack Overflow. Are developers asking about this? |\n| **Competitor gaps** | What have competitors written? What haven't they covered? |\n| **Internal data** | Support tickets, Discord questions, GitHub issues about this topic |\n| **Keyword research** | Use Ahrefs\u002FSEMrush for search volume on technical terms |\n\n**Red flags** — Don't write if:\n- You're the only one who cares about this topic\n- 10 identical articles already exist\n- The topic is too broad (\"Introduction to JavaScript\")\n- The topic is too narrow (no search volume, no community interest)\n\n### Phase 2: Content Type Selection\n\nChoose the right format for your goal:\n\n| Content Type | Best For | Structure |\n|-------------|----------|-----------|\n| **Tutorial** | Teaching a specific skill | Step-by-step, code-heavy |\n| **Guide** | Covering a topic comprehensively | Sections, reference material |\n| **Comparison** | Helping with decisions | Table-based, pros\u002Fcons |\n| **Announcement** | Launching features\u002Fproducts | News lead, what\u002Fwhy\u002Fhow |\n| **Thought leadership** | Building authority | Opinion, predictions, takes |\n| **Case study** | Social proof | Problem → Solution → Results |\n| **Troubleshooting** | Solving specific errors | Error → Cause → Fix |\n\n### Phase 3: Outline Structure\n\nUse this outline template:\n\n```markdown\n# [Title that promises specific value]\n\n## Hook (2-3 sentences)\n- State the problem or opportunity\n- Establish credibility (\"We migrated 10,000 repos...\")\n- Promise what the reader will learn\n\n## Context (optional)\n- Brief background if needed\n- Link to prerequisites\n\n## The Meat\n### Section 1: [First major concept]\n- Explanation\n- Code example\n- Common pitfall\n\n### Section 2: [Second major concept]\n- Explanation\n- Code example\n- Real-world application\n\n### Section 3: [Third major concept]\n- Explanation\n- Code example\n- Advanced tip\n\n## Putting It Together\n- Complete example\n- Working code\n\n## What's Next\n- Links to deeper content\n- Call to action (try the product, join Discord, etc.)\n```\n\n---\n\n## Writing Code Examples\n\nCode is the content. Get it right.\n\n### The Copy-Paste Test\n\nEvery code example must:\n\n| Requirement | Why It Matters |\n|------------|----------------|\n| **Run without modification** | Developers will copy-paste. If it fails, you lose trust. |\n| **Include imports** | Don't assume they know which libraries to import. |\n| **Show output** | What should they see when it works? |\n| **Handle errors** | Real code has error handling. Show it. |\n| **Use real values** | No `foo`, `bar`, `example.com` unless necessary. |\n\n### Code Example Structure\n\n```markdown\nFirst, install the dependencies:\n\n\\`\\`\\`bash\nnpm install your-library axios\n\\`\\`\\`\n\nNow create a file called `fetch-data.js`:\n\n\\`\\`\\`javascript\n\u002F\u002F fetch-data.js\nimport { Client } from 'your-library';\nimport axios from 'axios';\n\nconst client = new Client({\n  apiKey: process.env.YOUR_API_KEY \u002F\u002F Use environment variables\n});\n\nasync function fetchUserData(userId) {\n  try {\n    const user = await client.users.get(userId);\n    console.log(`Fetched user: ${user.name}`);\n    return user;\n  } catch (error) {\n    console.error(`Failed to fetch user: ${error.message}`);\n    throw error;\n  }\n}\n\n\u002F\u002F Example usage\nfetchUserData('user_123')\n  .then(user => console.log(user))\n  .catch(err => process.exit(1));\n\\`\\`\\`\n\nRun it:\n\n\\`\\`\\`bash\nYOUR_API_KEY=sk_test_xxx node fetch-data.js\n\\`\\`\\`\n\nExpected output:\n\n\\`\\`\\`\nFetched user: Jane Developer\n{ id: 'user_123', name: 'Jane Developer', email: 'jane@example.dev' }\n\\`\\`\\`\n```\n\n### Language-Specific Conventions\n\n| Language | Code Block | Package Install | Env Vars |\n|----------|-----------|-----------------|----------|\n| JavaScript\u002FNode | `javascript` or `js` | `npm install` | `process.env.VAR` |\n| TypeScript | `typescript` or `ts` | `npm install` | `process.env.VAR` |\n| Python | `python` or `py` | `pip install` | `os.environ['VAR']` |\n| Go | `go` | `go get` | `os.Getenv(\"VAR\")` |\n| Rust | `rust` | `cargo add` | `std::env::var(\"VAR\")` |\n| Shell | `bash` or `shell` | N\u002FA | `$VAR` |\n\n---\n\n## Technical Accuracy Checklist\n\nRun through before publishing:\n\n| Check | How to Verify |\n|-------|---------------|\n| **Code runs** | Copy-paste every snippet and run it |\n| **Versions match** | Are you using the current library version? |\n| **Links work** | Click every link |\n| **Commands work** | Run every CLI command |\n| **Screenshots current** | Do UI screenshots match the current product? |\n| **No deprecated APIs** | Check if any APIs used are deprecated |\n| **Security review** | No hardcoded secrets, SQL injection, etc. |\n| **Peer review** | Have an engineer read it for accuracy |\n\n---\n\n## SEO for Developer Content\n\nDevelopers use Google differently than consumers.\n\n### Developer Search Patterns\n\n| Pattern | Example Searches |\n|---------|-----------------|\n| **Error messages** | \"TypeError: Cannot read property 'map' of undefined\" |\n| **How to** | \"how to deploy next.js to vercel\" |\n| **Comparison** | \"prisma vs typeorm 2024\" |\n| **Best practices** | \"typescript project structure best practices\" |\n| **Alternatives** | \"alternatives to firebase\" |\n| **With** | \"react with typescript tutorial\" |\n\n### Technical SEO Checklist\n\n| Element | Best Practice |\n|---------|--------------|\n| **Title** | Include primary keyword, framework names, year if relevant |\n| **Meta description** | 150 chars, include keyword, promise specific outcome |\n| **H1** | Match or closely match title |\n| **H2s** | Include secondary keywords, make scannable |\n| **Code blocks** | Use proper syntax highlighting (helps featured snippets) |\n| **Internal links** | Link to related docs, tutorials, API reference |\n| **External links** | Link to official docs of tools mentioned |\n| **URL slug** | Lowercase, hyphens, include keyword |\n\n### Example Optimized Title\n\n| Bad | Good |\n|-----|------|\n| \"Using Our API\" | \"How to Authenticate with the YourProduct API (Node.js)\" |\n| \"Database Guide\" | \"PostgreSQL Connection Pooling: Complete Guide with pgBouncer\" |\n| \"Getting Started\" | \"Getting Started with YourProduct: Your First API Call in 5 Minutes\" |\n\n---\n\n## Content Quality Signals\n\nWhat separates great devrel content from mediocre:\n\n### Do This\n\n- **Show, don't tell** — Code over prose\n- **Address the \"why\"** — Not just how to do it, but when and why\n- **Acknowledge tradeoffs** — Nothing is perfect; developers respect honesty\n- **Link to sources** — Official docs, RFCs, related articles\n- **Include dates** — \"Updated March 2024\" or version numbers\n- **Progressive disclosure** — Start simple, add complexity\n- **Real examples** — Production scenarios, not just hello world\n\n### Don't Do This\n\n- **Wall of text** — Break up with code, headers, bullets\n- **Marketing speak** — \"Best-in-class,\" \"seamless,\" \"revolutionary\"\n- **Assuming knowledge** — Define acronyms, link to prerequisites\n- **Outdated content** — Nothing worse than a 2019 tutorial with deprecated APIs\n- **Buried lede** — Put the answer first, explanation second\n- **No code** — Developers came for code, not prose\n\n---\n\n## Content Templates\n\n### Blog Post Template\n\n```markdown\n# [Specific, keyword-rich title]\n\n[2-3 sentence hook: problem + promise]\n\n## The Problem\n\n[1 paragraph explaining the pain point]\n\n## The Solution\n\n[Brief explanation of your approach]\n\n### Step 1: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n### Step 2: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n### Step 3: [Action]\n\n[Explanation]\n\n\\`\\`\\`language\n\u002F\u002F Code\n\\`\\`\\`\n\n## Complete Example\n\n\\`\\`\\`language\n\u002F\u002F Full working code\n\\`\\`\\`\n\n## Troubleshooting\n\n### [Common Error 1]\n[Solution]\n\n### [Common Error 2]\n[Solution]\n\n## What's Next\n\n- [Link to deeper dive]\n- [Link to related tutorial]\n- [CTA: Try it yourself]\n```\n\n### Comparison Post Template\n\n```markdown\n# [Tool A] vs [Tool B]: [Specific Use Case] ([Year])\n\n[1 paragraph: Who this comparison is for and what you'll learn]\n\n## Quick Comparison\n\n| Feature | Tool A | Tool B |\n|---------|--------|--------|\n| [Feature 1] | | |\n| [Feature 2] | | |\n| [Feature 3] | | |\n\n## When to Choose [Tool A]\n\n- [Scenario 1]\n- [Scenario 2]\n- [Scenario 3]\n\n## When to Choose [Tool B]\n\n- [Scenario 1]\n- [Scenario 2]\n- [Scenario 3]\n\n## Deep Dive: [Specific Aspect]\n\n### Tool A Approach\n[Explanation + code]\n\n### Tool B Approach\n[Explanation + code]\n\n## Our Recommendation\n\n[Specific guidance based on use case]\n```\n\n---\n\n## Measuring Content Success\n\n### Metrics to Track\n\n| Metric | What It Tells You |\n|--------|------------------|\n| **Page views** | Reach (but vanity without context) |\n| **Time on page** | Engagement (are they reading?) |\n| **Scroll depth** | Did they read to the end? |\n| **Bounce rate** | Did they find what they needed? |\n| **Search rankings** | SEO performance |\n| **Backlinks** | Authority and reference value |\n| **Social shares** | Resonance (especially HN, Twitter, Reddit) |\n| **Conversion events** | Sign-ups, installs, docs clicks |\n\n### Content → Conversion Path\n\nTrack the journey:\n1. Search\u002Fsocial → Blog post\n2. Blog post → Docs \u002F quickstart\n3. Docs → Sign up \u002F install\n4. Sign up → Activation (first success)\n\n---\n\n## Tools\n\n| Tool | Use Case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor where your content gets shared (HN, Reddit, Twitter). Track competitor content performance. Find content ideas from developer conversations. |\n| **Grammarly \u002F Hemingway** | Readability and grammar checking |\n| **Carbon \u002F Ray.so** | Beautiful code screenshots |\n| **Excalidraw** | Technical diagrams |\n| **Loom** | Quick video walkthroughs |\n| **Ahrefs \u002F SEMrush** | Keyword research and SEO tracking |\n| **Google Search Console** | Track search performance |\n\n---\n\n## Related Skills\n\n- `developer-audience-context` — Foundation for knowing your readers\n- `technical-tutorials` — Deep dive into step-by-step content\n- `developer-newsletter` — Distributing content via email\n- `developer-seo` — Technical SEO optimization\n- `hacker-news-strategy` — Sharing content on HN effectively\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdevrel-content",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdevrel-content",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill devrel-content",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill devrel-content",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill devrel-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdevrel-content\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",2202,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fdevrel-content\u002FREADME.md",[60,67,74,81,90,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]