`). 2. `### ` inside a section → a labelled block within that section. 3. A fenced code block (triple-backtick) directly after a `### Label` → the paste content for that block. 4. An optional paragraph between `### Label` and the fenced code block → a `field-meta` note under the label (e.g. "Max 220 chars."). 5. A top-level `## Copy-paste blocks` section (by convention in the vault) marks the canonical source; if present, prefer blocks inside it. If the source has code blocks without `### Label` headers, fall back to auto-labels (`Block 1`, `Block 2`, ...) but prefer asking the user to add labels. ### Example source fragment ```markdown ## Copy-paste blocks ### Headline Max 220 chars. \`\`\` Shipping AI-native software · 10y Angular · Agentic engineering @ Yellowtail · Ex-Fidelity · Amsterdam 🌶 \`\`\` ### About ~120 words. \`\`\` I ship AI-native software... Tech Builder at Yellowtail... \`\`\` ``` ## Step 3: Auto-derive the Rich (HTML) variant For every block: - Single-line (no `\n`): Plain and Rich are identical. Emit only a Plain button. - Multi-line, no bullets: - Plain: preserve `\n` (use ` ` in `data-plain`). - Rich: wrap each blank-line-separated paragraph in `
...
`. - Multi-line with bullets (lines starting with `- ` or `* `): - Plain: preserve as-is. - Rich: emit non-bullet paragraphs as `
...
`, group consecutive `- ` lines into `
...
`. - Ordered lists (lines starting with `1. `, `2. `, ...): same as bullets but use `
`. The Rich clipboard write uses the multi-format API so targets choose: ```javascript await navigator.clipboard.write([ new ClipboardItem({ "text/plain": new Blob([plain], { type: "text/plain" }), "text/html": new Blob([html], { type: "text/html" }) }) ]); ``` Targets that don't grok HTML fall back to `text/plain`. LinkedIn About strips HTML, so users paste via the Plain button. Docs / Gmail / Notion / blog editors honour HTML, so users paste via Rich. ## Step 4: Apply /ro:write-copy scan Before writing the HTML, scan every block's content for banned patterns: ``` — (em-dash U+2014), – (en-dash U+2013) delve, leverage, robust, seamless, tapestry, landscape, empower, unlock, streamline (as filler) "not only X but also Y", "it's not just X, it's Y", "more than just a tool", "at the intersection of" ``` If any hit, flag to the user via a banner at the top of the HTML (`
...
`) naming the offending block. Do not silently rewrite: the content may have been deliberate (e.g. a quote). ## Step 5: Render the HTML Use this exact template. The navy + teal palette matches the user's LinkedIn cover / CV stack for brand coherence. Keep inline so the file is portable. ```html {{TITLE}}

{{SUBTITLE}}

{{TITLE}}

{{INTRO}}

copies text only (LinkedIn, forms). copies with HTML formatting (Docs, Gmail, Notion).

{{SECTIONS}}

{{FOOTER}}

``` ### Section and block markup Inside `{{SECTIONS}}`, emit one `
` per top-level grouping. Inside each, emit one `.block` per paste block. Single-line block (no HTML variant): ```html

{{SECTION_NAME}}

{{BLOCK_LABEL}}
{{OPTIONAL_META}}

{{DISPLAY_PLAIN}}

``` Multi-line block (with HTML variant): ```html
{{BLOCK_LABEL}}
{{OPTIONAL_META}}

{{DISPLAY_PLAIN}}

``` ### Escaping rules - For `data-plain` and `data-html` attributes: HTML-escape `"`, `&`, `<`, `>`, and replace `\n` with ` `. - For display content inside `
...
`: HTML-escape `"`, `&`, `<`, `>` only. Preserve `\n` as real newlines (the `white-space: pre-wrap` CSS renders them). - Never insert raw user content into attribute values without escaping. ## Step 6: Save and optionally open ```bash TS=$(date +%H%M) DATE=$(date +%Y-%m-%d) SLUG=$(basename "$SOURCE" .md) OUT="vaults/$VAULT/artifacts/paste-kits/$SLUG-$DATE-$TS.html" mkdir -p "$(dirname "$OUT")" # write file ``` If `--open` was passed, also run `open "$OUT"`. ## Step 7: Report Print: - Output path. - Block count per section. - Any `/ro:write-copy` hits flagged in Step 4. - Next steps ("Paste from the Plain button for LinkedIn fields; Rich for Docs / Gmail."). No auto-commit. Leave commits to the user. ## Rules - One source, one output file. Never overwrite a prior kit; timestamp the filename. - Self-contained HTML. Inline CSS + JS, no external assets. File should work from `file://` and email attachments. - Plain is the default button. For LinkedIn-first workflows, the first-press button is plain. - Rich is opt-in per block. Single-line blocks don't need it; complex blocks (paragraphs, bullets) do. - Apply /ro:write-copy rules on every block. Em-dashes especially — they leak through PDF extractions easily. - Escape every attribute. User content from vault markdown can contain `<`, `>`, `&`, `"`. - Palette: navy (`#0f172a`), teal (`#14b8a6`), cream (`#f8fafc`). Matches the LinkedIn cover + CV stack so kits feel part of the same brand. ## Changelog - v0.1.0 (2026-04-24): initial skill. Dual-format copy (text/plain + text/html) via the multi-format Clipboard API. Palette matches the LinkedIn cover / CV brand stack.