claude-code-copy-markdown
Claude Code Copy Markdown
Copy Claude Code's response as clean Markdown to the macOS clipboard (pbcopy).
Why this skill exists
Claude Code renders output richly in the terminal — box-drawing tables, indented lists, colored text, etc. This looks great in the terminal, but when you copy-paste it elsewhere, line breaks get mangled and tables fall apart. Asking "write that to a markdown file" every time is tedious. This skill reduces that to a single action.
Workflow
- User says "copy this", "copy as markdown", etc.
- Identify the previous response (or the part the user specified)
- Reformat the content as proper Markdown
- Pipe it to
pbcopy - Confirm completion
Formatting rules
Convert the previous response into clean Markdown following these rules.
Headings
- Section titles that were displayed as bold or prominent text become
##or###headings
Lists
- Use
-for all bullet points - Nest with 2-space indentation
Code blocks
- Wrap inline code with
` - Wrap multi-line code with
```and include the language name when known - File path references (e.g.
path/to/file.ts:10) become inline code
Tables
- Convert box-drawing tables (
┌─┬─┐, etc.) into Markdown pipe tables - Include header row and separator row
| Field | Meaning |
| ------- | ------------------------------------- |
| foundAt | The date the job was first discovered |
Line breaks and whitespace
- One blank line between paragraphs
- Remove excessive consecutive blank lines
- Join lines that were split by terminal word-wrapping into a single paragraph
Emphasis
- Use
**bold**for keywords or field names that were emphasized in the original output
Partial copy
When the user specifies a range (e.g. "just copy the table part", "copy the code section"), extract and copy only that portion. If no range is specified, copy the entire previous response.
Execution
Pipe the formatted Markdown to pbcopy using a heredoc to safely handle quotes and special characters:
pbcopy <<'MARKDOWN_EOF'
(formatted Markdown here)
MARKDOWN_EOF
Completion message
After copying, respond briefly:
Copied to clipboard.
No need for lengthy explanation or repeating the full content — the user already saw the output and just needs confirmation that it's now in the clipboard as Markdown.
More from mrsekut/agent-skills
chrome-store-submit
Automate new Chrome extension submission to Chrome Web Store using playwright-mcp. Reads manifest.json and source code, generates store listing text in any language, creates store images, and fills all required forms via browser automation. Use when submitting a new Chrome extension to Chrome Web Store, publishing a Chrome extension, or filling Chrome Web Store developer dashboard forms.
20cosense-conversation
Cosense(旧Scrapbox)上での会話記法を理解し、Cosense MCPを通じてページに書き込む際にCosense流の書き方で応答する。Cosenseのページに書き込むとき、Cosense上で会話・返答するとき、Cosense MCPを使うときにこのスキルを適用する。
12bun-publish-setup
First-time npm publish for bun libraries and GitHub Actions setup for automated publishing. Validates/fixes package.json, performs initial publish, and configures CI/CD workflow.
11curated-skill-creator
既存のスキルやインターネット上の類似事例をリサーチし、ユーザーの要望と組み合わせて高品質なClaude Codeスキルを作成するスキル。新しいスキルを作りたい、スキルのアイデアがある、こういうワークフローを自動化したい、といった場面で使う。既存のskill-creatorとの違いは、インターネット上の類似スキルやプロンプト、ベストプラクティスをリサーチして取り込むフェーズがあること。スキルを作りたい、ワークフローをスキル化したい、と言われたらこのスキルを使うこと。
2vscode-openvsx-extension-publish
Workflow for publishing VSCode extensions to both VS Code Marketplace and Open VSX. Supports preparing package.json and README, creating accounts and tokens, local testing, initial manual publish, and setting up GitHub Actions for automated subsequent publishes. Use this skill when asked to "publish an extension", "publish to marketplace", "distribute a VSCode extension", "publish to Open VSX", or "set up CI/CD for an extension". Proactively use this when the extension implementation is mostly complete and the user wants to publish.
2sdd
>
1