Skill

update-profile

Surgical edits to the desktop-manager machine profile without re-running full onboarding. Use when a single field changed — e.g. user upgraded distro, switched from X11 to Wayland, swapped GPU, changed sudo policy, added a service to watch, recorded a new hardware quirk. Reads and writes `$CLAUDE_USER_DATA/desktop-manager/profile.json`. Triggers on phrases like "update desktop profile", "I switched to wayland", "add a quirk", "change sudo mode".

npx claudepluginhub danielrosehill/claude-code-plugins --plugin desktop-manager

Tool Access

This skill uses the workspace's default tool permissions.

Preview

For one-off field changes against an existing profile. If the user wants a wholesale re-profile, run `/desktop-manager:onboard` instead.

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars1

Forks0

Last CommitApr 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

desktop-manager: update-profile

For one-off field changes against an existing profile. If the user wants a wholesale re-profile, run /desktop-manager:onboard instead.

Workspace resolution

PLUGIN_DATA_DIR="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/desktop-manager"
PROFILE_FILE="$PLUGIN_DATA_DIR/profile.json"

If $PROFILE_FILE doesn't exist, point the user at /desktop-manager:onboard and stop. Don't bootstrap a partial profile from this skill.

Arguments

$ARGUMENTS is parsed as <field-path> [new-value]. Examples:

desktop.session_type wayland
policies.sudo_mode passwordless
packaging.preferred_for_gui_apps flatpak
services_of_interest +bluetooth (append)
services_of_interest -bluetooth (remove)
quirks +"AMDGPU resets randomly under heavy load" (append free-form)
hardware.gpu (no value → re-detect just this field via lspci -k)

If no arguments, show the user the current profile and ask which field they want to change.

Procedure

Load $PROFILE_FILE. If version doesn't match what this plugin understands (currently 1), refuse and tell the user to re-onboard.
Resolve the field. Walk the JSON path. If the path doesn't exist, reject with the closest sibling suggestion — don't silently create new top-level fields.
Compute the new value:
- Bare new-value → set the field.
- +value on a list field → append (deduplicate).
- -value on a list field → remove.
- No value given → re-run the auto-detection probe for that field from onboard's table and propose the result.
Diff and confirm. Show old value, new value. Wait for explicit user confirmation.
Write. Update last_profiled to now (UTC ISO-8601). chmod 600 "$PROFILE_FILE".
Tell the user what changed and which commands are affected. For example, if desktop.session_type flipped to wayland, mention that troubleshoot-hardware will now use wlr-randr instead of xrandr.

Editable fields

See lib/PROFILE.md for the full schema. All fields in there are user-editable except version, which is owned by the plugin.