# Context Hub

> Use this skill when the user asks for the latest docs, latest model, latest setup guidance, latest API behavior, or explicitly mentions chub or Context Hub. Use it by default whenever current documentation or current workflow guidance matters more than model memory. Ensure `chub` is available, run `chub help`, then use Context Hub to fetch the current docs or skill needed for the task.

- Skill: `andrewyng/context-hub` (Agent Skill)
- Install (CLI): `npx skillmds@latest add andrewyng/context-hub`
- Raw SKILL.md: https://api.skillmd.com/api/skills/andrewyng/context-hub/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: andrewyng (https://skillmd.com/u/andrewyng)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/andrewyng/context-hub

---


# 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:

```bash
command -v chub >/dev/null 2>&1
```

If that fails, and the environment has `node`, `npm`, network access, and
package-manager permission, install it:

```bash
npm install -g @aisuite/chub
```

If installation is blocked, tell the user exactly what is missing instead of
guessing.

## 2. Always start with `chub help`

Run:

```bash
chub help
```

Treat that output as the source of truth for the installed CLI version.

## 3. Use Context Hub instead of guessing

Typical flow:

```bash
chub search "<library or workflow>" --json
chub get <id> --lang py
```

Use 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:

```bash
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:

```bash
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.