About launch
launch is a skill that opens the FloatingClock app on macOS. It prefers the installed application and falls back to a local build when needed.
Key features
- 01Open the installed app
- 02Fall back to a local build
Use cases
- 01Launch FloatingClock from its installed location
- 02Open a local build when the app is not installed
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ terrylica/ cc-skills --skill launchAfter installing, type/launchin Claude Code to confirm it loaded.
Details
From the project README/floating-clock:launch
Open the FloatingClock app.
Self-Evolving Skill: This skill improves through use. If the launch path or fallback logic breaks — fix this file immediately, don't defer. Only update for real, reproducible issues.
Steps
Prefer the installed app; fall back to the local build if the user hasn't installed yet:
if [ -d /Applications/FloatingClock.app ]; then
open /Applications/FloatingClock.app
echo "Launched from /Applications/"
else
PLUGIN_ROOT="$(cc-plugin-root floating-clock)"
LOCAL_APP="$PLUGIN_ROOT/build/FloatingClock.app"
if [ -d "$LOCAL_APP" ]; then
open "$LOCAL_APP"
echo "Launched from local build at $LOCAL_APP"
echo "Tip: run /floating-clock:install to put it in /Applications/ for Spotlight access."
else
echo "No app found. Run /floating-clock:install first."
exit 1
fi
fi
Post-Execution Reflection
After this skill completes, check before closing:
- Did
opensucceed silently? — If macOS surfaced a gatekeeper prompt, document the bypass. - Did the fallback to local build trigger when expected? — If the user has the installed app but it's stale, the system path wins; that's intentional.
- Did paths drift? —
/Applications/FloatingClock.appor local build path change → update the script.
Only update if the issue is real and reproducible — not speculative.
Comments
Markdown supported