clipboard-daemon
Set up and manage the clipboard-history background daemon. Use when configuring automatic clipboard capture, troubleshooting the daemon, or setting up auto-start on login. Triggers include "clipboard daemon", "auto-capture clipboard", "clp daemon", "start clipboard watcher", "daemon not running".
Best use case
clipboard-daemon is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Set up and manage the clipboard-history background daemon. Use when configuring automatic clipboard capture, troubleshooting the daemon, or setting up auto-start on login. Triggers include "clipboard daemon", "auto-capture clipboard", "clp daemon", "start clipboard watcher", "daemon not running".
Teams using clipboard-daemon should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clipboard-daemon/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clipboard-daemon Compares
| Feature / Agent | clipboard-daemon | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Set up and manage the clipboard-history background daemon. Use when configuring automatic clipboard capture, troubleshooting the daemon, or setting up auto-start on login. Triggers include "clipboard daemon", "auto-capture clipboard", "clp daemon", "start clipboard watcher", "daemon not running".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# clipboard-daemon Guide to running and managing the clipboard-history daemon. ## How the Daemon Works The daemon polls the system clipboard every 500ms. When the content changes, it computes a SHA-256 hash and saves the new content to the database if the hash differs from the last saved entry. Identical consecutive copies are stored only once. ## Starting and Stopping ```bash clp daemon start # start in background clp daemon stop # send SIGTERM, wait for exit clp daemon status # check running state and uptime ``` ## Auto-Start on Login ### macOS / zsh Add to `~/.zshrc` or `~/.zprofile`: ```bash clp daemon status > /dev/null 2>&1 || clp daemon start ``` ### Linux / bash Add to `~/.bashrc` or `~/.profile`: ```bash clp daemon status > /dev/null 2>&1 || clp daemon start ``` ## PID File The daemon writes its PID to: ``` ~/.local/share/clipboard-history/daemon.pid ``` The `daemon stop` command reads this file and sends SIGTERM. If the process is not running but the PID file exists, `daemon start` will overwrite it. ## Daemon Status Output When running: ``` * daemon running (pid 12345) -- uptime: 3h 24m -- entries recorded: 142 -- polling every 500ms ``` When not running: ``` -- daemon not running -- start with: clp daemon start ``` ## Troubleshooting **Daemon stops unexpectedly** - Check system memory. The daemon uses minimal memory but may be killed by the OS. Add auto-start to your shell profile. **Entries not being captured** - Verify with `clp daemon status`. If not running, restart with `clp daemon start`. **High CPU usage** - Unlikely at 500ms polling, but increase the interval: `CLP_POLL_MS=2000 clp daemon start`. **Stale PID file** - If `daemon start` reports already running but the process is not alive, the PID file may be stale. Remove it: `rm ~/.local/share/clipboard-history/daemon.pid`, then start again. ## Configuration ```bash # Change polling interval (milliseconds) CLP_POLL_MS=1000 clp daemon start # Use custom database path CLP_DB_PATH=/path/to/db.sqlite clp daemon start # Enable debug logging (logs to stderr) CLP_DEBUG=1 clp daemon start ```
Related Skills
clipboard-history
Access persistent clipboard history from the terminal. Use when retrieving previously copied text, searching clipboard history, or restoring old clipboard content. Triggers include "clipboard history", "what did I copy", "clp", "paste old content", "clipboard search", "recover copied text".
Skill: Uptime Monitoring
## Overview
Skill: Status Page
## Overview
Skill: unit-conversion
## Overview
Skill: recipe-scaler
## Overview
reading-list
Operate the reading-list API to save, manage, tag, search, and export articles.
email-digest
Configure, test, and troubleshoot the reading-list daily email digest delivered via nodemailer.
websocket-realtime
Use the WebSocket connection in poll-builder to receive live vote updates. Use when you need to stream real-time poll results, monitor a poll for new votes, or build a live dashboard. Triggers include "live results", "real-time updates", "stream votes", "watch poll", or "WebSocket".
poll-builder
Self-hosted poll creation tool with real-time results. Use when you need to create a poll, check vote counts, close a poll, export results, or get the shareable link for a poll. Triggers include "create poll", "vote", "poll results", "survey", "collect votes", "share poll", or any task involving polling or voting.
Skill: personal-finance
## Overview
Skill: csv-import
## Overview
Skill: Syntax Highlighting
## Purpose