get-api-docs
The get-api-docs skill provides a workflow for fetching current and accurate API documentation using the chub CLI tool instead of relying on training data. Use this skill when you need reliable, up-to-date library or API reference information, particularly before writing code that depends on specific API specifications or when uncertain about correct syntax and parameters.
git clone --depth 1 https://github.com/mxyhi/ok-skills /tmp/get-api-docs && cp -r /tmp/get-api-docs/get-api-docs ~/.claude/skills/get-api-docsSKILL.md
# Get API Docs via chub When you need documentation for a library or API, fetch it with the `chub` CLI rather than guessing from training data. This gives you the current, correct API. ## Step 1 - Ensure chub exists and get the latest instructions for using it Run ```bash chub --help ``` If this results in an error showing that chub does not exist, then install it first, and run it again. If the environment has node, npm, network access, and package-manager permission, install it as follows: ```bash npm install -g @aisuite/chub ``` ## Step 2 — Find the right documents If there is a conflict, follow the instructions from the output of chub --help since that will be the latest guidance. However, a key command for searching for the right documentation is chub search: ```bash chub search "<keywords>" --json ``` Pick the best-matching `id` from the results (e.g. `openai/chat`, `anthropic/sdk`, `stripe/api`). If nothing matches, try some broader terms. ## Step 3 — Fetch the docs Again, follow the latest instructions from chub --help instead of this if there is a conflict. But a key command for fetching the relevant docs is: ```bash chub get <id> --lang py # or --lang js, --lang ts ``` Remember to include the --lang parameter. ## Step 4 — Use the docs and leave feedback Read the fetched content and use it to write accurate code or answer the question. Do not rely on memorized API shapes — use what the docs say. Finally, after completing the task, if you discovered something not in the doc — a gotcha, workaround, version quirk, or project-specific detail — save it so future sessions start smarter: ```bash chub annotate <id> "Webhook verification requires raw body — do not parse before verifying" ``` Annotations are local, persist across sessions, and appear automatically on future `chub get` calls. Keep notes concise and actionable. Don't repeat what's already in the doc. Additionally, to help all developers, give feedback on the documentation using chub feedback, following the instructions in chub --help . Do not include secrets, source code, private architecture details, or other sensitive information in feedback comments.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
Autonomous iteration loop: modify, verify, keep/discard against any metric
Use when working with icons in any project. Provides CLI for searching 200+ icon libraries (Iconify) and retrieving SVGs. Commands: `better-icons search <query>` to find icons, `better-icons get <id>` to get SVG. Also available as MCP server for AI agents.
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
>
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.