菜单
Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, reduce...
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ChonSong/skill-retriever --skill developer-onboarding命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | developer-onboarding |
| description | Get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, reduce... |
| risk | unknown |
| source | https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-onboarding |
| 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 get developers to "Hello World" fast with optimized quickstarts, tutorials, and sample apps. Trigger phrases: developer onboarding, time to first value, quickstart guide, hello world tutorial, developer activation, onboarding checklist, sample apps, getting started experience, reduce...
Get developers from signup to working code as fast as possible, then guide them to deeper engagement.
Developer onboarding is the critical window between "I signed up" and "I understand how to use this." You have about 10 minutes of developer attention. Every second of confusion, every error message without guidance, every "it should work but doesn't" moment costs you users.
Great onboarding feels like pair programming with someone who anticipated every question. Bad onboarding feels like being dropped in a foreign city without a map.
Review the /devmarketing-skills/skills/developer-audience-context skill to understand your target developers. A hobbyist building side projects needs different onboarding than an enterprise architect evaluating tools for production. Review /devmarketing-skills/skills/developer-signup-flow to ensure signup flows smoothly into onboarding.
First value isn't "made an API call." First value is when the developer sees your tool doing something useful for them.
| Tool Type | First Value Moment |
|---|---|
| API | Response returns meaningful data |
| SDK | Library performs expected function |
| Database | Query returns results |
| Hosting | App is live and accessible |
| Auth | User successfully logs in |
| Payment | Test charge processes |
Track timestamps at each stage:
signup_completed: 2024-01-15T10:00:00Z
dashboard_loaded: 2024-01-15T10:00:05Z
api_key_copied: 2024-01-15T10:01:30Z
first_api_call: 2024-01-15T10:04:45Z
first_successful_response: 2024-01-15T10:04:46Z # TTFV = 4:46
Benchmarks by category:
Map every step and eliminate blockers:
Common TTFV killers:
TTFV audit process:
# Quickstart: [Specific Goal] in 5 Minutes
What you'll build: [Screenshot or description of end result]
Prerequisites:
- Node.js 18+ (check: node --version)
- npm or yarn
## Step 1: Install the SDK
[One command, copy button]
## Step 2: Initialize with your API key
[Code with placeholder, copy button]
## Step 3: Make your first request
[Complete working example, copy button]
## Step 4: See the result
[Expected output shown]
## Next steps
- [Link to common second task]
- [Link to full documentation]
Progress indicators (Stripe style):
Your integration progress:
[x] Create account
[x] Get API keys
[ ] Install SDK
[ ] Make first API call
[ ] Handle webhooks
Contextual next steps (Vercel style):
You've deployed your first site.
What's next?
[ ] Add a custom domain
[ ] Set up environment variables
[ ] Enable analytics
Too much context upfront:
# Bad: The history of authentication
Before we begin, let's understand OAuth 2.0...
[500 words of background]
# Good: Jump to action
Install the SDK and make your first authenticated request.
Assuming environment:
# Bad
Run `npm install` to install dependencies.
# Good
npm install our-sdk
# Or with yarn: yarn add our-sdk
# Or with pnpm: pnpm add our-sdk
Hidden prerequisites:
# Bad (prerequisite discovered in Step 3)
Step 3: Connect to Redis
First, make sure Redis is running...
# Good (prerequisites listed upfront)
Prerequisites:
- Redis 6+ running locally (docker run -p 6379:6379 redis)
Interactive tutorials work for:
Interactive tutorial tools:
Static docs work better for:
Best practice: Offer both
# Make Your First API Request
## Quick version (copy-paste)
[Code block with copy button]
## Interactive version
[Launch in StackBlitz] [Try in CodeSandbox]
## Video walkthrough
[5-minute embedded video]
Do:
Don't:
Tiered approach:
Minimal example (Hello World)
Starter template (Basic app)
Production template (Full app)
github.com/your-org/
├── examples/
│ ├── minimal/
│ │ ├── node/
│ │ ├── python/
│ │ └── go/
│ ├── starter/
│ │ ├── nextjs/
│ │ ├── express/
│ │ └── fastapi/
│ └── production/
│ ├── saas-starter/
│ └── internal-tool/
Templates that don't work are worse than no templates.
Template health checklist:
Excellent templates: Supabase
Excellent templates: Clerk
Installation failures
Authentication failures
First request failures
Bad error message:
Error: Request failed with status 401
Good error message:
Authentication failed: Invalid API key
Your API key starts with 'sk_test_' but you're calling the production endpoint.
To fix:
1. Use the production API key (starts with 'sk_live_'), or
2. Change endpoint to https://api.example.com/test/
Docs: https://docs.example.com/auth#environments
Detect common mistakes in real-time:
// Client SDK that catches common errors
if (apiKey.startsWith('sk_test_') && endpoint.includes('/v1/')) {
console.warn(
'Warning: Using test API key with production endpoint. ' +
'This will fail. Use production key or test endpoint.'
);
}
In-dashboard error recovery:
Something went wrong with your integration.
We detected:
- Last API call: 2 hours ago
- Status: 401 Unauthorized
- Likely cause: API key rotated
[Regenerate API Key] [View Error Logs] [Contact Support]
Activation = the moment a developer has enough success to keep using your product.
Different products, different activation definitions:
| Product | Activation Definition |
|---|---|
| Stripe | First successful test charge |
| Twilio | First SMS sent and delivered |
| Auth0 | First user authenticated |
| Vercel | First deploy accessible via URL |
| Algolia | First search returns results |
Activation rate
Activated users / Signed up users × 100
Benchmark: 20-40% for self-serve developer products
Time to activation
Median time from signup to activation event
Benchmark: <10 minutes for APIs, <1 hour for infrastructure
Activation by cohort Track weekly or monthly cohorts to identify improvements:
Week 1 cohort: 25% activation
Week 2 cohort: 28% activation (added better error messages)
Week 3 cohort: 35% activation (added interactive tutorial)
Track behaviors that predict activation:
| Leading Indicator | Correlation to Activation |
|---|---|
| Copied API key | 2x more likely |
| Viewed quickstart | 1.5x more likely |
| Installed SDK | 3x more likely |
| Joined Discord | 2.5x more likely |
Confirm activation led to value:
| Lagging Indicator | Meaning |
|---|---|
| Day 7 retention | Still using after a week |
| API calls in week 2 | Continued development |
| Upgrade to paid | Perceived enough value |
| Invited team member | Expanding usage |
Signed up: 1,000
├── Visited dashboard: 950 (95%)
├── Viewed quickstart: 700 (74%)
├── Copied API key: 500 (71%)
├── Made first API call: 350 (70%)
├── Got successful response: 300 (86%) ← Activation
├── Made 10+ API calls: 150 (50%)
└── Day 7 return: 100 (67%)
| Timing | Purpose | |
|---|---|---|
| Welcome | Immediate | Confirm signup, provide key links |
| Getting started | +1 hour | Drive first API call if not done |
| Tips | +1 day | Share common patterns |
| Check-in | +3 days | Ask if stuck, offer help |
| Activation push | +7 days | Final nudge if not activated |
Do:
Don't:
/devmarketing-skills/skills/developer-signup-flow - Getting to the onboarding start/devmarketing-skills/skills/developer-audience-context - Who you're onboarding/devmarketing-skills/skills/free-tier-strategy - What they can do without paying