- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mxyhi/ok-skills --skill get-api-docs -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mxyhi/ok-skills --skill get-api-docs -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mxyhi/ok-skills --skill get-api-docs -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add mxyhi/ok-skills --skill get-api-docs -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/mxyhi/ok-skills/tree/HEAD/get-api-docsFrom the publisher
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.
Run
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:
npm install -g @aisuite/chub
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:
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.
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:
chub get <id> --lang py # or --lang js, --lang ts
Remember to include the --lang parameter.
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:
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.
>
---name: get-api-docsdescription: >---# get-api-docs/SKILL.mdFAQ
Download get-api-docs/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/mxyhi/ok-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.