Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel/write-api-reference
Produces API reference documentation for Next.js APIs: functions, components, file conventions, directives, and config options. **Auto-activation:** User asks to write, create, or draft an API reference page. Also triggers on paths like `docs/01-app/03-api-reference/`, or keywords like "API reference", "props", "parameters", "returns", "signature". **Input sources:** Next.js source code, existing API reference pages, or user-provided specifications. **Output type:** A markdown (.mdx) API refe
Passed 12 of 23 test cases with the skill, and 3 of 23 without it.
and 17 more in the full report
11 fixed1 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you write a complete API reference document for our framework's `<Form>` component? I need a standalone MDX page that documents its props, basic and advanced code examples with language switchers, essential usage caveats, and version history.
| Checked | Without skill | With skill |
|---|---|---|
| The output uses markdown code blocks with the switcher property rather than JSX Tabs components. | Missed | Passed |
| The props summary table includes a Prop header column. | Passed | Passed |
| Operational caveats use a Good to know section heading or blockquote format rather than warning callout containers. | Missed | Passed |
The instructions your model reads when the skill loads.
Produce an API reference page that documents a single API surface (function, component, file convention, directive, or config option). The page should be concise, scannable, and example-driven.
Each page documents one API. If the API has sub-methods (like cookies.set()), document them on the same page. If two APIs are independent, they get separate pages.
Identify which category the API belongs to, then follow the corresponding template.
cookies, fetch, generateStaticParams): signature, params/returns, methods table, examplesLink, Image, Script): props summary table, individual prop docs, examplespage, layout, route): definition, code showing the convention, props, behavior, examplesuse client, use cache): definition, usage, serialization/boundary rules, referencebasePath, images, etc.): definition, config code, behavioral sections---
title: {API name}
description: {API Reference for the {API name} {function|component|file convention|directive|config option}.}
---
{One sentence defining what it does and where it's used.}
```tsx filename="path/to/file.tsx" switcher
// Minimal working usage
```
```jsx filename="path/to/file.js" switcher
// Same example in JS
```
## Reference
test cases passed, vs 3 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.