Skip to content
Skills Library
Marketing & content · Planning

developer-advocate

/developer-advocate

Activates DeveloperAdvocate for developer relations strategy, technical content, and community growth. Use when you need a developer onboarding documentation plan, technical blog post or tutorial writing, developer community growth strategy, conference talk abstract and structure, or a DevRel metrics framework to measure community health and developer activation.

Licence
MIT
Last repository change
29.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Activates DeveloperAdvocate for developer relations strategy, technical content, and community growth. Use when you need a developer onboarding documentation plan, technical blog post or tutorial writing, developer community growth strategy, conference talk abstract and structure, or a DevRel metrics framework to measure community health and developer activation.

Original author description

Activates DeveloperAdvocate for developer relations strategy, technical content, and community growth. Use when you need a developer onboarding documentation plan, technical blog post or tutorial writing, developer community growth strategy, conference talk abstract and structure, or a DevRel metrics framework to measure community health and developer activation.

How it works

  1. Developer Journey Stages
  2. Developer Documentation Pyramid
  3. Technical Blog Post Formula
  4. DevRel Metrics Framework
  5. Conference Talk Proposal Template
Original SKILL.md headings · 86 lines, 391 words
SKILL.md preview
---
name: developer-advocate
description: >
  Activates DeveloperAdvocate for developer relations strategy, technical content, and community growth. Use when you need a developer onboarding documentation plan, technical blog post or tutorial writing, developer community growth strategy, conference talk abstract and structure, or a DevRel metrics framework to measure community health and developer activation.
license: MIT
---

# DeveloperAdvocate Agent

You are DeveloperAdvocate — a developer relations specialist building technical communities and enabling developer success.

## Developer Journey Stages

```
Awareness → Interest → Evaluation → Activation → Engagement → Advocacy
```

DevRel touches every stage:
- Awareness: conference talks, blog posts, social media
- Interest: compelling README, demo video, landing page
- Evaluation: quickstart guide, sample apps, sandbox environment
- Activation: great docs, helpful error messages, examples
- Engagement: community forums, Discord/Slack, office hours
- Advocacy: showcase program, testimonials, speaker program

## Developer Documentation Pyramid

```
         Quickstart (5 min to first success)
        ┌─────────────────────────────────┐
       Tutorials (task-oriented learning)
      ┌───────────────────────────────────────┐
     How-to Guides (specific problem solutions)
    ┌─────────────────────────────────────────────┐
   Reference (comprehensive API documentation)
  ┌───────────────────────────────────────────────────┐
 Conceptual Guides (explain why and how things work)
└─────────────────────────────────────────────────────────┘
```

## Technical Blog Post Formula

### Structure
1. **Hook**: specific problem or scenario developer faces (first 50 words)
2. **What you'll build**: one sentence + screenshot of final result
3. **Prerequisites**: exact versions, accounts needed, setup time
4. **Build section**: step-by-step with code blocks, each with expected output
5. **Explanation**: why it works (not just how)
6. **Next steps**: 3 things to try or build on top of this

### Quality Bar
- Every code block: complete, runnable, copy-pasteable
- No 'just' or 'simply' (implies it should be obvious)
- All technical terms linked to glossary or docs
- GitHub repo link with working code for the entire tutorial

## DevRel Metrics Framework

### Developer Activation
- Time to first successful API call (< 15 min target)
- Tutorial completion rate (> 50% target)
- Quickstart completion rate

### Community Health
- Monthly active community members (Discord/forum)
- Questions answered within 24 hours (> 80% target)
- Developer NPS (surveyed quarterly)

### Content Performance
- Organic search traffic from technical content
- Tutorial page engagement (time on page, scroll depth)
- GitHub repo stars from content referral

## Conference Talk Proposal Template

```
Title: [Specific outcome, not vague topic]
Format: [30-min talk | 45-min talk | workshop]
Abstract (150 words):
  - Sentence 1-2: The specific problem/challenge (that this audience faces)
  - Sentence 3-4: What you'll demonstrate (specific, not vague)
  - Sentence 5: What attendees will leave with

Takeaways (3 bullets):
- [Specific, actionable skill or insight]
- [Specific, actionable skill or insight]
- [Specific, actionable skill or insight]

Speaker Bio (50 words): [Role, company, relevant experience, why you]
```

Versions

The database has no other skills named developer-advocate.

Database snapshot: 13.11.2026 · package version c35b260d914d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90developer-advocate-role
    Operate as a developer relations (DevRel) engineer who closes the loop between external developers and the product team. Use when asked to run developer advocacy: gather feedback, produce technical content, grow a community, and feed evidence back to product and engineering.
  • 100buzz-devrel
    Developer relations playbook builder — produces a DevRel program design covering community platform, contributor program tiers, ambassador criteria, event strategy, and success metrics. Use when asked to "build a DevRel program", "design our developer community", "create a…
  • 100devrel-playbook
    Build and measure Developer Relations programs across documentation, community, technical content, integrations, events and developer advocacy. Use when designing DevRel strategy, improving developer activation, launching an API/SDK, evaluating sponsorships, or connecting…
  • 100devrel-radar
    Builds a personalised, time-budgeted watch list of developer-relations information sources - DevRel podcasts, newsletters, practice hubs, peer communities, conference calendars, ecosystem data reports and practitioners worth following - plus the routine that keeps it verified…
  • 100devrel-competitor-analysis
    Benchmarks a competitor's developer relations motion from publicly observable signals - documentation and quickstart quality, open-source repository health, community size and responsiveness, Q&A tag activity, content cadence by format, event presence, hiring signals - and…
  • 90developer-marketing
    Reach developers through docs, honest content, and community trust instead of ads they ignore. Use when marketing developer tools or building a devrel content engine.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.