Skip to content
Skillpedia
Writing48k · #2839

devrel-content

Helps your agent create technical content for developers. It produces articles, tutorials, and documentation that explain concepts and features.

What it does

This tool helps create technical content for developers, like blog posts, tutorials, and documentation. It guides you through researching, choosing a format, and structuring the content, ensuring it's accurate and useful for the audience.

When to use it

  • ✓When you need to write a technical tutorial.
  • ✓While creating product documentation for developers.
  • ✓To draft a blog post about a programming topic.

Example of what to ask your AI

“Write a tutorial on how to use the X API to authenticate users.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/devrel-content/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/devrel-content/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

First, it helps research and validate your topic to ensure there's interest. Then, you choose the best format (tutorial, guide, etc.) and use a template to structure the content, including working code examples.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill devrel-content

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/devrel-content/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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:

# [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

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')

…
FAQ

What is 'DevRel Content'?

DevRel Content stands for Developer Relations Content. It's material created to help and engage the developer community, such as tutorials and documentation.

How do I know if my topic is good?

Check if developers are searching for it (Google, Reddit), if there are gaps in existing content, and if the topic isn't too broad or too narrow.

Why do code examples need to work perfectly?

Developers copy and paste code. If an example doesn't work immediately, they lose trust and might stop using the product or learning about the topic.

Details

Original description by the author

When the user wants to create technical content for developers including blog posts, tutorials, and documentation.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2839
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills