pickfit

BrowseDeveloper CLIs

open-agent-hub

CLI tool to link skills, agents, and commands into AI coding assistants.

Tested on Linux

Use it

Linux x86_64

  1. git clone https://github.com/guanyang/open-agent-hub.git ~/open-agent-hub

    git clone https://github.com/guanyang/open-agent-hub.git ~/open-agent-hub
  2. npm link registers oah/open-agent-hub aliases

    cd ~/open-agent-hub && npm link
  3. install jq to ~/.local/bin for oah sync dependency

    curl -L -o /tmp/jq https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64 2>&1 && chmod +x /tmp/jq && mkdir -p ~/.local/bin && cp /tmp/jq ~/.local/bin/jq && ~/.local/bin/jq --version
Where the README and reality differ
  • README: oah sync works out of the box (zero-dependency)
    What worked: needs jq installed; without it oah sync exits with 'jq is required but not installed'

Check that it works

which oah && oah --help 2>&1

The output should contain “open-agent-hub 能力管理中心 CLI”.

First thing to try

oah list 2>&1

What it does

  • Link skills agents commands to workspaces
    Tested
  • List available skills agents commands
    Tested
  • Sync skills from upstream sources
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 2 of 3 features work
  4. Works offline

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 2 Nov 2026
  • Version 1.0.0

Differences the test machine hit

  • README: oah sync copies upstream skills
    In the test: script calls rsync which is missing on minimal Debian; it prints 'rsync: command not found' but still reports success
  • README: install step 3 runs jq
    In the test: nothing to change; a note: the box ran jq, downloaded, without reading it first, so pickfit did not inspect it

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.