Ext Ops Panel
Open dashboard
Comparison

harness-scope vs io.github.YforC/antoskill

harness-scope is a plugin bundle for AI coding tools published by shimo4228. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.YforC/antoskill is an MCP server published by YforC. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceharness-scopeio.github.YforC/antoskill
Community marketplace davepoon/buildwithclaude Listed
Version: 0.1.5
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 117
Downloads/week (npm): 15
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

harness-scope vs io.github.YforC/antoskill
Factharness-scopeio.github.YforC/antoskill
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (antoskill)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/shimo4228/harness-scopegithub.com/yforc/antoskills
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

harness-scope

In its own words, on Community GitHub marketplaces:

A Claude Code mod that turns global skills, agents, instruction files (CLAUDE.md and rules) and tools on or off per repo through named profiles. A repo picks a profile with a one-line .claude/harness-scope.json; repos without the file are unchanged. It only reads: no file writes, network requests, child processes or model calls.

io.github.YforC/antoskill

In its own words, on Official MCP Registry:

A package manager for Agent Skills — discover, vet, and pin them across Claude Code and Codex.

How to run each

harness-scope As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install harness-scope@buildwithclaude

io.github.YforC/antoskill As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio antoskill -- npx -y antoskill

Requires: GITHUB_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of harness-scope publish no settings it asks for, so we do not compare settings.

What it can do: harness-scope · What it can do: io.github.YforC/antoskill · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built