Skip to content

Skills & Knowledge Hub

One source of truth for your AI agent's skills, prompts, knowledge, and plugins — managed in the dashboard and synced to every machine and agent with one command.

Your coding agent is only as good as the context it carries. The Hub keeps that context — skills, prompts, knowledge-base docs, and plugins — in one place, shared across your machines, your team, and all your agents, and kept up to date automatically.

A hub is a named collection. Create one or many: a personal hub for your own setup, a workspace hub your whole team shares, or a public hub anyone can subscribe to.

What a hub holds

KindWhat it is
SkillA SKILL.md (with optional bundled files) your agent loads on demand.
PromptA reusable prompt or system message.
KnowledgeA markdown doc your agent can read for project/domain context.
PluginA Claude Code plugin bundle.

Visibility levels

VisibilityWho can see it
PrivateOnly you.
WorkspaceEveryone in your account or organization.
PublicAnyone — discoverable and subscribable.

Create and fill a hub

In the dashboard:

Create a hub

New hub → name it and choose a visibility.

Add items

Three ways to add:

  • Direct — paste a skill, prompt, knowledge doc, or plugin.
  • From skills.sh — import any public GitHub repo that has a SKILL.md at its root (paste owner/repo or a raw SKILL.md URL).
  • From your coding agent — upload context you just produced with the MCP tool hub_add_item.

Every item is scanned for prompt injection before it can sync. Items that fail the scan are flagged and never written to a machine — you always see each item's verdict.

Sync to your machine

The anyr CLI pulls your hubs into a project's .claude/ tree and keeps them current — re-syncing only rewrites what changed and prunes what was removed.

# Pull every hub you can see (own + subscribed)
anyr skills sync

# Pull a single hub
anyr skills pull my-hub

# See what's available / what's installed
anyr skills list
anyr skills status

Each hub is downloaded to ~/.anyrouter/hubs/<slug>/ as a self-contained Claude Code plugin — skills/ for skills (and knowledge/prompts, wrapped so the agent can load them) and plugins/ for plugin items. Your own ~/.claude/skills is never touched.

Load a hub straight into a session

anyr claude --hub my-hub

Run anyr claude on its own and it lists your hubs so you can pick one. Either way the CLI syncs the hub, prints exactly what landed (with each item's scan verdict), then launches Claude Code with --plugin-dir pointed at the hub — so its skills load (namespaced anyrouter-my-hub:<skill>) and your agent starts with that context already in place.

Push from the command line

# Upload a local skill folder (needs a management key)
anyr skills push ./my-skill --hub my-hub

# Import from skills.sh / GitHub into a hub
anyr skills add owner/repo --hub my-hub

Manage from inside your coding agent (MCP)

Connect the AnyRouter MCP server and your agent gets hub tools:

  • list_hubs, get_hub, search_public_hubs — browse.
  • create_hub — start a new collection.
  • hub_add_item — persist a knowledge doc or skill you just wrote, so your whole team and every agent can sync it.
  • hub_import_skill — import a skill from skills.sh / GitHub.

Security

Skills, prompts, and knowledge become instructions in your agent's context, and plugins can run. The Hub scans every item for prompt-injection and unsafe patterns (instruction overrides, secret exfiltration, destructive commands, and more) on upload and on every edit. High-risk items are blocked from syncing; lower-risk findings are surfaced so you can decide. Nothing is loaded silently — the CLI prints exactly what it wrote, from which hub, with each scan verdict.