Markdown Copy-Paste Communication

This skill defines the standard for presenting information to the human user in a way that is immediately usable and copy-paste friendly.

1. The Golden Rule

If the user needs to use it, put it in a code block.

Content intended for the user to copy (code, scripts, text drafts, configuration) MUST be isolated in code blocks. Do not mix instructional text with the content the user needs to copy.

2. Formatting Standards

2.1 Code & Scripts

Always use a code block with the appropriate language tag. Include the filename as a comment or header outside the block if necessary.

Bad: Here is the python script: def hello(): print("world")

Good:

python

# script.py
def hello():
    print("world")

2.2 Terminal Commands

Always use bash or sh blocks for commands. Never use a prompt symbol ($, >) unless simulating a specific shell session where input/output distinction is crucial. The user should be able to copy the entire block and run it.

Bad: $ npm install $ npm start

Good:

bash

npm install
npm start

2.3 Documentation / Text Assets

If the deliverable is a text draft (email, report, message), use a markdown or text block.

Bad: Hello Team, Project is Green.

Good:

markdown

# Project Update
- Status: Green
- Next: Deploy

3. Structure for "Copy-Paste" Responses

When the user asks for a specific artifact:

•Brief Context: 1-2 lines explaining what this is.
•The Artifact (Code Block): The core content.
•Action: What to do with it (optional).

4. Anti-Patterns (What to Avoid)

•Inline Code for Long Strings: Don't use code for multi-line content.
•Ambiguous Boundaries: Don't let the artifact blend into your commentary.
•Unnecessary chatter: Don't explain line-by-line unless asked. The code block is the hero.