Skip to main content
AI/MLterrylica

install

Build FloatingClock from source and install to /Applications, then launch. Use when user wants to install the floating-clock plugin's macOS app.

Stars
49
Source
terrylica/cc-skills
Updated
2026-05-30
Slug
terrylica--cc-skills--install
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/terrylica/cc-skills/HEAD/plugins/floating-clock/skills/install/SKILL.md -o .claude/skills/install.md

Drops the SKILL.md into .claude/skills/install.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

/floating-clock:install

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.

Steps

  1. 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
    
  2. Build, bundle, sign:

    cd "$PLUGIN_ROOT" && make all
    
  3. Copy to /Applications:

    cp -R "$PLUGIN_ROOT/build/FloatingClock.app" /Applications/
    
  4. Launch:

    open /Applications/FloatingClock.app
    
  5. Confirm:

    Installed to /Applications/FloatingClock.app and launched. The app is now discoverable via Spotlight (⌘Space → FloatingClock) and Launchpad. Right-click the clock for options.

Post-Execution Reflection

After this skill completes, check before closing:

  1. Did make all produce the expected build/FloatingClock.app? — If not, fix the Makefile or the build prerequisite.
  2. Did the copy/launch step succeed silently? — If macOS prompted (gatekeeper, permission), document the bypass.
  3. Did paths drift? — Plugin root, Makefile target, or app bundle name change → update the script.

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