git-worktrees vs Skills Anywhere
git-worktrees is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
git-worktrees is a plugin bundle for AI coding tools published by gabrielkoerich. No marketplace we read lists it any more. Skills Anywhere is an MCP server published by noteflowai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Skills Anywhere | |
|---|---|---|
| Community marketplace gabrielkoerich/skills | Removed on 2026-10-21 Version: not stated Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.19.0 Downloads/month (npm): 4 143 Downloads/week (npm): 1 160 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.19.0 Downloads/month (npm): 4 143 Downloads/week (npm): 1 160 Forks (GitHub): 1 Stars (GitHub): 7 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
| Fact | git-worktreesno longer listed · | Skills Anywhere |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 6 | 7 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (dsh-skills-anywhere) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/gabrielkoerich/skills | github.com/noteflowai/dsh-skills-anywhere |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of git-worktrees
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Git worktree management for parallel development workflows
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
Git worktree management for working on multiple branches simultaneously
-
Creates git worktrees for all open PRs or specific branches, handling branches with slashes, cleaning up stale worktrees, and supporting custom branch creation for development.
-
Git worktree workflow commands for task-based development
-
Replaces Claude Code's built-in worktree — aligns with native git worktree where CC diverges (HEAD base, origin/* auto-tracking) and adds layers native lacks…
What each says it does
git-worktrees
>
Skills Anywhere
Discover and load Agent Skills from configured local directories and Git sources over stdio MCP.
How to run each
git-worktrees
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Skills Anywhere As a local MCP server: npm package
claude mcp add --transport stdio dsh-skills-anywhere -- npx -y dsh-skills-anywhere mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: git-worktrees · What it can do: Skills Anywhere · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.