Ext Ops Panel
Open dashboard
Comparison

skillers vs LoopSkill

skillers is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). LoopSkill is an MCP server published by wisechef-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceskillersLoopSkill
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.9.65
Forks (GitHub): 0
Stars (GitHub): 2
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

skillers vs LoopSkill
FactskillersLoopSkill
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)4 (better)2 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (app.loopskill.io/api/mcp/http)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-sh/skillersgithub.com/wisechef-ai/loopskill-api
Changes in the last 7 days (differs)20
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 39 h ago, requires a key

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

skillers

In its own words, on Claude Code: claude-plugins-community:

Learn from your workflow patterns and suggest skills, hooks, and agents to automate the repetitive work. Skillers reads your AI conversation transcripts (Claude Code, Codex CLI, OpenCode), extracts recurring patterns into themed weighted-knowledge files, then recommends concrete skills/hooks/agents to codify them. Two phases: `/skillers compact` analyzes transcripts and writes `.skillers/<theme>.md` knowledge files; `/skillers recommend` reads accumulated knowledge plus your existing plugin/skill ecosystem and suggests automations that don't already exist. The output is "here are 4 patterns I see you doing manually every week and the exact SKILL.md / hooks.json that would automate each."

LoopSkill

In its own words, on Official MCP Registry:

Search, install and compose AI agent skills, loops and bundles from the LoopSkill marketplace.

How to run each

skillers As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install skillers@claude-community

LoopSkill As a remote MCP server

Claude Code
claude mcp add --transport http loopskill https://app.loopskill.io/api/mcp/http/ --header "x-api-key: <YOUR_X_API_KEY>"

Requires: x-api-key header

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

Only LoopSkill has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: skillers · What it can do: LoopSkill · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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