Context Hub
- 24 installs
- 33 repo stars
- Updated April 23, 2026
- andrewyng/context-hub-skill
context-hub is a Claude Code skill that fetches current documentation, setup guidance, and workflow instructions through the chub (Context Hub) CLI when up-to-date information matters more than model memory.
About
This skill directs the agent to use the chub (Context Hub) CLI whenever current docs, setup guidance, or workflow instructions matter more than model memory. A developer uses it before coding against a library or when the user asks for the latest docs, model, or API behavior. It ensures chub is installed, runs chub help as the source of truth, then fetches docs with chub search and chub get and can save local notes and feedback.
- Routes to Context Hub (chub) for current docs, models, and setup guidance
- 5-step flow: ensure chub, run chub help, fetch, annotate, leave feedback
- Treats chub help output as the source of truth over the skill file itself
Context Hub by the numbers
- 24 all-time installs (skills.sh)
- Ranked #972 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
context-hub capabilities & compatibility
Free CLI; requires npm install of @aisuite/chub and network access.
- Capabilities
- api docs fetch · documentation lookup · current docs retrieval
- Works with
- openai · anthropic
- Use cases
- documentation · api development
- Pricing
- Free
What context-hub says it does
Use this skill whenever current docs, current setup guidance, or current workflow instructions matter.
If this file and `chub help` ever disagree, follow `chub help`.
npm install -g @aisuite/chub
npx skills add https://github.com/andrewyng/context-hub-skill --skill context-hubAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 24 |
|---|---|
| repo stars | ★ 33 |
| Last updated | April 23, 2026 |
| Repository | andrewyng/context-hub-skill ↗ |
What it does
Pull current documentation, model names, and workflow guidance via the chub CLI when up-to-date information matters more than model memory.
Who is it for?
Developers who need the latest docs, model names, or setup steps for a library and want current reference over the model's memorized knowledge.
Skip if: Environments where chub installation is blocked (no node, npm, network, or package-manager permission).
When should I use this skill?
When the user mentions the latest docs, latest model, chub, or Context Hub, or whenever current documentation matters more than model memory.
What you get
The agent uses fetched current docs as authority for API shapes, setup steps, versions, and model names.
- Current docs or skill fetched via chub
- Local annotations and feedback on doc entries
By the numbers
- 5-step workflow (ensure chub, chub help, use, annotate, feedback)
- 10 valid feedback labels listed
Files
Context Hub
Use this skill whenever current docs, current setup guidance, or current workflow instructions matter. Trigger it immediately when the user mentions the latest docs, latest model, chub, or Context Hub. Keep the workflow simple: ensure chub exists, run chub help, then follow the guidance it returns.
If this file and chub help ever disagree, follow chub help.
1. Ensure chub exists
Check whether chub is already installed:
command -v chub >/dev/null 2>&1If that fails, and the environment has node, npm, network access, and package-manager permission, install it:
npm install -g @aisuite/chubIf installation is blocked, tell the user exactly what is missing instead of guessing.
2. Always start with chub help
Run:
chub helpTreat that output as the source of truth for the installed CLI version.
3. Use Context Hub instead of guessing
Typical flow:
chub search "<library or workflow>" --json
chub get <id> --lang pyUse the fetched docs or skill as the authority for API shapes, setup steps, versions, model names, model configuration, and workflow guidance.
4. Save concise local notes
If you discover a short project-specific note that should appear next time, save it:
chub annotate <id> "Concise project-specific note"Use annotations only for notes that are local, actionable, and worth seeing on future fetches.
5. Leave feedback after using an entry
Unless the user explicitly tells you not to, always leave feedback after using a doc or skill:
chub feedback <id> up --label accurate "What was useful"
chub feedback <id> down --label outdated "What needs fixing"Valid labels: accurate, well-structured, helpful, good-examples, outdated, inaccurate, incomplete, wrong-examples, wrong-version, poorly-structured.
Do not include secrets, source code, private architecture details, or other sensitive information in feedback comments.
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.451k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.391k15.9kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.387k15.9k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k72Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k72
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.267k192kFAQ
What is the source of truth for this skill?
The output of chub help; if the skill file and chub help disagree, follow chub help.
How do I install chub?
If node, npm, network access, and package-manager permission are available, run npm install -g @aisuite/chub.