Agent skill

Devrel Content

by sickn33 in sickn33/agentic-awesome-skills

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

MITAuto-check passedWriting & Content

Install Devrel Content

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills devrel-content --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/devrel-content .claude/skills/devrel-content && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
devrel-content
GitHub stars
47k
Used in
1 other repo
Token cost
~3k tokens
SKILL.md length
1,015 words
Files
2
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 3 steps: Research & Validation → Content Type Selection → Outline Structure
  • Wants to create technical content for developers including blog posts
  • SKILL.md covers When to Use, Before You Start, The DevRel Content Framework and Writing Code Examples, plus 8 more sections
  • Calls npm, pip and go

What it does

Devrel Content is an agent skill from sickn33/agentic-awesome-skills. When the user wants to create technical content for developers including blog posts, tutorials, and documentation.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Wants to create technical content for developers including blog posts
  • Tasks that involve Blog and article writing

Example prompts

  • “/devrel-content”

Requirements

  • Python 3
  • Node.js
  • A credential in YOUR_API_KEY

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Research & Validation
  2. Content Type Selection
  3. Outline Structure

What it can do on your machine

Read from SKILL.md and the folder at commit 1e53ce2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • pip
    • go
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • octolens.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Devrel Content loads about 3k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 1,015 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 1,015 words, ~3,013 tokens.

Download SKILL.mdSave it as .claude/skills/devrel-content/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
devrel-content
description
When the user wants to create technical content for developers including blog posts, tutorials, and documentation.
risk
critical
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 TypeWhat to Do
Search intentGoogle your topic. What already ranks? What's missing?
Community signalsSearch Reddit, HN, Stack Overflow. Are developers asking about this?
Competitor gapsWhat have competitors written? What haven't they covered?
Internal dataSupport tickets, Discord questions, GitHub issues about this topic
Keyword researchUse 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 TypeBest ForStructure
TutorialTeaching a specific skillStep-by-step, code-heavy
GuideCovering a topic comprehensivelySections, reference material
ComparisonHelping with decisionsTable-based, pros/cons
AnnouncementLaunching features/productsNews lead, what/why/how
Thought leadershipBuilding authorityOpinion, predictions, takes
Case studySocial proofProblem → Solution → Results
TroubleshootingSolving specific errorsError → 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:

RequirementWhy It Matters
Run without modificationDevelopers will copy-paste. If it fails, you lose trust.
Include importsDon't assume they know which libraries to import.
Show outputWhat should they see when it works?
Handle errorsReal code has error handling. Show it.
Use real valuesNo 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
LanguageCode BlockPackage InstallEnv Vars
JavaScript/Nodejavascript or jsnpm installprocess.env.VAR
TypeScripttypescript or tsnpm installprocess.env.VAR
Pythonpython or pypip installos.environ['VAR']
Gogogo getos.Getenv("VAR")
Rustrustcargo addstd::env::var("VAR")
Shellbash or shellN/A$VAR

Technical Accuracy Checklist

Run through before publishing:

CheckHow to Verify
Code runsCopy-paste every snippet and run it
Versions matchAre you using the current library version?
Links workClick every link
Commands workRun every CLI command
Screenshots currentDo UI screenshots match the current product?
No deprecated APIsCheck if any APIs used are deprecated
Security reviewNo hardcoded secrets, SQL injection, etc.
Peer reviewHave an engineer read it for accuracy

SEO for Developer Content

Developers use Google differently than consumers.

Developer Search Patterns
PatternExample 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
ElementBest Practice
TitleInclude primary keyword, framework names, year if relevant
Meta description150 chars, include keyword, promise specific outcome
H1Match or closely match title
H2sInclude secondary keywords, make scannable
Code blocksUse proper syntax highlighting (helps featured snippets)
Internal linksLink to related docs, tutorials, API reference
External linksLink to official docs of tools mentioned
URL slugLowercase, hyphens, include keyword
Show full SKILL.md (389 more words)Show less
Example Optimized Title
BadGood
"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
MetricWhat It Tells You
Page viewsReach (but vanity without context)
Time on pageEngagement (are they reading?)
Scroll depthDid they read to the end?
Bounce rateDid they find what they needed?
Search rankingsSEO performance
BacklinksAuthority and reference value
Social sharesResonance (especially HN, Twitter, Reddit)
Conversion eventsSign-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

ToolUse Case
OctolensMonitor where your content gets shared (HN, Reddit, Twitter). Track competitor content performance. Find content ideas from developer conversations.
Grammarly / HemingwayReadability and grammar checking
Carbon / Ray.soBeautiful code screenshots
ExcalidrawTechnical diagrams
LoomQuick video walkthroughs
Ahrefs / SEMrushKeyword research and SEO tracking
Google Search ConsoleTrack search performance

  • 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.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/devrel-content of sickn33/agentic-awesome-skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Devrel Content next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Devrel Content compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Devrel Content this skillsickn33/agentic-awesome-skills47k1 repos~3kAutomated safety check: PassMIT
Khazix WeChat Article WriterKKKKhazix/khazix-skills21k2 repos~2.9kAutomated safety check: PassMIT
Figurevectorize-io/hindsight46k—~1.9kAutomated safety check: PassMIT
SepiaNanako0129/sepia3k—~3.6kAutomated safety check: PassMIT
Blog Post Draftingluongnv89/claude-howto42k—~2.1kAutomated safety check: PassMIT
Notion To Blogwasp-lang/wasp19k—~922Automated safety check: PassMIT

Similar skills

  • Khazix WeChat Article Writer

    KKKKhazix/khazix-skills

    Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.

    21k GitHub starsUsed in 2 repos~2.9k tokens
    Writing & ContentAuto-check passed
  • Figure

    vectorize-io/hindsight

    Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.

    46k GitHub stars~1.9k tokensUpdated today
    Writing & ContentAuto-check passed
  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3k GitHub stars~3.6k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Blog Post Drafting

    luongnv89/claude-howto

    Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.

    42k GitHub stars~2.1k tokensUpdated 7 days ago
    Writing & ContentAuto-check passed
  • Notion To Blog

    wasp-lang/wasp

    Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.

    19k GitHub stars~922 tokensUpdated today
    Writing & ContentAuto-check passed
  • WeChat Article Rewriting

    aiworkskills/wechat-article-skills

    Rewrites, continues, or polishes an existing WeChat article draft using a configurable language model, sending the full draft text to that endpoint.

    665 GitHub starsUsed in 1 repo~2.2k tokens
    Writing & ContentAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Devrel Content

What does Devrel Content do?

When the user wants to create technical content for developers including blog posts, tutorials, and documentation. Devrel Content is an agent skill from sickn33/agentic-awesome-skills. When the user wants to create technical content for developers including blog posts, tutorials, and documentation.

When should I use Devrel Content?

Devrel Content fits situations like: wants to create technical content for developers including blog posts; tasks that involve Blog and article writing.

How do I install Devrel Content in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a claude-code`. Or copy the skill folder (skills/devrel-content in sickn33/agentic-awesome-skills) into .claude/skills/devrel-content in your project. Claude Code loads it when a task matches its description.

How do I install Devrel Content in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a codex`. Or copy the skill folder (skills/devrel-content in sickn33/agentic-awesome-skills) into .agents/skills/devrel-content in your project. Codex loads it when a task matches its description.

Can I use Devrel Content in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill devrel-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/devrel-content, .gemini/skills/devrel-content, .github/skills/devrel-content and .opencode/skills/devrel-content in your project.

What does Devrel Content need to run?

Going by SKILL.md and its folder, Devrel Content needs the command-line tools its instructions call (npm, pip, go and cargo). Our summary lists: Python 3; Node.js; A credential in YOUR_API_KEY.

Does Devrel Content access the network?

SKILL.md names 1 domain. As links in the text: octolens.com. This is read from the text; nothing was executed.

Is Devrel Content safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Devrel Content use?

Devrel Content is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Devrel Content use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Devrel Content?

Skills that share tags, products or a category with Devrel Content: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 46k stars), Sepia (Nanako0129/sepia, 3k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Devrel Content?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.