Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From clippy
Save useful artifacts from the current conversation into the Clippy clipboard manager. Use when the user says "save that", "clip this", "add this to clippy", or asks to keep a command, code snippet, URL, or other text for later reuse.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clippy:clip-captureThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Capture worthwhile artifacts from the conversation (shell commands, code snippets, URLs, config blocks, one-liners) into Clippy so the user can paste them later.
Capture worthwhile artifacts from the conversation (shell commands, code snippets, URLs, config blocks, one-liners) into Clippy so the user can paste them later.
Identify the artifact. Take exactly what the user pointed at. If they said "save that" ambiguously, pick the most recent command/snippet/URL and confirm your choice in one line before saving. Save the raw text, not your commentary around it.
Title it well. Pass a short, specific title to clippy_add that says what the clip does, not where it came from. Good: "ffmpeg trim first 10s", "Postgres connection string (staging)". Bad: "snippet", "from conversation".
Categorize when obvious. Call clippy_list_categories first. If an existing category clearly fits (for example "Commands", "URLs", "Snippets"), file the new clip there with clippy_set_category after adding it. Do not invent new categories for a single clip unless the user asks.
Confirm. Report the returned clip id and title. Remind the user that the running Clippy app shows externally added clips on its next capture or relaunch.
clippy_add calls with three titles, not one blob.npx claudepluginhub w159/clippy --plugin clippyGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.