mcpField
D
daemon-setup

daemon-setup

github.com/terrylicaCloud & DevOps192 installsUpdated today
Repository

About daemon-setup

An interactive skill for installing and verifying the asciinema chunker daemon on macOS. It guides credential setup and launchd installation for users who want the daemon to run independently of Claude Code.

Key features

  1. 01Preflight dependency checks
  2. 02Existing installation handling
  3. 03GitHub PAT setup and verification
  4. 04Optional Pushover configuration
  5. 05launchd setup and health checks

Use cases

  1. 01Installing the chunker daemon for the first time
  2. 02Reinstalling while retaining credentials
  3. 03Resetting credentials for a fresh setup
  4. 04Diagnosing daemon startup or notification issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/terrylica/cc-skills --skill daemon-setup

After installing, type/daemon-setupin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
evolution-log.md
launchd-installation.md
pat-setup-guide.md
pushover-setup-guide.md
verification-and-troubleshooting.md

Details

From the project README

/asciinema-tools:daemon-setup

Interactive wizard to set up the asciinema chunker daemon. This daemon runs independently of Claude Code, using dedicated credentials stored in macOS Keychain.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Why a Daemon?

Problem with old approachDaemon solution
Uses gh auth token (shared)Uses dedicated PAT from Keychain
Dies when terminal closeslaunchd keeps it running
Silent push failuresLogs + Pushover notifications
Tied to Claude Code sessionCompletely decoupled

Setup Phases Overview

PhaseNameDetails
1Preflight CheckBelow
2Check ExistingBelow
3GitHub PAT SetupPAT Setup Guide
4Pushover SetupPushover Setup Guide
5-6Config + Installlaunchd Installation Guide
7Verify + TroubleshootVerification & Troubleshooting

Execution

Phase 1: Preflight Check

Check required tools:

/usr/bin/env bash << 'PREFLIGHT_EOF'
MISSING=()
for tool in asciinema zstd git curl jq; do
  command -v "$tool" &>/dev/null || MISSING+=("$tool")
done

# macOS-specific: security command for Keychain
if [[ "$(uname)" == "Darwin" ]]; then
  command -v security &>/dev/null || MISSING+=("security (macOS Keychain)")
fi

if [[ ${#MISSING[@]} -gt 0 ]]; then
  echo "MISSING:${MISSING[*]}"
  exit 1
fi

echo "PREFLIGHT:OK"
PREFLIGHT_EOF

If MISSING not empty, use AskUserQuestion:

Question: "Missing required tools: {MISSING}. How would you like to proceed?"
Header: "Dependencies"
Options:
  - label: "Install via Homebrew (Recommended)"
    description: "Run: brew install {MISSING}"
  - label: "I'll install manually"
    description: "Pause setup and show install instructions"
  - label: "Abort setup"
    description: "Exit the setup wizard"

If "Install via Homebrew": Run brew install {MISSING} and continue.


Phase 2: Check Existing Installation
/usr/bin/env bash << 'CHECK_EXISTING_EOF'
PLIST_PATH="$HOME/Library/LaunchAgents/com.cc-skills.asciinema-chunker.plist"
DAEMON_RUNNING="false"

if [[ -f "$PLIST_PATH" ]]; then
  echo "PLIST_EXISTS:true"
  if launchctl list 2>/dev/null | grep -q "asciinema-chunker"; then
    DAEMON_RUNNING="true"
  fi
else
  echo "PLIST_EXISTS:false"
fi

echo "DAEMON_RUNNING:$DAEMON_RUNNING"

# Check if PAT already in Keychain
if security find-generic-password -s "asciinema-github-pat" -a "$USER" -w &>/dev/null 2>&1; then
  echo "PAT_EXISTS:true"
else
  echo "PAT_EXISTS:false"
fi
CHECK_EXISTING_EOF

If PLIST_EXISTS=true, use AskUserQuestion:

Question: "Existing daemon installation found. What would you like to do?"
Header: "Existing"
Options:
  - label: "Reinstall (keep credentials)"
    description: "Update daemon script and plist, keep Keychain credentials"
  - label: "Fresh install (reset everything)"
    description: "Remove existing credentials and start fresh"
  - label: "Cancel"
    description: "Exit without changes"

Phase 3: GitHub PAT Setup

See PAT Setup Guide for the full interactive flow: PAT creation walkthrough, Keychain storage, and verification.


Phase 4: Pushover Setup (Optional)

See Pushover Setup Guide for the full interactive flow: Pushover explanation, app creation, credential storage, and test notification.


Phase 5-6: Daemon Configuration and launchd Installation

See launchd Installation Guide for chunking settings selection, plist generation from template, and service installation.


Phase 7: Verification

See Verification & Troubleshooting for daemon health checks, post-install verification, the final success message, and the troubleshooting table.

Quick Reference

Troubleshooting
IssueCauseSolution
Keychain access deniedmacOS permission not grantedGrant access in System Settings
PAT test failedToken expired or invalid scopeGenerate new token with repo scope
launchctl load failedplist syntax errorCheck plutil -lint <plist-path>
Daemon keeps stoppingScript error or crashCheck /asciinema-tools:daemon-logs
Pushover not workingInvalid credentialsRe-run setup with correct app/user key
Health file missingDaemon not runningRun /asciinema-tools:daemon-start
Related Commands
CommandDescription
/asciinema-tools:daemon-statusCheck daemon health
/asciinema-tools:daemon-logsView logs
/asciinema-tools:daemon-stopStop daemon
/asciinema-tools:daemon-startStart daemon

Post-Execution Reflection

After this skill completes, reflect before closing the task:

  1. Locate yourself. — Find this SKILL.md's canonical path (Glob for this skill's name) before editing. All corrections target THIS file and its sibling references/ — never other documentation.
  2. What failed? — Fix the instruction that caused it. If it could recur, add it as an anti-pattern.
  3. What worked better than expected? — Promote it to recommended practice. Document why.
  4. What drifted? — Any script, reference, or external dependency that no longer matches reality gets fixed now.
  5. Log it. — Every change gets an evolution-log entry with trigger, fix, and evidence.

Do NOT defer. The next invocation inherits whatever you leave behind.

Comments

Markdown supported