[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P1NSAJS1JN6REY564XSTHY":3,"skill-same:01M6P1NSAJS1JN6REY564XSTHY":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":27,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":37,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6P1NSAJS1JN6REY564XSTHY","devrel-content",null,"When the user wants to create technical content for developers including blog posts, tutorials, and documentation.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdevrel-content\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"content","devrel","devrel content","community","for","tree","posts","critical","wed","main","github","user","technical","blog","https","license","create","documentation","2026-11-10 10:12:30",false,"---\nname: devrel-content\ndescription: \"When the user wants to create technical content for developers including blog posts, tutorials, and documentation.\"\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":35,"source":51,"license":14,"date_added":52,"description":7,"source_repo":53,"source_type":31,"license_source":54},"https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdevrel-content",1782864000000,"jonathimer\u002Fdevmarketing-skills","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fdevrel-content","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill devrel-content",{"tool":66,"command":67},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill devrel-content",{"tool":69,"command":70},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill devrel-content","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdevrel-content\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"README.md","REFERENCE","参考文档",2202,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdevrel-content\u002FREADME.md",[81,107,131,153,179,203],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":46},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[91,92,93,94,95,96,83,97,98,99,100,101,31,37,102,35,103,104,105,106],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":46},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[114,115,116,117,118,119,120,121,122,123,124,125,126,101,127,31,128,129,35,130],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":46},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[138,139,140,141,38,142,143,43,42,144,145,146,147,31,37,148,149,150,151,152],"transcript","youtube transcript","youtube","safe","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":168,"publishedAt":46},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[159,162,165],{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":163,"categoryName":164,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":166,"categoryName":167,"taxonomyType":25,"taxonomyTypeDesc":26},"01JBSEEDCAT000000000000030","开发工程师",[138,139,140,169,141,170,38,142,43,171,172,173,174,145,175,31,37,176,177,178],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":46},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":163,"categoryName":164,"taxonomyType":20,"taxonomyTypeDesc":21},[140,190,191,118,141,192,193,194,195,43,173,196,197,198,199,37,200,148,201,202],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":46},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[209],{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},[211,140,212,213,141,170,171,214,215,172,173,174,145,216,175,31,37,176,217,151],"youtube full","full","google","server","dlp","credits","automatic"]