
Install
- 69 installs
- 62 repo stars
- Updated August 3, 2026
- terrylica/cc-skills
Helps with ai & agent building tasks.
About
install is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- install
- AI & Agent Building
- AI-coding skill
Install by the numbers
- 69 all-time installs (skills.sh)
- Ranked #5,786 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/terrylica/cc-skills --skill installAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 69 |
|---|---|
| repo stars | ★ 62 |
| Last updated | August 3, 2026 |
| Repository | terrylica/cc-skills ↗ |
What it does
Helps with ai & agent building tasks.
Files
/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
fi2. Build, bundle, sign:
cd "$PLUGIN_ROOT" && make all3. Copy to /Applications:
cp -R "$PLUGIN_ROOT/build/FloatingClock.app" /Applications/4. Launch:
open /Applications/FloatingClock.app5. 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.