From linux-system-optimisation
First-run setup for linux-system-optimisation. Detects the machine's hardware (CPU, GPU, RAM, storage type, kernel, distro, DE, display server), asks the user where to store benchmark results (default ~/linux-system-optimisation/benchmarks/), installs missing benchmark tools, then runs the first tailored benchmark via the `benchmark` skill. Triggers on "set up linux-system-optimisation", "first run", or any optimise/benchmark request when no config exists.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin linux-system-optimisationThis skill uses the workspace's default tool permissions.
One-time setup. Establishes a benchmark-results store the user owns, profiles the hardware, and runs the first benchmark so subsequent `optimise` runs have something to read.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.
Share bugs, ideas, or general feedback.
One-time setup. Establishes a benchmark-results store the user owns, profiles the hardware, and runs the first benchmark so subsequent optimise runs have something to read.
Plugin config (small pointers only) lives at:
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/linux-system-optimisation/config.json
Benchmark results (user-owned data — they may want to inspect, version, share) live at a user-chosen path. Default suggestion: ~/linux-system-optimisation/benchmarks/. Store only the pointer in config.json:
{
"benchmarks_dir": "/home/<user>/linux-system-optimisation/benchmarks",
"system_profile": { "...": "see below" },
"first_run_at": "<ISO-8601>"
}
If config.json already exists, this skill is a no-op — surface that and suggest benchmark instead.
system_profile:
lscpu -J → model, vendor, cores/threads, base/max MHz, flags.lspci -nn | grep -iE 'vga|3d|display'; for NVIDIA also nvidia-smi -q | head -40; for AMD also glxinfo | grep -i 'opengl renderer'.free -h + dmidecode -t memory (sudo) for module-level info if available.lsblk -d -o NAME,ROTA,TRAN,MODEL,SIZE — distinguish NVMe / SATA-SSD / HDD.uname -r, lsb_release -ds or cat /etc/os-release.$XDG_CURRENT_DESKTOP, $XDG_SESSION_TYPE.sysbench stress-ng fio glmark2 vkmark mbw cpupower lm-sensors. Install missing ones via sudo apt install -y <pkg>. power-profiles-daemon is usually preinstalled on Ubuntu — check with systemctl status power-profiles-daemon.config.json with the profile and pointer.benchmark to run the first measurement. Don't re-prompt — the user just confirmed they want to set up.~/.claude/.$CLAUDE_USER_DATA — those are user-owned.