Ext Ops Panel
Open dashboard
Comparison

remote-system-maintenance vs Snap-It (BTRFS Snapshots)

remote-system-maintenance is a plugin bundle for AI coding tools published by 2389-research. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Snap-It (BTRFS Snapshots) is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
Marketplaceremote-system-maintenanceSnap-It (BTRFS Snapshots)
Claude Code: claude-plugins-community Listed
Version: dbb92f1
Forks (GitHub): 8
Stars (GitHub): 97
Not marked · First seen
Not listed
Community marketplace danielrosehill/claude-code-plugins Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
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

remote-system-maintenance vs Snap-It (BTRFS Snapshots)
Factremote-system-maintenanceSnap-It (BTRFS Snapshots)
Marketplaces that list it11
Stars (GitHub) (differs)97 (better)1 (worse)
Forks (GitHub) (differs)8 (better)0 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published10
Licence (differs)Not statedMIT
Repository (differs)github.com/2389-research/claude-pluginsgithub.com/danielrosehill/claude-snap-it-plugin
Changes in the last 7 days (differs)12
First seen (differs)2026-10-112026-10-15

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

remote-system-maintenance

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

Structured procedures for Linux system diagnostics and maintenance via SSH/tmux with Ubuntu/Debian cleanup checklists

Snap-It (BTRFS Snapshots)

In its own words, on Community GitHub marketplaces:

Manage BTRFS snapshots via snapper and btrfs from Claude Code — create, list, diff, rollback, and prune subvolume snapshots. Includes /snap and /snap-before commands for one-shot and pre/post-paired snapshots around risky changes.

How to run each

remote-system-maintenance As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install remote-system-maintenance@claude-community

Snap-It (BTRFS Snapshots) As a Claude Code plugin

Claude Code
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install snap-it@danielrosehill

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

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

What it can do: remote-system-maintenance · What it can do: Snap-It (BTRFS Snapshots) · 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. 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