From floating-clock
Build FloatingClock from source and install to /Applications, then launch. Use when user wants to install the floating-clock plugin's macOS app.
How this skill is triggered — by the user, by Claude, or both
Slash command
/floating-clock:installThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Install the FloatingClock macOS app from this plugin's source to `/Applications/` so it's available from Spotlight, Launchpad, and Finder.
Install the FloatingClock macOS app from this plugin's source to /Applications/ so it's available from Spotlight, Launchpad, and Finder.
Self-Evolving Skill: This skill improves through use. If the build, copy, or launch step breaks (signing change, path drift, macOS gatekeeper update) — fix this file immediately, don't defer. Only update for real, reproducible issues.
Resolve plugin root:
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/floating-clock}"
if [ ! -f "$PLUGIN_ROOT/Makefile" ]; then
echo "ERROR: plugin root not found at $PLUGIN_ROOT" >&2
exit 1
fi
Build, bundle, sign:
cd "$PLUGIN_ROOT" && make all
Copy to /Applications:
cp -R "$PLUGIN_ROOT/build/FloatingClock.app" /Applications/
Launch:
open /Applications/FloatingClock.app
Confirm:
Installed to
/Applications/FloatingClock.appand launched. The app is now discoverable via Spotlight (⌘Space → FloatingClock) and Launchpad. Right-click the clock for options.
After this skill completes, check before closing:
make all produce the expected build/FloatingClock.app? — If not, fix the Makefile or the build prerequisite.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.