OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Infrastructure

Open Agent Hub

Open Agent Hub is a TypeScript command-line utility that links reusable skills, expert-role agent prompts and slash commands into project workspaces or global configurations for AI coding assistants. Its built-in manager supports listing components, checking link status, selecting component types and choosing assistant targets.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Open Agent Hub — OpenViST project profile in Agent Infrastructure.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the built-in CLI when you want to manage skills, expert-role prompts and slash commands as linked components in an assistant’s project or global configuration. For a skills-only install, the README also provides a Vercel skills CLI route.

Who it is for

  • Developers who want to organize reusable prompt skills and commands within coding-assistant project workspaces.
  • Teams or individual developers who want shared components linked across projects through global assistant configurations.
  • Contributors maintaining modular skills, agent roles or slash-command collections for supported assistants.

Documented uses

  • List the repository’s available skills, agents and commands.
  • Link one named component or a selected category into a project or global configuration.
  • Choose an assistant target or a custom configuration directory for linked components.
  • Use the separately documented Vercel skills CLI to install all repository skills or one selected skill.
Before you choose

Requirements & limits

The project is publicly available on GitHub under the MIT license. Its documented interface is a CLI.

  • Project-level activation uses configuration directories within the current working directory; global activation uses user-level configuration paths.
  • Supported targets have different documented paths, so choose the target that matches the assistant you use.
  • The built-in manager covers skills, agents and slash commands; the alternate Vercel CLI instructions cover skills.
  • The README describes native plugin configurations for Claude Code, Codex and Cursor in addition to directory linking.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up the built-in CLI

Clone the repository and register its CLI manager for managing assistant capabilities.

Before you start

  • Git and npm, as used in the documented setup commands.

Steps

  1. Clone https://github.com/guanyang/open-agent-hub.git to a local directory.

  2. Change into the cloned repository directory.

  3. Run npm link to register the CLI manager and its documented aliases.

Expected outcome

The repository documents the CLI manager as registered for subsequent component management.

Guide limitations

  • This setup sequence does not itself activate skills, agents or commands.
  • The README’s later examples use the command name oah.
Documentation 1 ↗
Source-based practical guide

Enable a component in the current workspace

Link one named component into the default project-level assistant configuration.

Before you start

  • The repository cloned locally and its CLI manager registered, as described in the setup guide.
  • A supported component name and target assistant; project scope is the documented default.

Steps

  1. From the project workspace, run oah list to view scanned skills, agents and commands.

  2. Run oah enable to activate one named component.

  3. To choose a specific assistant configuration, use the documented --target= option, such as --target=cursor.

Expected outcome

The selected component is linked into the project-level configuration path for the selected target.

Guide limitations

  • The target must be one of the documented names: claude, antigravity, gemini, codex, cursor, trae, opencode or kiro.
  • The guide describes linking components; it does not establish how an assistant subsequently uses a particular component.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
13 October 2026
Original website title
guanyang/open-agent-hub · Official homepage title · retained in its source language
How we review sourcesSuggest a correction