Create or edit package README.md files in the AI SDK monorepo.
79%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/edit-package-readme/SKILL.mdKeep README.md files minimal; they must not contain documentation beyond simple starting points. Detailed documentation belongs exclusively in content/ and lives under https://ai-sdk.dev/docs.
Every package README.md file must contain the following, in the given order:
#) with a descriptive package title, not its npm identifier.## Setup: only one fenced, one-line npm i command, including necessary related packages.## Usage: only one fenced, basic getting-started code example (TypeScript or a framework component with TypeScript).See the [<package title> documentation](<url>) for more information. If none clearly fits, use 1–2 related docs links with custom phrasing.You must not include anything else in the readme. Any additional documentation belongs in content/.
Omit the optional note when it does not apply.
# <Package Title>
A brief description of the package.
-> **Note**: <Optional compatibility or experimental notice.>
## Setup
```bash
npm i <npm-package>
```
## Usage
```ts
import { example } from '<npm-package>';
await example();
```
See the [<package title> documentation](https://ai-sdk.dev/...) for more information.These packages have special-case README.md files and do not follow this format:
aicodemodprovider-utilsproviderNever consult these files for which README.md conventions to follow.
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.