Proofreader Api

If you're wiring up the browser's built-in Proofreader API into a text editor or form, this skill keeps you from misreading the spec. It walks through feature detection, availability checks, monitored model downloads, session lifecycle, and the quirks around correction metadata and permissions-policy constraints. The procedures are opinionated about when to gate creation behind user activation, how to handle download progress, and why you shouldn't reuse destroyed sessions. Worth using if you're integrating client-side proofreading and want to avoid the common traps around option mismatches, quota failures, and browser-specific fallbacks. Don't reach for it if you're doing server-side LLM work or general prompt engineering.

skills.sh installs: 152
GitHub stars: 31
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add webmaxru/agent-skills --skill proofreader-api --agent claude-code

Installs into .claude/skills of the current project.

Files

Proofreader API

Procedures

Step 1: Identify the browser integration surface

Inspect the workspace for browser entry points, editor or form UI handlers, and any existing built-in AI abstraction layer.
Execute node scripts/find-proofreader-targets.mjs . to inventory likely frontend files and existing Proofreader API markers when a Node runtime is available.
If a Node runtime is unavailable, inspect the nearest package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary.
If the workspace contains multiple frontend apps, prefer the app that contains the active text-entry route, editor component, or user-requested proofreading surface.
If the inventory still leaves multiple plausible frontend targets, stop and ask which app should receive the Proofreader API integration.
If the project is not a browser web app, stop and explain that this skill does not apply.

SKILL.md on GitHub