context-hub
Skill42 starsChanged 7 months agoMITView on GitHub
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.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- hongphuc5497/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- hongphuc5497/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill whenever current docs, current setup guidance, or current workflow instructions matter.
- Very specific: line 17
If this file and chub help ever disagree, follow chub help.
- Very specific: line 21
Check whether chub is already installed:
- Very specific: line 27
If that fails, and the environment has node, npm, network access, and package-manager permission, install it:
- Distinctive: line 34
If installation is blocked, tell the user exactly what is missing instead of guessing.
- Distinctive: line 45
Treat that output as the source of truth for the installed CLI version.
- Distinctive: line 56
Use the fetched docs or skill as the authority for API shapes, setup steps, versions, model names, model configuration, and workflow …
- Distinctive: line 61
If you discover a short project-specific note that should appear next time, save it:
- Distinctive: line 68
Use annotations only for notes that are local, actionable, and worth seeing on future fetches.
- Distinctive: line 85
Do not include secrets, source code, private architecture details, or other sensitive information in feedback comments.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.