coreyhaines31/makerskills / skills/paste
paste
VerifiedWhen you want to clean and reformat content (usually from your terminal) for pasting into Slack, Notion, Twitter/X, LinkedIn, email, GitHub, or plain text. Strips ANSI codes, box-drawing chars, terminal prompt artifacts, and applies destination-specific formatting. Default input is the system clipboard; default output is both the clipboard and a chat preview. Triggers on "/paste", "/paste [destination]", "clean this for X," "format for slack/notion/twitter/linkedin/email/github," "render as markdown," "paste-ready," "strip formatting," "make this copy-pastable." Default destination is plain. Also scans for secrets (API keys, tokens, .env values) and warns before copying anything sensitive.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.0 KB |
| references/destinations.md | markdown | 4.9 KB |
| references/secret-patterns.md | markdown | 3.0 KB |
references/destinations.md
View on GitHub# Destination rules
After universal cleaning (Step 4 in SKILL.md), apply the transform below per destination.
---
## plain
Strip all markdown syntax. Result: text + line breaks only.
- `**bold**`, `*italic*`, `_italic_`, `~~strike~~` → remove the marks, keep the text
- `# Heading`, `## Heading` → keep text, drop the `#`
- `> blockquote` → drop the `>`
- `[link text](url)` → `link text (url)` or just `link text` if URL is noise
- Inline `` `code` `` → drop the backticks
- Triple-backtick code blocks → keep content as plain text (drop the fences and language hint)
- Tables → convert to bulleted lists (one row per bullet, columns separated by `: ` or `, `)
- Bullets and numbered lists → keep, normalize to `- ` and `1. ` style
---
## slack
Slack uses its own markdown subset.
- `**bold**` → `*bold*`
- `*italic*` → `_italic_`
- `~~strike~~` → `~strike~`
- `# H1` / `## H2` / `### H3` → bold text on its own line (Slack has no headers): `*Heading*`
- `[link text](https://url)` → `<https://url|link text>` (Slack auto-link format)
- Inline `` `code` `` → keep (Slack renders inline code)
- Triple-backtick code blocks → keep
- Bullet lists → keep with `• ` or `- `
- Numbered lists → keep
- Tables → convert to bulleted list. Slack tables look terrible. Example:
```
| Name | Role |
| Alice | PM |
| Bob | Eng |
```
→
```
• Alice — PM
• Bob — Eng
```
---
## notion
Notion's paste handler parses markdown natively. Keep everything.
- Keep all markdown syntax (`**bold**`, `*italic*`, `_underline_`, `~~strike~~`)
- Keep headers (`#`, `##`, `###`)
- Keep tables (Notion renders them as databases on paste)
- Keep code blocks with language hint (Notion preserves syntax highlighting)
- Keep links inline `[text](url)` — Notion handles them
- Keep blockquotes (`>`)
- Result: clean, idiomatic markdown
---
## twitter (X)
Strip all formatting. X is plain text.
- Strip all markdown (`**`, `*`, `_`, `~`, `#`, `>`, backticks)
- Strip headers entirely (no flat headers in tweets — they look weird)
- Strip code fences; keep the code contents (or note: "this is code, doesn't fit a tweet, want me to paste-bin it?")
- Tables → flatten to a short list
- URLs:
- Surface them separately
- Per the user's voice rule: links don't go in the body — surface for use as a reply
- Char count: warn at >280
---
## linkedin
Strip formatting. LinkedIn is plain text.
- Strip all markdown
- Keep line breaks (LinkedIn rewards whitespace and scannability)
- Strip headers — use a bold-feeling first line instead (no actual bold available)
- URLs:
- Surface separately, don't include in body
- Per the user's voice rule: links go in a first comment, not body
- No hashtags (the user's voice rule)
- Char count: note at >400 (comfort line, not hard limit)
---
## email (plain)
Plain text email. Most safe across clients.
- Strip markdown syntax (keep the text)
- Convert links to `text (url)` format — most email clients won't auto-link inline markdown
- Keep tables as ASCII (most clients render OK in monospace; otherwise convert to bullets)
- Keep line breaks
---
## email (rich / html)
Render to HTML so the user can copy from a browser into Gmail/Apple Mail with formatting preserved.
- Convert markdown → HTML (use a simple converter: `pandoc` if installed, else hand-render)
- Style with minimal inline CSS for readability (system font stack, 16px base, 1.5 line height, max-width 640px)
- Write to `/tmp/paste-<timestamp>.html`
- `open /tmp/paste-<timestamp>.html` to launch in default browser
- Skip clipboard — the user selects + copies from the browser
---
## github
Markdown is native. Keep almost everything.
- Keep all markdown
- Keep code blocks with language hint (`)
- Keep tables (GitHub renders them)
- Strip ANSI from terminal output but **wrap the cleaned output in a fenced code block** with language hint (`bash`, `shell`, or `text` as appropriate)
- Keep links inline
- Keep `> blockquotes` (GitHub renders)
- @-mentions: leave as-is (user can decide whether to break them)
---
## markdown (render in chat)
Render the cleaned markdown directly in chat — Claude Code renders it inline for the user to read.
- Apply universal cleaning
- Keep markdown structure intact
- Copy raw markdown to clipboard too (in case the user wants to paste somewhere else)
- After rendering, offer: *"Want me to also open this as HTML in your browser?"* — if yes, write to `/tmp/paste-<ts>.html` and `open`
---
## html (render to file + open browser)
For when you want to copy rich-formatted content from a browser into a rich-text destination (Notion via browser, email composer, Google Docs).
- Convert markdown → HTML
- Minimal inline CSS for clean reading
- Write to `/tmp/paste-<timestamp>.html`
- `open <path>` to launch in default browser
- Skip clipboard
- Tell the user: *"Open in [Chrome/Safari]. Cmd-A, Cmd-C to grab the formatted version."*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |