From floating-clock
Quit FloatingClock, remove it from /Applications, and clear its saved preferences. Use when the user wants to completely uninstall the.
How this skill is triggered — by the user, by Claude, or both
Slash command
/floating-clock:uninstallThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Remove FloatingClock completely: terminate it, remove it from `/Applications/`, and clear its NSUserDefaults.
Remove FloatingClock completely: terminate it, remove it from /Applications/, and clear its NSUserDefaults.
Self-Evolving Skill: This skill improves through use. If the uninstall step misses a path (new pref domain, new auxiliary file) — fix this file immediately, don't defer. Only update for real, reproducible issues.
Confirm with the user first — uninstall is destructive:
AskUserQuestion(
header: "Uninstall",
question: "Remove FloatingClock from /Applications/ and clear all saved settings?",
options: [
{ label: "Yes, uninstall", description: "Quits app, removes bundle, clears preferences" },
{ label: "Cancel", description: "Do nothing" }
],
multiSelect: false
)
If cancelled, print Uninstall cancelled. and exit.
If confirmed:
pkill -f "FloatingClock.app/Contents/MacOS/floating-clock" 2>/dev/null || true
rm -rf /Applications/FloatingClock.app
defaults delete com.terryli.floating-clock 2>/dev/null || true
echo "FloatingClock uninstalled. (The plugin itself remains — remove it separately via 'claude plugin marketplace remove' if desired.)"
After this skill completes, check before closing:
defaults returned an error other than "not found", investigate.~/Library/Saved Application State/, log files, etc., and add to the cleanup if so.Only update if the issue is real and reproducible — not speculative.
npx claudepluginhub terrylica/cc-skills --plugin floating-clockGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.