api-onboarding

api-onboarding is a skill for Claude Code, Codex from jonathimer/devmarketing-skills. It costs 104 tokens per session (2,946 once invoked), scanned A, original, MIT.

A guide for reducing the time between discovering an API and successfully making the first API request. It covers authentication, test environments, interactive documentation, and common points of failure.

In plain words
What is it for?
Use it to measure first-call time, simplify sign-in, plan sandbox environments, improve API documentation, and fix onboarding problems.
Why use it?
It helps find and remove the steps that cause developers to abandon an API before using it.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/jonathimer/devmarketing-skills/api-onboarding
Any agent
npx skills add jonathimer/devmarketing-skills --skill api-onboarding
Clone the repo
git clone --depth 1 https://github.com/jonathimer/devmarketing-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for api-onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/api-onboarding.svg)](https://agentmods.dev/skills/jonathimer/devmarketing-skills/api-onboarding)
Your own site
<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/api-onboarding"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/api-onboarding.svg" alt="Measured on agentmods" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,946 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00104 $0.02946
Opus 5 $0.00052 $0.01473
Sonnet 5 $0.00021 $0.00589
Haiku 4.5 $0.00010 $0.00295

Measured 4d ago against content hash af61320c469a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-onboarding scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -H "Authorization: Bearer sk_test_YOUR_KEY" ...
skills/api-onboarding/SKILL.md · 462 lines

How it starts

The opening of the file, as written. The whole thing — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reducing Time-to-First-API-Call

The 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.

Overview

Time-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.

This skill covers:

  • Measuring and optimizing TTFAC
  • Removing authentication friction
  • Creating effective sandbox environments
  • Building interactive documentation
  • Identifying and fixing common failure points

Before You Start

Review the developer-audience-context skill to understand:

  • What's the typical technical sophistication of your developers?
  • What tools and environments do they commonly use?
  • What alternative products have they tried? What was their experience?
  • What's their urgency level? (Evaluating vs. building immediately)

Your onboarding should meet developers where they are.

Understanding TTFAC

What TTFAC Measures

Time-to-First-API-Call measures the elapsed time from a developer's first interaction to their first successful API response. This includes:

  1. Discovery time: Finding the "Get Started" content
  2. Signup time: Creating an account
  3. Credential time: Obtaining API keys
  4. Setup time: Installing SDK, configuring environment
  5. Execution time: Running first request
  6. Success time: Receiving successful response

TTFAC Benchmarks

Rating TTFAC Developer Experience
Excellent < 5 min "This is amazing"
Good 5-15 min "Pretty straightforward"
Acceptable 15-30 min "Got there eventually"
Poor 30-60 min "This is frustrating"
Failing > 60 min "I'll try something else"

Measuring TTFAC

Instrumentation points:

// Track these events with timestamps
analytics.track('docs_quickstart_viewed');
analytics.track('signup_started');
analytics.track('signup_completed');
analytics.track('api_key_created');
analytics.track('sdk_installed');     // Via package manager data
analytics.track('first_api_call');    // Via API logs
analytics.track('first_successful_call');

Read the full file on GitHub · 462 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 462 lines · 104 tokens per session scan A af61320c469a

Subscribe to this mod's changes

api-onboarding is a skill published in the GitHub repository jonathimer/devmarketing-skills (86 stars, last pushed 6mo ago), licensed MIT. It adds 104 tokens to every session and 2,946 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens