[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A2WSQYQBJN8PZRYH1YCSKH":3,"skill-same:01M7A2WSQYQBJN8PZRYH1YCSKH":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A2WSQYQBJN8PZRYH1YCSKH","api-onboarding",null,"Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: \"API...","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fapi-onboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: api-onboarding\ndescription: 'Reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: \"API...'\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fapi-onboarding\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Reducing Time-to-First-API-Call\n## When to Use\n\nUse this skill when you need reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: \"API...\n\n\nThe time between a developer discovering your API and successfully making their first call is the most critical window in your entire developer journey. Every minute of friction here costs you potential users.\n\n## Overview\n\nTime-to-First-API-Call (TTFAC) is the single most predictive metric for developer adoption. Developers who succeed quickly become active users. Developers who struggle leave—often silently.\n\nThis skill covers:\n- Measuring and optimizing TTFAC\n- Removing authentication friction\n- Creating effective sandbox environments\n- Building interactive documentation\n- Identifying and fixing common failure points\n\n## Before You Start\n\nReview the **developer-audience-context** skill to understand:\n- What's the typical technical sophistication of your developers?\n- What tools and environments do they commonly use?\n- What alternative products have they tried? What was their experience?\n- What's their urgency level? (Evaluating vs. building immediately)\n\nYour onboarding should meet developers where they are.\n\n## Understanding TTFAC\n\n### What TTFAC Measures\n\nTime-to-First-API-Call measures the elapsed time from a developer's first interaction to their first successful API response. This includes:\n\n1. **Discovery time**: Finding the \"Get Started\" content\n2. **Signup time**: Creating an account\n3. **Credential time**: Obtaining API keys\n4. **Setup time**: Installing SDK, configuring environment\n5. **Execution time**: Running first request\n6. **Success time**: Receiving successful response\n\n### TTFAC Benchmarks\n\n| Rating | TTFAC | Developer Experience |\n|--------|-------|---------------------|\n| **Excellent** | \u003C 5 min | \"This is amazing\" |\n| **Good** | 5-15 min | \"Pretty straightforward\" |\n| **Acceptable** | 15-30 min | \"Got there eventually\" |\n| **Poor** | 30-60 min | \"This is frustrating\" |\n| **Failing** | > 60 min | \"I'll try something else\" |\n\n### Measuring TTFAC\n\n**Instrumentation points:**\n```javascript\n\u002F\u002F Track these events with timestamps\nanalytics.track('docs_quickstart_viewed');\nanalytics.track('signup_started');\nanalytics.track('signup_completed');\nanalytics.track('api_key_created');\nanalytics.track('sdk_installed');     \u002F\u002F Via package manager data\nanalytics.track('first_api_call');    \u002F\u002F Via API logs\nanalytics.track('first_successful_call');\n```\n\n**Calculate:**\n- Median TTFAC (more useful than average)\n- TTFAC by developer segment\n- Drop-off rates at each step\n- Success rates within time windows (5 min, 15 min, 60 min)\n\n## Authentication Simplification\n\nAuthentication is the #1 source of onboarding friction. Simplify ruthlessly.\n\n### The Ideal Auth Flow\n\n1. Developer signs up (\u003C 2 minutes)\n2. API key visible immediately (not buried in settings)\n3. Key works immediately (no activation delay)\n4. Copy-paste into example code\n5. Success\n\n### Auth Anti-Patterns to Avoid\n\n**The Approval Queue**\n```\n❌ \"Your API access request has been submitted.\n    You'll receive access within 2-3 business days.\"\n```\nDevelopers leave and find an alternative.\n\n**The Hidden Key**\n```\n❌ Settings → Team → API → Credentials → Keys → Show Key\n```\nMake keys visible on dashboard home.\n\n**The Complex Token**\n```\n❌ OAuth flow requiring:\n   - Client ID\n   - Client secret\n   - Redirect URI configuration\n   - Token exchange\n   - Token refresh handling\n```\nFor getting started, provide simple API keys.\n\n**The Verification Gauntlet**\n```\n❌ Sign up → Verify email → Verify phone →\n   Add payment → Verify payment → Then API key\n```\nMinimize friction for first API call.\n\n### Auth Simplification Strategies\n\n**Provide Test Keys Immediately**\n```\n✅ \"Here's your test API key: sk_test_abc123...\n    Use this in sandbox mode—no charges, no setup.\"\n```\n\n**Support Multiple Auth Methods**\n```\n✅ Quickstart: API key header\n   Production: OAuth when they need it\n```\n\n**Pre-populate Examples**\n```\n✅ # Your API key is pre-filled in these examples\n   curl -H \"Authorization: Bearer sk_test_YOUR_KEY\" ...\n```\n\n**Delay Production Requirements**\n```\n✅ Test mode: Instant access\n   Production mode: Add payment, verify identity (later)\n```\n\n## Sandbox Environments\n\nA sandbox removes the fear of \"breaking something\" and lets developers experiment freely.\n\n### Sandbox Requirements\n\n**Instant Access**: No approval, no payment, no complex setup\n\n**Realistic Behavior**: Same API, same responses, same errors\n\n**Clear Boundaries**: Obvious when in sandbox vs. production\n\n**Reset Capability**: Easy way to start fresh\n\n**Generous Limits**: Don't rate-limit experimentation\n\n### Sandbox Implementation Patterns\n\n**Separate Endpoints**\n```\nProduction: api.example.com\nSandbox:    sandbox-api.example.com\n```\n\n**Key Prefixes**\n```\nProduction key: sk_live_abc123...\nSandbox key:    sk_test_xyz789...\n```\n\n**Environment Parameter**\n```\ncurl -X POST https:\u002F\u002Fapi.example.com\u002Fv1\u002Fmessages \\\n  -H \"Authorization: Bearer $API_KEY\" \\\n  -d '{\"sandbox\": true, ...}'\n```\n\n### Sandbox Data\n\n**Pre-populated Test Data**\n```javascript\n\u002F\u002F Sandbox comes with test users\nconst testUsers = await client.users.list();\n\u002F\u002F Returns: [\n\u002F\u002F   { id: \"usr_test_alice\", name: \"Alice (Test)\" },\n\u002F\u002F   { id: \"usr_test_bob\", name: \"Bob (Test)\" }\n\u002F\u002F ]\n```\n\n**Magic Values**\n```javascript\n\u002F\u002F Special values trigger specific behaviors\nclient.payments.create({\n  amount: 1000,\n  card: \"4242424242424242\"  \u002F\u002F Always succeeds\n});\n\nclient.payments.create({\n  amount: 1000,\n  card: \"4000000000000002\"  \u002F\u002F Always declines\n});\n```\n\n**Documented Test Scenarios**\n```markdown\n## Test Card Numbers\n\n| Number           | Behavior              |\n|-----------------|----------------------|\n| 4242424242424242 | Successful charge    |\n| 4000000000000002 | Declined             |\n| 4000000000009995 | Insufficient funds   |\n| 4000000000000069 | Expired card         |\n```\n\n## Interactive Documentation\n\nLet developers make API calls without leaving the browser.\n\n### \"Try It\" Functionality\n\n**Essential Features:**\n- Pre-authenticated (use their sandbox key automatically)\n- Pre-filled with working example data\n- Editable request parameters\n- Real API responses (not mocked)\n- Copy as cURL\u002Fcode option\n\n**Implementation:**\n```html\n\u003Cdiv class=\"api-explorer\">\n  \u003Ch3>Try it: Send a Message\u003C\u002Fh3>\n\n  \u003Cdiv class=\"request-editor\">\n    \u003Clabel>To Phone Number\u003C\u002Flabel>\n    \u003Cinput type=\"text\" value=\"+15551234567\" \u002F>\n\n    \u003Clabel>Message Body\u003C\u002Flabel>\n    \u003Ctextarea>Hello from the API Explorer!\u003C\u002Ftextarea>\n\n    \u003Cbutton onclick=\"sendRequest()\">Send Request\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"response-viewer\">\n    \u003Ch4>Response\u003C\u002Fh4>\n    \u003Cpre>\u003Ccode id=\"response\">\u003C\u002Fcode>\u003C\u002Fpre>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n### Interactive Docs Tools\n\n**OpenAPI-Based:**\n- Swagger UI\n- Redoc\n- Stoplight Elements\n\n**Custom Platforms:**\n- ReadMe.io\n- Postman Published Docs\n- Custom React components\n\n### Interactive Examples\n\nGo beyond single requests:\n\n```markdown\n## Interactive Tutorial: Send Your First Message\n\n### Step 1: Check your balance\n\u003Capi-explorer endpoint=\"GET \u002Faccount\u002Fbalance\" \u002F>\n\n### Step 2: Send a message\n\u003Capi-explorer endpoint=\"POST \u002Fmessages\"\n  body='{\"to\": \"+15551234567\", \"body\": \"Hello!\"}' \u002F>\n\n### Step 3: Check message status\n\u003Capi-explorer endpoint=\"GET \u002Fmessages\u002F{id}\"\n  params='{\"id\": \"{{previous.id}}\"}' \u002F>\n```\n\n## Common Failure Points\n\n### Failure Point Analysis\n\nTrack where developers fail and why:\n\n```javascript\n\u002F\u002F Instrument error events\napi.on('request_error', (error, request) => {\n  analytics.track('api_error', {\n    error_type: error.type,\n    error_code: error.code,\n    endpoint: request.endpoint,\n    time_since_signup: timeSinceSignup(),\n    is_first_call: isFirstCall()\n  });\n});\n```\n\n### Most Common First-Call Failures\n\n**1. Authentication Errors (40% of first-call failures)**\n```\nProblem: Wrong key, malformed header, missing auth\nFix:\n- Clearer error messages: \"API key should start with 'sk_test_'\"\n- Pre-filled code examples with actual key\n- Auth header format shown with example\n```\n\n**2. Request Format Errors (25%)**\n```\nProblem: Wrong content type, malformed JSON, missing fields\nFix:\n- Accept flexible content types on simple endpoints\n- Return specific field-level errors\n- Show exactly what was expected vs. received\n```\n\n**3. Environment\u002FSetup Errors (20%)**\n```\nProblem: SDK not installed, wrong SDK version, missing dependencies\nFix:\n- Version-specific installation instructions\n- Compatibility matrix clearly visible\n- Quick environment check script\n```\n\n**4. Rate Limiting (10%)**\n```\nProblem: Aggressive rate limits during exploration\nFix:\n- Generous sandbox limits (or none)\n- Clear rate limit errors with retry-after\n- Don't count failed requests against limits\n```\n\n**5. Networking Errors (5%)**\n```\nProblem: Firewall, proxy, SSL issues\nFix:\n- Connectivity test endpoint\n- Clear networking troubleshooting guide\n- Alternative ports\u002Fprotocols if possible\n```\n\n### Error Recovery Flows\n\nDesign error messages that recover the onboarding:\n\n```json\n{\n  \"error\": {\n    \"type\": \"authentication_error\",\n    \"message\": \"Invalid API key provided\",\n    \"code\": \"invalid_api_key\",\n    \"recovery\": {\n      \"steps\": [\n        \"Check that your API key starts with 'sk_test_' or 'sk_live_'\",\n        \"Ensure there are no extra spaces or newlines\",\n        \"Generate a new key at https:\u002F\u002Fdashboard.example.com\u002Fkeys\"\n      ],\n      \"docs\": \"https:\u002F\u002Fdocs.example.com\u002Fauthentication\",\n      \"support\": \"https:\u002F\u002Fsupport.example.com\u002Fauth-issues\"\n    }\n  }\n}\n```\n\n## The First-Call Experience Audit\n\n### Audit Checklist\n\nPerform this audit quarterly (or after any onboarding changes):\n\n**As a New Developer:**\n- [ ] Create a new account (use a fresh browser\u002Fincognito)\n- [ ] Time how long until you have a working API key\n- [ ] Follow the quickstart exactly as written\n- [ ] Make your first API call\n- [ ] Record total time and every friction point\n\n**Questions to Answer:**\n- How many clicks from homepage to first API call?\n- How many pages\u002Ftabs did you need open?\n- What did you have to figure out that wasn't explained?\n- Where did you get stuck or confused?\n- What would have made you give up?\n\n### Friction Point Scoring\n\n| Friction | Impact | Priority |\n|----------|--------|----------|\n| Must verify email before API key | High | Fix immediately |\n| API key buried in settings | High | Fix immediately |\n| No copy button on code examples | Medium | Fix this quarter |\n| Quickstart assumes specific OS | Medium | Fix this quarter |\n| Example uses outdated SDK version | Low | Fix when updating docs |\n\n## Onboarding Optimization Framework\n\n### Step 1: Measure Current State\n- Instrument TTFAC tracking\n- Run first-call audit with 5 developers\n- Identify top 3 drop-off points\n\n### Step 2: Reduce Steps\n- Can any step be eliminated entirely?\n- Can any step be deferred until later?\n- Can multiple steps be combined?\n\n### Step 3: Accelerate Remaining Steps\n- Pre-fill everything possible\n- Provide copy buttons everywhere\n- Show progress and next steps\n\n### Step 4: Recover Failures\n- Improve error messages\n- Add inline troubleshooting\n- Provide live support for stuck developers\n\n### Step 5: Measure and Iterate\n- Track TTFAC improvements\n- A\u002FB test onboarding changes\n- Regular audits with real developers\n\n## Tools\n\n### Onboarding Analytics\n- **Amplitude\u002FMixpanel**: Event tracking and funnels\n- **FullStory\u002FHotjar**: Session recording\n- **Custom dashboards**: TTFAC metrics\n\n### Interactive Docs\n- **ReadMe.io**: Full-featured developer hub\n- **Stoplight**: OpenAPI-powered docs\n- **Redocly**: API documentation platform\n- **Custom**: Build with React\u002FVue\n\n### Testing\n- **Ghost Inspector**: Automated onboarding testing\n- **Checkly**: API monitoring and testing\n- **k6**: Load testing of onboarding flows\n\n## Related Skills\n\n- **docs-as-marketing**: Quickstart documentation\n- **sdk-dx**: SDK that reduces onboarding complexity\n- **developer-sandbox**: The playground developers onboard with\n- **developer-audience-context**: Understanding your onboarding audience\n- **developer-metrics**: Measuring onboarding success\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Reducing Time-to-First-API-Call\n## When to Use\n\nUse this skill when you need reduce time-to-first-API-call (TTFAC) by optimizing every step of the developer onboarding journey. This skill covers authentication simplification, sandbox environments, interactive documentation, and identifying and eliminating common failure points. Trigger phrases: \"API...\n\n\nThe time between a developer discovering your API and successfully making their first call is the most critical window in your entire developer journey. Every minute of friction here costs you potential users.\n\n## Overview\n\nTime-to-First-API-Call (TTFAC) is the single most predictive metric for developer adoption. Developers who succeed quickly become active users. Developers who struggle leave—often silently.\n\nThis skill covers:\n- Measuring and optimizing TTFAC\n- Removing authentication friction\n- Creating effective sandbox environments\n- Building interactive documentation\n- Identifying and fixing common failure points\n\n## Before You Start\n\nReview the **developer-audience-context** skill to understand:\n- What's the typical technical sophistication of your developers?\n- What tools and environments do they commonly use?\n- What alternative products have they tried? What was their experience?\n- What's their urgency level? (Evaluating vs. building immediately)\n\nYour onboarding should meet developers where they are.\n\n## Understanding TTFAC\n\n### What TTFAC Measures\n\nTime-to-First-API-Call measures the elapsed time from a developer's first interaction to their first successful API response. This includes:\n\n1. **Discovery time**: Finding the \"Get Started\" content\n2. **Signup time**: Creating an account\n3. **Credential time**: Obtaining API keys\n4. **Setup time**: Installing SDK, configuring environment\n5. **Execution time**: Running first request\n6. **Success time**: Receiving successful response\n\n### TTFAC Benchmarks\n\n| Rating | TTFAC | Developer Experience |\n|--------|-------|---------------------|\n| **Excellent** | \u003C 5 min | \"This is amazing\" |\n| **Good** | 5-15 min | \"Pretty straightforward\" |\n| **Acceptable** | 15-30 min | \"Got there eventually\" |\n| **Poor** | 30-60 min | \"This is frustrating\" |\n| **Failing** | > 60 min | \"I'll try something else\" |\n\n### Measuring TTFAC\n\n**Instrumentation points:**\n```javascript\n\u002F\u002F Track these events with timestamps\nanalytics.track('docs_quickstart_viewed');\nanalytics.track('signup_started');\nanalytics.track('signup_completed');\nanalytics.track('api_key_created');\nanalytics.track('sdk_installed');     \u002F\u002F Via package manager data\nanalytics.track('first_api_call');    \u002F\u002F Via API logs\nanalytics.track('first_successful_call');\n```\n\n**Calculate:**\n- Median TTFAC (more useful than average)\n- TTFAC by developer segment\n- Drop-off rates at each step\n- Success rates within time windows (5 min, 15 min, 60 min)\n\n## Authentication Simplification\n\nAuthentication is the #1 source of onboarding friction. Simplify ruthlessly.\n\n### The Ideal Auth Flow\n\n1. Developer signs up (\u003C 2 minutes)\n2. API key visible immediately (not buried in settings)\n3. Key works immediately (no activation delay)\n4. Copy-paste into example code\n5. Success\n\n### Auth Anti-Patterns to Avoid\n\n**The Approval Queue**\n```\n❌ \"Your API access request has been submitted.\n    You'll receive access within 2-3 business days.\"\n```\nDevelopers leave and find an alternative.\n\n**The Hidden Key**\n```\n❌ Settings → Team → API → Credentials → Keys → Show Key\n```\nMake keys visible on dashboard home.\n\n**The Complex Token**\n```\n❌ OAuth flow requiring:\n   - Client ID\n   - Client secret\n   - Redirect URI configuration\n   - Token exchange\n   - Token refresh handling\n```\nFor getting started, provide simple API keys.\n\n**The Verification Gauntlet**\n```\n❌ Sign up → Verify email → Verify phone →\n   Add payment → Verify payment → Then API key\n```\nMinimize friction for first API call.\n\n### Auth Simplification Strategies\n\n**Provide Test Keys Immediately**\n```\n✅ \"Here's your test API key: sk_test_abc123...\n    Use this in sandbox mode—no charges, no setup.\"\n```\n\n**Support Multiple Auth Methods**\n```\n✅ Quickstart: API key header\n   Production: OAuth when they need it\n```\n\n**Pre-populate Examples**\n```\n✅ # Your API key is pre-filled in these examples\n   curl -H \"Authorization: Bearer sk_test_YOUR_KEY\" ...\n```\n\n**Delay Production Requirements**\n```\n✅ Test mode: Instant access\n   Production mode: Add payment, verify identity (later)\n```\n\n## Sandbox Environments\n\nA sandbox removes the fear of \"breaking something\" and lets developers experiment freely.\n\n### Sandbox Requirements\n\n**Instant Access**: No approval, no payment, no complex setup\n\n**Realistic Behavior**: Same API, same responses, same errors\n\n**Clear Boundaries**: Obvious when in sandbox vs. production\n\n**Reset Capability**: Easy way to start fresh\n\n**Generous Limits**: Don't rate-limit experimentation\n\n### Sandbox Implementation Patterns\n\n**Separate Endpoints**\n```\nProduction: api.example.com\nSandbox:    sandbox-api.example.com\n```\n\n**Key Prefixes**\n```\nProduction key: sk_live_abc123...\nSandbox key:    sk_test_xyz789...\n```\n\n**Environment Parameter**\n```\ncurl -X POST https:\u002F\u002Fapi.example.com\u002Fv1\u002Fmessages \\\n  -H \"Authorization: Bearer $API_KEY\" \\\n  -d '{\"sandbox\": true, ...}'\n```\n\n### Sandbox Data\n\n**Pre-populated Test Data**\n```javascript\n\u002F\u002F Sandbox comes with test users\nconst testUsers = await client.users.list();\n\u002F\u002F Returns: [\n\u002F\u002F   { id: \"usr_test_alice\", name: \"Alice (Test)\" },\n\u002F\u002F   { id: \"usr_test_bob\", name: \"Bob (Test)\" }\n\u002F\u002F ]\n```\n\n**Magic Values**\n```javascript\n\u002F\u002F Special values trigger specific behaviors\nclient.payments.create({\n  amount: 1000,\n  card: \"4242424242424242\"  \u002F\u002F Always succeeds\n});\n\nclient.payments.create({\n  amount: 1000,\n  card: \"4000000000000002\"  \u002F\u002F Always declines\n});\n```\n\n**Documented Test Scenarios**\n```markdown\n## Test Card Numbers\n\n| Number           | Behavior              |\n|-----------------|----------------------|\n| 4242424242424242 | Successful charge    |\n| 4000000000000002 | Declined             |\n| 4000000000009995 | Insufficient funds   |\n| 4000000000000069 | Expired card         |\n```\n\n## Interactive Documentation\n\nLet developers make API calls without leaving the browser.\n\n### \"Try It\" Functionality\n\n**Essential Features:**\n- Pre-authenticated (use their sandbox key automatically)\n- Pre-filled with working example data\n- Editable request parameters\n- Real API responses (not mocked)\n- Copy as cURL\u002Fcode option\n\n**Implementation:**\n```html\n\u003Cdiv class=\"api-explorer\">\n  \u003Ch3>Try it: Send a Message\u003C\u002Fh3>\n\n  \u003Cdiv class=\"request-editor\">\n    \u003Clabel>To Phone Number\u003C\u002Flabel>\n    \u003Cinput type=\"text\" value=\"+15551234567\" \u002F>\n\n    \u003Clabel>Message Body\u003C\u002Flabel>\n    \u003Ctextarea>Hello from the API Explorer!\u003C\u002Ftextarea>\n\n    \u003Cbutton onclick=\"sendRequest()\">Send Request\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\n  \u003Cdiv class=\"response-viewer\">\n    \u003Ch4>Response\u003C\u002Fh4>\n    \u003Cpre>\u003Ccode id=\"response\">\u003C\u002Fcode>\u003C\u002Fpre>\n  \u003C\u002Fdiv>\n\u003C\u002Fdiv>\n```\n\n### Interactive Docs Tools\n\n**OpenAPI-Based:**\n- Swagger UI\n- Redoc\n- Stoplight Elements\n\n**Custom Platforms:**\n- ReadMe.io\n- Postman Published Docs\n- Custom React components\n\n### Interactive Examples\n\nGo beyond single requests:\n\n```markdown\n## Interactive Tutorial: Send Your First Message\n\n### Step 1: Check your balance\n\u003Capi-explorer endpoint=\"GET \u002Faccount\u002Fbalance\" \u002F>\n\n### Step 2: Send a message\n\u003Capi-explorer endpoint=\"POST \u002Fmessages\"\n  body='{\"to\": \"+15551234567\", \"body\": \"Hello!\"}' \u002F>\n\n### Step 3: Check message status\n\u003Capi-explorer endpoint=\"GET \u002Fmessages\u002F{id}\"\n  params='{\"id\": \"{{previous.id}}\"}' \u002F>\n```\n\n## Common Failure Points\n\n### Failure Point Analysis\n\nTrack where developers fail and why:\n\n```javascript\n\u002F\u002F Instrument error events\napi.on('request_error', (error, request) => {\n  analytics.track('api_error', {\n    error_type: error.type,\n    error_code: error.code,\n    endpoint: request.endpoint,\n    time_since_signup: timeSinceSignup(),\n    is_first_call: isFirstCall()\n  });\n});\n```\n\n### Most Common First-Call Failures\n\n**1. Authentication Errors (40% of first-call failures)**\n```\nProblem: Wrong key, malformed header, missing auth\nFix:\n- Clearer error messages: \"API key should start with 'sk_test_'\"\n- Pre-filled code examples with actual key\n- Auth header format shown with example\n```\n\n**2. Request Format Errors (25%)**\n```\nProblem: Wrong content type, malformed JSON, missing fields\nFix:\n- Accept flexible content types on simple endpoints\n- Return specific field-level errors\n- Show exactly what was expected vs. received\n```\n\n**3. Environment\u002FSetup Errors (20%)**\n```\nProblem: SDK not installed, wrong SDK version, missing dependencies\nFix:\n- Version-specific installation instructions\n- Compatibility matrix clearly visible\n- Quick environment check script\n```\n\n**4. Rate Limiting (10%)**\n```\nProblem: Aggressive rate limits during exploration\nFix:\n- Generous sandbox limits (or none)\n- Clear rate limit errors with retry-after\n- Don't count failed requests against limits\n```\n\n**5. Networking Errors (5%)**\n```\nProblem: Firewall, proxy, SSL issues\nFix:\n- Connectivity test endpoint\n- Clear networking troubleshooting guide\n- Alternative ports\u002Fprotocols if possible\n```\n\n### Error Recovery Flows\n\nDesign error messages that recover the onboarding:\n\n```json\n{\n  \"error\": {\n    \"type\": \"authentication_error\",\n    \"message\": \"Invalid API key provided\",\n    \"code\": \"invalid_api_key\",\n    \"recovery\": {\n      \"steps\": [\n        \"Check that your API key starts with 'sk_test_' or 'sk_live_'\",\n        \"Ensure there are no extra spaces or newlines\",\n        \"Generate a new key at https:\u002F\u002Fdashboard.example.com\u002Fkeys\"\n      ],\n      \"docs\": \"https:\u002F\u002Fdocs.example.com\u002Fauthentication\",\n      \"support\": \"https:\u002F\u002Fsupport.example.com\u002Fauth-issues\"\n    }\n  }\n}\n```\n\n## The First-Call Experience Audit\n\n### Audit Checklist\n\nPerform this audit quarterly (or after any onboarding changes):\n\n**As a New Developer:**\n- [ ] Create a new account (use a fresh browser\u002Fincognito)\n- [ ] Time how long until you have a working API key\n- [ ] Follow the quickstart exactly as written\n- [ ] Make your first API call\n- [ ] Record total time and every friction point\n\n**Questions to Answer:**\n- How many clicks from homepage to first API call?\n- How many pages\u002Ftabs did you need open?\n- What did you have to figure out that wasn't explained?\n- Where did you get stuck or confused?\n- What would have made you give up?\n\n### Friction Point Scoring\n\n| Friction | Impact | Priority |\n|----------|--------|----------|\n| Must verify email before API key | High | Fix immediately |\n| API key buried in settings | High | Fix immediately |\n| No copy button on code examples | Medium | Fix this quarter |\n| Quickstart assumes specific OS | Medium | Fix this quarter |\n| Example uses outdated SDK version | Low | Fix when updating docs |\n\n## Onboarding Optimization Framework\n\n### Step 1: Measure Current State\n- Instrument TTFAC tracking\n- Run first-call audit with 5 developers\n- Identify top 3 drop-off points\n\n### Step 2: Reduce Steps\n- Can any step be eliminated entirely?\n- Can any step be deferred until later?\n- Can multiple steps be combined?\n\n### Step 3: Accelerate Remaining Steps\n- Pre-fill everything possible\n- Provide copy buttons everywhere\n- Show progress and next steps\n\n### Step 4: Recover Failures\n- Improve error messages\n- Add inline troubleshooting\n- Provide live support for stuck developers\n\n### Step 5: Measure and Iterate\n- Track TTFAC improvements\n- A\u002FB test onboarding changes\n- Regular audits with real developers\n\n## Tools\n\n### Onboarding Analytics\n- **Amplitude\u002FMixpanel**: Event tracking and funnels\n- **FullStory\u002FHotjar**: Session recording\n- **Custom dashboards**: TTFAC metrics\n\n### Interactive Docs\n- **ReadMe.io**: Full-featured developer hub\n- **Stoplight**: OpenAPI-powered docs\n- **Redocly**: API documentation platform\n- **Custom**: Build with React\u002FVue\n\n### Testing\n- **Ghost Inspector**: Automated onboarding testing\n- **Checkly**: API monitoring and testing\n- **k6**: Load testing of onboarding flows\n\n## Related Skills\n\n- **docs-as-marketing**: Quickstart documentation\n- **sdk-dx**: SDK that reduces onboarding complexity\n- **developer-sandbox**: The playground developers onboard with\n- **developer-audience-context**: Understanding your onboarding audience\n- **developer-metrics**: Measuring onboarding success\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fapi-onboarding",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fapi-onboarding",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill api-onboarding",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill api-onboarding",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill api-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fapi-onboarding\u002FSKILL.md",true,[53],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"README.md","REFERENCE","参考文档",1595,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fapi-onboarding\u002FREADME.md",[60,67,74,81,90,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]