Damecek

Copy a finished LinkedIn post draft to the macOS clipboard with formatting preserved (HTML via pandoc + pbcopy-html.swift). Use AFTER draft-post N when the user wants to paste the post into the LinkedIn editor with bold/italic intact. Requires pandoc.

Copy a finished LinkedIn post draft to the macOS clipboard as plain UTF-8 text (via pbcopy-text.swift). Use AFTER draft-post N when the user wants the raw markdown on the clipboard with Mathematical Bold/Italic Unicode (U+1D400–U+1D7FF) intact. Use this instead of macOS pbcopy, which mangles 4-byte UTF-8 sequences.

Outline a long-form technical article (1500–2500 words) about the current repository, with each section mapped to verified claims and repo file references. Use this AFTER proof-pack when the user wants a long-form article or blog post (NOT a short LinkedIn post — for that use series-plan). Requires content/claims.md from proof-pack.

Write the publish-ready long-form article (1500–2500 words) from the article plan, with inline code snippets and direct repo links. Use this AFTER article-plan when the user wants the final article text — this skill produces the actual prose, not the outline.

Draft the actual copy for a specific LinkedIn post (1 of 5 in the series) — produces 3 style variants (technical, business, founder), 5 opening hooks, and hashtags. Use this AFTER series-plan when the user wants to write the real text of post N. Requires the series plan from series-plan.

Generate a Gemini image prompt (1200x627 LinkedIn infographic) plus alt text from a finished post draft. Use this AFTER draft-post N when the user wants the visual asset for a specific post — picks one of 6 visual concepts based on the post content.

Entry point for any LinkedIn content (post, article, or series) about the current repository. Use this FIRST whenever the user wants to write, draft, plan, or promote anything on LinkedIn about this project — it extracts the verifiable factual claims that every other drafting skill depends on. Triggers on intents like "write a LinkedIn post about this repo", "draft an article about this project", "promote this on LinkedIn".

Transform a finished LinkedIn post into 4 derivative formats (short post, carousel script, comment version, DM explanation) for multi-channel distribution. Use this AFTER draft-post N when the user wants to spread the same message across other channels or formats.

Release new npm + SF 2GP package versions for salesforce-mcp-lib. TRIGGER when: user says "release", "publish", "new version", "bump version", "npm publish", "package version create", or asks to tag and push a release. DO NOT TRIGGER when: writing code (use sf-apex/sf-lwc), deploying metadata to an org (use sf-deploy), or running tests only (use sf-testing).

Use when working on this repository (Zed Salesforce DX extension) and you need up-to-date or authoritative information about Zed extension APIs/docs, language server integration, the Language Server Protocol, Salesforce language tooling behavior (Apex today; LWC/Aura/Visualforce scope planning), or the Salesforce VS Code reference implementations. This skill provides a repeatable research workflow using Context7 and a small set of authoritative web sources, plus local repo reference paths.

Use Context7 to verify and retrieve up-to-date information from the `damecek/salesforce-documentation-context` documentation via the fixed `libraryId:/damecek/salesforce-documentation-context`. Use in any Salesforce project when you need to confirm uncertain details, fetch newer information than the model may know, or get accurate examples/usage guidance from that documentation set; always call `mcp__context7__query-docs` directly and skip `mcp__context7__resolve-library-id`.