ams-clipboard-manager
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
03 SKILL.md 正文
Clipboard Manager
Overview
The default clipboard holds one item — a constant source of lost copies and re-copying.
A clipboard manager keeps history: every copy saved, searchable, pinnable, pasteable by selection.
Power features: paste-as-plain-text, transformations (case, whitespace), pinned favorites, and merged pasting.
For researchers, writers, developers, and support staff, it's among the highest-ROI utilities installed.
When to use
- Research involving many sources (copy from many places, paste selectively)
- Writing and editing with repeated phrases, quotes, or references
- Development work with frequent code snippet reuse
- Support/sales work pasting standard responses and links
- Any workflow where you re-copy the same thing multiple times daily
Core concepts
- History depth. Keep 50-200+ items. Deep enough that 'I copied it an hour ago' is recoverable. Searchable history beats big visible lists.
- Search and filter. Type-to-find across history. The recall hotkey + a few characters beats scrolling every time.
- Pinning favorites. Pin the 10-20 evergreen clips: addresses, links, boilerplate. Pinned items survive history rotation.
- Paste as plain text. Strip formatting on paste — essential when moving text between apps with clashing styles. Dedicated hotkey.
- Transformations. Upper/lower/title case, trim whitespace, URL encode/decode, sort lines. Small transforms, constant use.
- Merge and sequence. Paste multiple history items in order, or merge clips into one. Assembling content from fragments.
- Exclusions. Password managers and sensitive fields must be excluded. Verify exclusion works — clipboard history is a security surface.
- Images and files. Modern managers store images and file references too. Screenshots and files join the recallable history.
Practical workflow
- Install and enable. Pick a manager (OS-integrated like Raycast/Alfred history, or standalone). Enable on login — it must always run.
- Set history depth. 100+ items to start. Deep enough to be useful, shallow enough to search fast.
- Learn the recall hotkey. The single most important step. Practice until invoking history is reflex, not a remembered feature.
- Verify exclusions. Copy from your password manager; confirm it doesn't appear in history. Non-negotiable security check.
- Pin your evergreen clips. Copy each favorite once, pin it. Build the pinned set over the first week of real use.
- Learn plain-text paste. Separate hotkey for unformatted paste. You'll use it dozens of times daily once known.
- Explore transforms. Case conversion, whitespace trim, URL encode — map the 2-3 you'll actually use.
- Prune periodically. Clear stale history monthly; review pins quarterly. A junk-filled history slows recall.
Common pitfalls
- Never learning the hotkey. Installed but invoked never. The hotkey is the product — drill it until automatic.
- Shallow history. Default 10-item history that rotates before you need it. Raise the depth on day one.
- No exclusions verified. Assuming sensitive copies are excluded. Verify with a test copy from your password manager.
- History as hoarding. 500 unpinned, unsearchable items. Pin the keepers, search the rest, clear periodically.
- Formatting surprises. Pasting rich text into plain contexts (or vice versa). Plain-text paste hotkey solves 90% of this.
- Manager not launching at login. Works Monday, forgotten Tuesday. Must auto-start; check after every OS update.
- Pasting secrets accidentally. History makes it easy to paste the wrong clip — especially credentials. Double-check before pasting into shared contexts.
- Ignoring images/files. Using history for text only while re-screenshotting daily. Enable image history if your workflow needs it.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).