skills/developer-onboarding/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, develop category: Document Processing source: antigravity tags: [python, javascript, node, nextjs, markdown, api, ai, workflow, template, design] url: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/developer-onboarding --- # Developer On
npx skillsauth add ranbot-ai/awesome-skills skills/developer-onboardingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
tools
Use when a user asks to mine or update a private, evidence-backed work profile from local Claude Code, Codex, Copilot CLI, or OpenCode sessions.
data-ai
Use when diagnosing Android overheating, idle heat, thermal throttling, charging or radio heat, or abnormal battery drain with read-only ADB evidence and approval gates.
research
Research public competitor ads, analyze creative patterns and landing pages, and produce an evidence-labeled strategic teardown.
tools
Compiled CLI covering all 52 endpoints of the Anytype local API — objects, properties, tags, search, chat, files — one binary, no MCP server needed.