菜单
Transform documentation into a powerful marketing channel that attracts, converts, and retains developers. This skill covers creating documentation that ranks in search, converts visitors into users, and accelerates adoption through exceptional information architecture and...
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ChonSong/skill-retriever --skill docs-as-marketing命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
AI-powered Draw.io diagram generation with real-time browser preview. Create flowcharts, architecture diagrams, sequence diagrams, and cloud infrastructure diagrams (AWS/GCP/Azure) using natural language. Supports animated connectors, real-time editing, and structured A–H format extraction from text or images.
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this,"...
基于 SOC 职业分类
正在显示 SKILL.md
| name | docs-as-marketing |
| description | Transform documentation into a powerful marketing channel that attracts, converts, and retains developers. This skill covers creating documentation that ranks in search, converts visitors into users, and accelerates adoption through exceptional information architecture and... |
| risk | unknown |
| source | https://github.com/jonathimer/devmarketing-skills/tree/main/skills/docs-as-marketing |
| source_repo | jonathimer/devmarketing-skills |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE |
Use this skill when you need transform documentation into a powerful marketing channel that attracts, converts, and retains developers. This skill covers creating documentation that ranks in search, converts visitors into users, and accelerates adoption through exceptional information architecture and...
Documentation is often a developer's first meaningful interaction with your product. Great docs don't just explain—they market. They reduce friction, build trust, and turn curious visitors into active users who recommend your product to others.
Developer documentation serves multiple marketing functions:
This skill covers the intersection of technical writing and developer marketing—creating documentation that serves both education and conversion goals.
Review the developer-audience-context skill to understand your target developers:
Your documentation strategy should directly address these audience insights.
Structure your docs around the four types developers need:
| Type | Purpose | Marketing Function |
|---|---|---|
| Tutorials | Learning-oriented, step-by-step | Builds confidence, shows product value |
| How-to Guides | Task-oriented, problem-solving | Demonstrates capability breadth |
| Reference | Information-oriented, accurate | Proves product depth and reliability |
| Explanation | Understanding-oriented, conceptual | Establishes thought leadership |
Good Navigation Structure:
Getting Started
├── Quickstart (< 5 min)
├── Installation
└── Core Concepts
Guides
├── Authentication
├── [Most Common Use Case]
├── [Second Most Common Use Case]
└── ...
API Reference
├── Overview
├── Authentication
├── Endpoints (alphabetical or logical grouping)
└── SDKs
Resources
├── Examples
├── Changelog
└── Support
Bad Navigation Structure:
Documentation
├── Chapter 1: Introduction
├── Chapter 2: Getting Started
├── Chapter 3: Advanced Topics
├── Appendix A
└── API (link to separate site)
Every documentation page should follow this hierarchy:
Your quickstart is your most important conversion page. Optimize ruthlessly.
Developers should reach a meaningful success moment within 5 minutes. If your quickstart takes longer, you're losing developers.
Measure and optimize:
# Quickstart
Get your first [meaningful result] in under 5 minutes.
## Prerequisites
- [Specific version] of [language/tool]
- [Account/API key] (link to signup)
## Step 1: Install
[Single command, copy-paste ready]
## Step 2: Configure
[Minimal configuration, explain what each part does]
## Step 3: Run
[The payoff—show them it works]
## What You Built
[Explain what just happened and why it matters]
## Next Steps
- [Immediate next tutorial]
- [Reference docs for what they just used]
- [Community/support link]
Good Quickstart:
# Send Your First Message
Send an SMS in under 5 minutes.
## Prerequisites
- Node.js 16 or higher
- A Twilio account ([sign up free](https://github.com/jonathimer/devmarketing-skills/tree/main/skills/docs-as-marketing/link))
## Install the SDK
```bash
npm install twilio
Create send-sms.js:
const twilio = require('twilio');
const client = twilio('YOUR_ACCOUNT_SID', 'YOUR_AUTH_TOKEN');
client.messages.create({
body: 'Hello from my app!',
to: '+15551234567',
from: '+15559876543'
}).then(message => console.log(`Sent: ${message.sid}`));
Run it:
node send-sms.js
You should see: Sent: SM1234...
You authenticated with your API credentials and sent an SMS...
**Bad Quickstart:**
```markdown
# Getting Started
Welcome to our platform! Before we begin, let's discuss
the architecture of our messaging system...
[500 words of background]
## Installation
First, ensure you have the correct version of Node.js.
You can check this by running...
[200 words on version checking]
You'll also need to configure your environment variables.
Create a .env file and add the following variables...
[Complex configuration with 10+ variables]
Critical: Example code must work when copied. Test it.
Good Example:
## Create a User
Creates a new user in your organization.
### Request
```bash
curl -X POST https://api.example.com/v1/users \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"email": "developer@example.com",
"name": "Jane Developer"
}'
{
"id": "usr_123abc",
"email": "developer@example.com",
"name": "Jane Developer",
"created_at": "2024-01-15T10:30:00Z"
}
| Code | Meaning |
|---|---|
| 400 | Invalid email format |
| 409 | Email already exists |
| 401 | Invalid or missing API key |
**Bad Example:**
```markdown
## POST /users
Parameters:
- email (string)
- name (string)
- org_id (string, optional)
- role (enum, optional)
- metadata (object, optional)
- ...
Returns a user object.
Provide examples in languages your developers actually use:
Developer documentation can capture high-intent search traffic.
Target Query Types:
Page Titles:
Good: "Send SMS with Node.js | Twilio Docs"
Bad: "Documentation - Messaging - SMS - Send"
Meta Descriptions:
Good: "Learn how to send SMS messages using Node.js and the
Twilio API. Includes code examples and troubleshooting tips."
Bad: "This page contains documentation for the SMS sending
functionality of our messaging product."
URL Structure:
Good: /docs/sms/send-messages/nodejs
Bad: /docs/section/3/page/27?lang=nodejs
Create a documentation web, not documentation silos:
| Metric | What It Tells You |
|---|---|
| Time on quickstart | Engagement (but also confusion) |
| Quickstart completion rate | Conversion effectiveness |
| Search → signup rate | Docs as acquisition channel |
| Support ticket deflection | Docs comprehensiveness |
| Page ratings/feedback | Content quality |
| Internal search queries | Content gaps |
Implement:
Problem: Pages with no code, no structure, no visual breaks Fix: Lead with code, use headers liberally, break up paragraphs
Problem: Assuming developers know your terminology Fix: Define terms on first use, link to glossary
Problem: One page trying to cover all use cases Fix: Separate pages for distinct tasks, link between them
Problem: Quickstart code that no longer works Fix: Automated testing of documentation code samples
Problem: Discovering requirements mid-tutorial Fix: All prerequisites at the top, with version numbers