---
title: Your Agent Doesn't Know What the Community Already Figured Out
cover_image: 'https://raw.githubusercontent.com/itlackey/akm/main/docs/posts/akm-logo-sized.webp'
series: akm-knowledge
description: How to connect your agent to curated community knowledge with the Context Hub integration
tags:
  - ai
  - agents
  - cli
  - skills
published: true
id: 3363736
date: '2026-03-18T18:09:15Z'
---

This is part four in a series about managing the growing pile of skills, scripts, and context that AI coding agents depend on. In [part one](https://dev.to/itlackey/your-ai-agents-skill-list-is-getting-out-of-hand-32ck), I covered why progressive disclosure beats dumping everything into context. [Part two](https://dev.to/itlackey/you-already-have-dozens-of-agent-skills-you-just-cant-find-them) showed how `akm` unifies your local assets across platforms into one searchable stash. [Part three](https://dev.to/itlackey/your-agents-memory-shouldnt-disappear-when-the-session-ends) added remote context via OpenViking for teams that need persistent, shared knowledge. *(note: OpenViking is not supported in akm v1 — see [intro-part-03](intro-part-03.md) for details)*

All of that assumed you were building your own library from scratch. Your skills. Your knowledge docs. Your team's accumulated context. That's fine — and it's necessary — but it ignores a much larger resource: everything everyone else has already built.

Right now, there are high-quality skills and knowledge documents sitting in public repositories that solve problems you're going to hit next week. Prompt-chaining patterns. API integration guides. Framework-specific coding conventions. Stuff that experienced practitioners have refined and published, ready to use. Your agent has no idea any of it exists.

That's what the [Context Hub](https://github.com/andrewyng/context-hub) integration fixes.

## What Is Context Hub?

Context Hub is a public GitHub repository — originally curated by Andrew Ng's team — structured specifically for agent consumption. It organizes community-contributed knowledge and skills into a browsable, searchable hierarchy under a `content/` directory. Each entry is either a `DOC.md` (knowledge) or a `SKILL.md` (skill), with frontmatter metadata for descriptions, tags, languages, and versions.

Think of it like a curated package registry, except instead of code libraries, it's agent context. Each document is a self-contained piece of knowledge or a skill definition that any agent can pick up and use immediately. No installation, no dependencies, no build step.

The structure is intentionally simple:

```
content/
  openai/
    docs/
      chat-api/
        python/
          DOC.md
    skills/
      prompt-chaining/
        SKILL.md
  anthropic/
    docs/
      tool-use/
        typescript/
          DOC.md
```

Every entry gets indexed into the same search pipeline as your local assets, which means `akm` can search and display it the same way it handles anything else in your stash.

## One Command to Connect

If you already have `akm` installed:

```bash
akm add context-hub
```

That's the full setup. Under the hood, this adds the default Context Hub repository as a git source. It downloads the repo as an archive, extracts it into a local cache, and on the next `akm index`, every `DOC.md` and `SKILL.md` gets indexed into the same FTS5 search pipeline as your local assets.

The cache refreshes automatically every 12 hours. If the network is down, it falls back to stale cache for up to 7 days. Your local stash still works regardless — the Context Hub provider degrades gracefully without taking anything else down with it.

Verify it's registered:

```bash
akm list
```

You should see `context-hub` in the list alongside your local stash directories and any other providers you've configured.

## Search Works the Same Way

Here's what changes in practice: nothing about your workflow. You still run `akm search`. The difference is that results now include entries from Context Hub alongside your local assets.

```bash
akm search "prompt chaining patterns"
```

This might return a local skill you wrote last month *and* a community-contributed skill from Context Hub. The results are unified — same ranking, same format, same `type:name` refs. Context Hub assets go through the same scoring pipeline as everything else. No special handling, no second-class results.

Want to narrow it down to just skills?

```bash
akm search "api integration" --type skill
```

Or just knowledge documents?

```bash
akm search "coding standards" --type knowledge
```

The type filter applies across all sources — local, remote, and Context Hub alike.

## Show Works Too

When you find something useful, load it the same way you'd load any other asset:

```bash
akm show skill:prompt-chaining
```

Your agent gets the full content — frontmatter, description, the complete skill definition — in the same format as every other `akm show` result. It doesn't need to know the asset lives on GitHub. It doesn't need a GitHub token. It just works. The ref is `type:name`, same as a local asset.

Context Hub assets support the same view modes as local knowledge docs:

```bash
# Table of contents
akm show knowledge:chat-api toc

# A specific section
akm show knowledge:chat-api section "Authentication"

# A line range
akm show knowledge:chat-api lines 10 25
```

For large documents, the `toc` and `section` views keep context lean. Your agent can scan the table of contents first, then pull only the section it needs. Progressive disclosure all the way down.

## Custom Context Hub Repositories

The default `akm add context-hub` points at Andrew Ng's repository, but you're not limited to that. Any GitHub repository works as a git source — you don't need to follow a specific directory convention. `akm` walks the repo, classifies files by type, and indexes everything.

Say your organization maintains an internal knowledge base for agent context — API references, architecture decisions, coding standards:

```bash
akm add https://github.com/your-org/team-knowledge \
  --provider git \
  --name "team-knowledge"
```

Now `akm search` queries your team's knowledge base alongside the public Context Hub and your local stash. All in one search. You can add as many git sources as you want — each gets its own cache and index.

Need a specific branch instead of `main`?

```bash
akm add https://github.com/your-org/team-knowledge/tree/staging \
  --provider git \
  --name "team-staging"
```

The provider parses the GitHub URL and pulls the right branch automatically.

## What Your Agent Actually Sees

This is where the pieces from the whole series come together. After four posts, here's what a fully-wired `akm search` looks like from your agent's perspective:

```bash
akm search "deploy containers to production"
```

Results might include:

1. A local script from your primary stash — the deploy script you wrote last month
2. A team skill from an installed GitHub stash — the Docker Compose workflow your teammate packaged
3. A knowledge doc from OpenViking — the architecture decision about container orchestration from last sprint *(note: OpenViking is not supported in akm v1 — see [intro-part-03](intro-part-03.md) for details)*
4. A community skill from Context Hub — a battle-tested container deployment pattern that 50 other people have already vetted

Four different sources. One result set. One `akm show` command to load whichever one the agent needs. Everything else stays out of context.

The agent doesn't need to care about where an asset lives. Local file, managed source, OpenViking server, git repo — every result uses the same `type:name` ref. The agent searches, picks, loads, and gets to work.

## The Full Stack

Here's what the complete setup looks like after four posts:

```bash
# Install
curl -fsSL https://raw.githubusercontent.com/itlackey/akm/main/install.sh | bash
akm setup

# Local platform assets
akm add ~/.claude/skills
akm add .opencode/skills
akm add .cursor/rules

# Community and team stashes
akm add github:your-org/team-agent-toolkit
akm add @scope/deploy-skills

# Community knowledge (Context Hub is just a git repo)
akm add context-hub

# Team knowledge (any git repo works)
akm add https://github.com/your-org/team-knowledge \
  --provider git \
  --name team-knowledge

# Remote context server
akm add https://your-viking.internal:1933 \
  --provider openviking \
  --name team-context \
  --options '{"apiKey":"..."}'

# Build the local index
akm index
```

Drop the `AGENTS.md` snippet into every project:

```markdown
## Resources & Capabilities

You have access to a searchable library of scripts, skills, commands, agents,
knowledge, and memories via the `akm` CLI. Use `akm -h` for details.
```

And your agent has access to everything: local skills, platform assets, team stashes, community registries, remote knowledge, persistent memories, and curated community context. One search, one interface.

## Why This Matters

The value of agent skills and knowledge compounds when it's shared. A prompt-chaining pattern that one person refines over a weekend becomes infrastructure when a thousand agents can find it. A coding standard document that one team writes becomes a community resource when it's discoverable from any stash.

Context Hub isn't the only way this will happen — community registries, marketplace-style discovery, and decentralized skill sharing are all coming. But it's working today, it's open source, and it plugs directly into the same `akm search` / `akm show` workflow you're already using.

If you've written skills or knowledge docs worth sharing, consider contributing them to [Context Hub](https://github.com/andrewyng/context-hub). Structure them with frontmatter, put them in a `content/` directory, and they become searchable for every agent running `akm`.

The repo is at [github.com/itlackey/akm](https://github.com/itlackey/akm). Context Hub is at [github.com/andrewyng/context-hub](https://github.com/andrewyng/context-hub). If you've got a team knowledge base in a git repo, add it as a git source and let me know how it holds up.

---

*__Update (March 2026):__ This post was updated to reflect akm's current CLI. `akm add` replaces the earlier `akm stash add` for adding sources (including git and OpenViking providers), `akm setup` replaces `akm init`, and `akm list` replaces `akm stash list`. Sources (formerly "stash sources") are now managed through a single `akm add` / `akm remove` interface. If you're following along with an older version, `akm upgrade` will get you current.*


---

> **Note (2026-04-23):** This post has been updated to align with akm 0.6.0 terminology. Earlier wording referred to a *kit* and the *Kit Maker's Guide*; those terms have been renamed to *stash* and *Stash Maker's Guide* throughout. The pre-rename text is preserved in this repository's git history.
