Skip to content
Back to skills

Launch

ASecurity

Launch FloatingClock, preferring the installed /Applications copy and falling back to the local build. Use when the user wants to open the floating-clock app.

  • 75 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
toolsbash

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add terrylica/cc-skills --skill launch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Launch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Launch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/terrylica-launch/badge)](https://www.skillsdirectory.com/skills/terrylica-launch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: launch
description: "Launch FloatingClock, preferring the installed /Applications copy and falling back to the local build. Use when the user wants to open the floating-clock app."
allowed-tools: Bash
---

# /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:

```bash
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:

1. **Did `open` succeed silently?** — If macOS surfaced a gatekeeper prompt, document the bypass.
2. **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.
3. **Did paths drift?** — `/Applications/FloatingClock.app` or local build path change → update the script.

Only update if the issue is real and reproducible — not speculative.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…