agentleFS
CodeAlive-AICodeAlive-AI/ai-driven-development/skills/clipboard/SKILL.md

clipboard

Skill169 starsChanged 56 days agoMITView on GitHub

Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use a heredoc to safely handle special characters (quotes, apostrophes, backticks, dollar signs):

    line 12
  2. Distinctive:

    Use when the user wants formatting preserved for pasting into Slack, Word, Google Docs, Notion, etc.

    line 22
  3. Distinctive:

    Step 1: Write the HTML content to a temp file:

    line 24
  4. Distinctive:

    Step 2: Write the plain text fallback to a temp file:

    line 36
  5. Distinctive:

    Plain: Default for code snippets, terminal output, simple text, or when user says "copy to clipboard" without formatting context

    line 75
  6. Distinctive:

    If ambiguous, ask what to copy

    line 80
  7. Very specific:

    Use single-quoted heredoc delimiters ('CLIPBOARD', 'CLIPBOARD_HTML', 'CLIPBOARD_TEXT') to prevent shell expansion

    line 81
  8. Distinctive:

    Always provide a plain text fallback alongside HTML

    line 83

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Clipboard

Copy the most recent relevant text block from the conversation to the macOS system clipboard.

Plain Text Copy (Default)

Use a heredoc to safely handle special characters (quotes, apostrophes, backticks, dollar signs):

cat <<'CLIPBOARD' | pbcopy
<text to copy>
CLIPBOARD

Rich Text Copy (Formatted)

Use when the user wants formatting preserved for pasting into Slack, Word, Google Docs, Notion, etc. Sets both HTML and plain text on the clipboard via Swift, so the receiving app picks the richest format it supports.

Step 1: Write the HTML content to a temp file:

cat <<'CLIPBOARD_HTML' > /tmp/_clipboard_rich.html
<html><body>
<h2>Title</h2>
<p>Paragraph with <b>bold</b> and <i>italic</i>.</p>
<ul><li>Item one</li><li>Item two</li></ul>
</body></html>
CLIPBOARD_HTML

Step 2: Write the plain text fallback to a temp file:

cat <<'CLIPBOARD_TEXT' > /tmp/_clipboard_rich.txt
Title

Paragraph with bold and italic.

- Item one
- Item two
CLIPBOARD_TEXT

Step 3: Set clipboard with both HTML and plain text using Swift:

swift -e '
import AppKit

let html = try Data(contentsOf: URL(fileURLWithPath: "/tmp/_clipboard_rich.html"))
let text = try String(contentsOfFile: "/tmp/_clipboard_rich.txt", encoding: .utf8)

let pb = NSPasteboard.general
pb.clearContents()
pb.setData(html, forType: .html)
pb.setString(text, forType: .string)
'

Step 4: Clean up temp files:

rm -f /tmp/_clipboard_rich.html /tmp/_clipboard_rich.txt

When to Use Rich vs Plain

  • Rich (HTML): User says "copy formatted", "copy as rich text", "copy for Slack/LinkedIn/Word/Docs/Notion", or the content has meaningful formatting (bold, headers, lists, code blocks). This is also the correct way to copy for Slack and LinkedIn — they accept HTML rich text from clipboard and render it with proper formatting (bold, lists, code, etc.). Do NOT use Slack mrkdwn or markdown syntax for clipboard copy — use HTML rich text instead, it works universally.
    • ⚠️ Slack does NOT render HTML <table> tags. Tables pasted into Slack appear as a broken mess of text. Instead of <table>, present tabular data as plain-text lines (e.g. Label: value per line, or use <pre> for aligned columns). This also applies to LinkedIn and most chat apps.
  • Plain: Default for code snippets, terminal output, simple text, or when user says "copy to clipboard" without formatting context

Rules

  1. Identify the most recent text block the user wants copied (message, code block, drafted text, etc.)
  2. If ambiguous, ask what to copy
  3. Use single-quoted heredoc delimiters ('CLIPBOARD', 'CLIPBOARD_HTML', 'CLIPBOARD_TEXT') to prevent shell expansion
  4. For rich copy, convert markdown-style content to proper HTML (use <b>, <i>, <code>, <ul>/<li>, <h1>-<h6>, <pre>, etc.). Do NOT use <table> for Slack/chat targets — use line-per-row text instead.
  5. Always provide a plain text fallback alongside HTML
  6. Confirm success after copying, noting whether plain or rich format was used

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.