使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/terrylica/cc-skills --skill daemon-stop開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
/asciinema-tools:daemon-stop
Stop the asciinema chunker daemon via launchd.
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.
Execution
Check if Running
/usr/bin/env bash << 'CHECK_EOF'
PLIST_PATH="$HOME/Library/LaunchAgents/com.cc-skills.asciinema-chunker.plist"
if ! [[ -f "$PLIST_PATH" ]]; then
echo "Daemon not installed."
exit 0
fi
if ! launchctl list 2>/dev/null | grep -q "asciinema-chunker"; then
echo "Daemon not running."
exit 0
fi
echo "RUNNING"
CHECK_EOFStop Daemon
/usr/bin/env bash << 'STOP_EOF'
PLIST_PATH="$HOME/Library/LaunchAgents/com.cc-skills.asciinema-chunker.plist"
if launchctl unload "$PLIST_PATH"; then
echo "Daemon stopped"
# Verify
sleep 1
if launchctl list 2>/dev/null | grep -q "asciinema-chunker"; then
echo "WARNING: Daemon may still be running"
else
echo "Confirmed: Daemon is no longer running"
fi
else
echo "ERROR: Failed to stop daemon"
exit 1
fi
STOP_EOFOutput
On success:
Daemon stopped
Confirmed: Daemon is no longer runningNotes
- Stopping the daemon does NOT delete credentials from Keychain
- To restart:
/asciinema-tools:daemon-start - The daemon will NOT auto-start on next login until started again
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| Failed to stop daemon | Launchd error | Try launchctl unload -F <plist-path> |
| Daemon still running | Multiple instances | Kill manually: pkill -f asciinema-chunker |
| Can't find plist | Setup not run | Run /asciinema-tools:daemon-setup first |
| Recordings not stopping | asciinema rec is running | Exit recording shell first (Ctrl-D or type exit) |
Post-Execution Reflection
After this skill completes, check before closing:
- Did the command succeed? — If not, fix the instruction or error table that caused the failure.
- Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
- Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.
Only update if the issue is real and reproducible — not speculative.

