- Add examples/scripts/smart-suggest-roi.py: stdlib-only analyzer correlating suggestion log with session JSONL files to measure command acceptance rate. 4 acceptance signals, tier breakdown, daily trend, --json/--since/--no-sessions CLI. - Tune Aristote smart-suggest hook: tighten 5 over-firing triggers (/tech:commit, /tech:sonarqube, /tech:dupes, /check-conventions a11y, /tech:worktree) - Guide: identity re-injection hook, context engineering maturity grid, code review workflow, 1M context window GA update, Spring Break promo, security audit patterns - Resource evaluations: Nick Tune hooks (3/5), VicKayro security audit (2/5), Karl Mazier CLAUDE.md templates, Paul Rayner ContextFlow, Siddhant agent trace, Andrew Yng context hub, JP Caparas 1M context window Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.9 KiB
Resource Evaluation: Context Hub (andrewyng/context-hub)
Date: 2026-03-16 Source: LinkedIn post (text) + https://github.com/andrewyng/context-hub Type: Open-source CLI tool Author: Andrew Ng (andrewyng) Score: 2/5
Summary of Content
- What it is: A CLI tool (
chub) providing coding agents with curated, versioned API documentation as markdown files - Core commands:
chub get openai/chat --lang pyto fetch API docs;chub annotate <id> "note"for persistent cross-session annotations - Corpus: 602+ documentation entries (as of 2026-03-16), covering OpenAI, Anthropic, Stripe, AWS, and others
- Community loop: Users vote on doc quality (
chub feedback), surfacing improvements to maintainers - Claude Code integration: SKILL.md support for dropping into
~/.claude/skills/ - License: MIT, 6,342 stars
Score: 2/5
Justification: One genuinely novel feature (cross-session persistent annotations on external API docs) that Context7 cannot replicate. Everything else overlaps with existing guide coverage: Context7 already handles versioned library docs, @url natively pulls live documentation into Claude Code context, and anti-hallucination patterns are already documented. The annotation use case is real but solves a narrow problem. No production benchmarks, no independent validation.
Comparative Analysis
| Aspect | Context Hub | Our Guide |
|---|---|---|
| Curated API docs for agents | New CLI approach | Not covered as dedicated tool |
| Cross-session doc annotations | Unique feature | Not covered |
| Official library docs lookup | Overlaps with Context7 | Covered (Section 8, Context7) |
| Live URL context | Overlaps with native @url |
Covered (native Claude Code) |
| Agent hallucination prevention | Indirect angle | Covered but scattered |
| Maintenance/freshness guarantees | Community-maintained, lag risk | N/A |
Challenge Notes (technical-writer agent)
Key pushbacks:
- Stars ≠ adoption: 6,342 stars driven by Andrew Ng's social amplification, not production validation
- Context7 overlap not demonstrated:
chub get openai/chat --lang pyvs Context7'squery-docs— the evaluation doesn't prove the concrete gap - Annotation is the only novel angle: and it got buried — it's the one feature Context7 cannot replicate
- Hallucination framing is a stretch: community-maintained docs introduce a trust problem Context7 avoids (official sources)
- Missing:
@urlnative alternative: Claude Code already pulls live docs natively, weakening the "gap" case - Missing: maintenance risk: update lag when APIs change vs. Context7's live resolution
- Risk of not integrating: Low — existing guide coverage (Context7,
@url, grepai) handles most use cases
Fact-Check
| Claim (from LinkedIn post) | Verdict | Notes |
|---|---|---|
| "Andrew Ng just dropped" | Verified | Repo owner is andrewyng, not a fork |
| "68+ APIs" | False | Actual corpus: 602+ entries as of 2026-03-16 |
| "One of the fastest accelerating new repos" | Unverifiable | 6,342 stars in ~5 months; no public velocity data |
| "100% free & open source (MIT)" | Verified | MIT confirmed in license file |
Corrections: The "68+ APIs" figure is either from an early snapshot or fabricated. Real coverage is ~9x larger. The LinkedIn post is marketing-inflated.
Recommendation
Action: Do not integrate — one-line mention only.
If mentioned at all, one sentence under the Context7 entry in Section 8 (MCP servers): "For teams requiring persistent annotations on external API docs across sessions, see context-hub."
No section, no dedicated coverage, no hallucination-prevention framing. Revisit if production use cases emerge in the community.
Confidence: High (fact-check complete, challenge addressed)