Claude Code plugins for non-coding work: homelab, data, media and admin

I keep a lot of small Claude Code plugins on GitHub, and most of them have nothing to do with writing code. There are enough of them now that it's worth writing down what is in the pile, and which of them have already been retired (two, as it turns out).

So this is the inventory: thirteen plugins and four reference lists, all public, grouped by what they're for rather than alphabetically. Every plugin below is a set of skills and slash commands (some with agents) that Claude Code loads, and nearly all of them come from my plugin marketplace, which I wrote about in My Claude Code Projects Index & Plugin Marketplace.

I checked each repo before writing this. None is empty and none is private. Two are marked as superseded in their own READMEs, and I've said so where they come up.

Homelab and sysadmin

The pattern across these is that nothing about your own machines is baked into the plugin. Proxmox-Mgmt-Plugin manages a Proxmox VE host over SSH, with optional Proxmox API support. It has two skills: onboard, which captures the host, SSH user, web URL, node name and (optionally) API token references, and proxmox-maintenance, which covers VM and container lifecycle (qm, pct), storage and ZFS inspection, log review and update workflows. The host details live outside the plugin, in $CLAUDE_USER_DATA/proxmox-mgmt/config.json, so the same install works against several hosts and survives updates.

Synology-Mgmt-Plugin is the same idea for a Synology NAS: SSH-driven file operations, share listing, volume, RAID and SMART status, snapshot inspection, and DSM API access. It needs the SSH service enabled in DSM (Control Panel, Terminal & SNMP) and an admin account.

Claude-Sysadmin-Homelab-Plugin was the broader version: diagnose, status, config, services, logs, alias and hardware-probe commands for remote servers, container hosts, NAS boxes and single-board computers. Its README now says it is superseded (2026-10-23), merged into Ubuntu-Admin and removed from the marketplace. The repo stays up for reference, so don't install it.

For the desktop rather than the server there's Claude-Code-Linux-Desktop-Slash-Commands, a library of 93+ slash commands for Linux desktop administration (Ubuntu 25.04+ is the stated target). Its setup script builds a dedicated workspace at ~/claude-spaces/desktop-sys-admin, syncs the commands in, and writes a CLAUDE.md plus a system-info file (CPU, GPU, RAM, OS, network). That one isn't a marketplace plugin, you run the script.

Data

Two plugins that split the work in a way I like: one looks at data, the other fixes it. Claude-Data-Analyst-plugin is for a first pass over a CSV, Parquet or Excel file. Its skills include correlation analysis, a PII scan, anomaly sweeps, hypothesis testing, trend narration, multivariate analysis, a data dictionary builder, and a few I find more interesting than the headline ones: forensic-sweep (flags data that looks suspiciously clean, imputed or smoothed, so you know what happened upstream) and sample-size (the effective sample per question, with a go or no-go verdict). setup-data-workspace loads the files into DuckDB. It leans on duckdb, csvkit, miller and uv being on your path.

Claude-Data-Wrangler-plugin is the cleaning side: a cleanliness scan for columns likely to fail SQL ingestion, country-name standardisation, parsing strings like $4.27 or (500) into numbers, Unicode and mojibake repair, date conversion (ISO 8601, epoch, fiscal), ISO code enrichment, data dictionaries, CSV and JSON conversion, and proposing a normalised SQL schema from a flat file. Visualisation is explicitly out of scope.

Media: images, audio, press

Claude-Image-Production-Plugin (version 2.0.0 in its README) is batch work on image libraries: filters, background removal, cropping, resizing, compression, WebP conversion, plus a pile of organisers (by resolution, aspect ratio, orientation, format, EXIF capture time or camera), duplicate detection with perceptual hashing, and a install-deps skill that provisions ImageMagick, exiftool and a uv virtualenv with Pillow.

Claude-Audio-Production-Plugin is ffmpeg-first. The distinctive part is a voice-profile workflow: you register a microphone, it takes a reference sample, analyses it with librosa, and generates EQ and dynamics presets bound to that mic, with A/B audition files so you can hear before and after. There's also a light-edit skill that runs a whole spoken-word chain on one file. Transcription and diarisation are deliberately left to the companion Transcription-Pipeline, which has its own write-up.

Claude-PR-Media-Work-Plugin is the odd one out here: press and comms rather than files. It fetches and archives articles by date, searches and analyses the archive, and drafts media pitches, holding statements and responses, with a comms-strategy set of commands (competitive scan, campaign framework) on top.

Personal admin and planning

Claude-Budgeting-Plugin handles household budgeting: logging and bulk-importing transactions, categorising them (it learns merchant to category rules), building monthly budgets, forecasting cash flow over 3, 6 or 12 months, goal tracking and monthly reports. A provisioning command scaffolds a fresh budgeting workspace. The plugin holds the logic and the workspace holds your data, so updating the plugin never touches your numbers.

Claude-Career-Plugin covers logging roles of interest, comparing offers, tracking applications, salary benchmarking, CV tailoring, cover letters and interview prep, with three workspace variants (career planning, job search, salary research). It absorbed three earlier template repos. Its optional Hunter MCP is not installed automatically.

Claude-Filesystem-Organiser-Plugin scans, dedupes, flattens, renames and sorts local directories and Google Drive (via rclone). Its README marks it superseded as of 2026-10-27 by a private successor, folder-cleanup. It still works and is still listed, but it isn't being developed.

Claude-Ideation-Planning-Plugin captures ideas (text, URL or voice note), runs ideation batches, scores them with an ICEC-style scorecard, ranks them, and can run a six-persona council over one. Its sibling Claude-Business-Idea-Eval-Plugin is the business-specific version: VC-style review, TAM analysis, B2B or B2C fit, assumptions and objections, a council review, and exports to PDF. The council skill can also clone and run Karpathy's llm-council.

The lists

Four repos aren't plugins at all. Claude-Code-MCP-List is a short list of MCP servers for Claude Code, in 16 categories from browser automation to data science (it's headed as last updated 2025-10-28, so treat it as a starting point). Claude-Slash-Commands is my slash command collection and also the index for standalone single-command repos. Non-Code-Claude-Code gathers non-development uses of Claude Code (finance, learning, multi-agent ideation, personal planning), and says openly that my own projects are over-represented because copying them in is quicker than searching for others' work. The Linux desktop commands repo above is the fourth.

Non-Code-Claude-Code also states the idea behind most of this better than I would: a repository, meaning a delineated part of a filesystem, is a surprisingly effective frame for prototyping agentic workflows. A plugin is that, made portable.

Installing

Most READMEs give one of two forms. Add the marketplace once, then install by name:

/plugin marketplace add danielrosehill/Claude-Code-Plugins
/plugin install image-production@danielrosehill

Or, from the shell, the equivalent claude plugins install form, which is what the Proxmox, Synology, Data Analyst and Data Wrangler READMEs show:

claude plugins install proxmox-mgmt@danielrosehill

The plugin names I took from the READMEs are proxmox-mgmt, synology-mgmt, data-analyst, data-wrangler, image-production, audio-production, budgeting, pr-media-work, ideation-planning and business-idea-eval. The Career README doesn't state an install line, so check the marketplace for its name. The two superseded plugins should be skipped.

Most plugins start with an onboard or new-workspace step that asks about your setup and writes it to a user-data directory, not into the plugin itself. Run that first.

What I'd say about the whole set

Two of the thirteen are already superseded (one merged into a bigger admin plugin, one replaced by a private successor). The pattern that has survived is the one in the Proxmox and Budgeting plugins: logic in the plugin, your specifics in a separate data directory. That's what lets an update land without touching anything you care about.

If you only try one, try the Data Analyst's forensic-sweep on a dataset you've been told is clean.