mkl-write-launch-post
/mkl-write-launch-post
Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback.
- Author
- 00200200 ↗
- Repository
- maintainer-skills-lab ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback.
Original author description
Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback.
How it works
- Worked example
SKILL.md preview
--- name: "mkl-write-launch-post" description: "Draft factual project announcements, GitHub launch posts, and development updates for a specified audience or platform. Use to explain shipped work clearly, with evidence and a useful invitation for feedback." --- # Draft a project announcement Establish the audience, platform, and state of the work: available release, merged improvement, open PR, or plan. Inspect the supplied revision, demo, and project links before claiming availability. When the medium is unspecified, write a short platform-neutral draft that the user can adapt. Start with a concrete problem and what the project now lets someone do. Use a small example or observed result when available. Include the minimum context needed to understand a limitation, setup requirement, or preview status. Keep an open PR or planned capability explicitly separate from shipped behavior. Use the author's supplied tone or samples without inventing personal stories. Numbers about adoption, performance, time saved, stars, or customers need evidence. An aspirational sentence must remain an aspiration. Do not fabricate testimonials, claim affiliations, or frame a static format check as a successful live-agent test. For a stated length limit, measure the draft with the platform's actual counting rules when available; otherwise state the counting assumption. Preserve the destination URL. Prefer one relevant invitation, such as trying the example or reporting a specific integration issue, over several competing calls to action. Return a ready-to-review draft. List unresolved factual questions separately, without placeholders disguised as completed claims. Publishing or sending it is a separate action: use existing authorization if present; otherwise leave the draft for review. Output constraints: strictly under 350 words (~450 tokens). Focus on technical problem, solution, and a single call-to-action. Omit marketing hyperbole, artificial hype, or conversational intro/outro. Conclude immediately. ## Worked example Evidence: a merged change adds `--dry-run`; Linux was tested; Windows was not. No time-saving measurements exist. One suitable draft: "The installer now has a preview mode. Run with `--dry-run` to inspect planned changes before writing files. We tested it on Linux; Windows still needs a check. If you try it on Windows, an issue with the steps and output would help." Acceptance: availability matches the merged change, limits remain visible, and no adoption or productivity claim is invented. This is an authored example, not a recorded client evaluation.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · 00200200/maintainer-skills-lab | 95 | MIT |
| 00200200/maintainer-skills-lab | 100 | MIT |
| 00200200/maintainer-skills-lab | 100 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 367dc81c221c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mkl-match-voice
Adapt a draft to a user's writing samples or explicit tone brief. Use for consistent personal or project voice across docs and posts; distinguish style evidence from factual content. - 100mkl-match-voice
Adapt a draft to a user's writing samples or explicit tone brief. Use for consistent personal or project voice across docs and posts; distinguish style evidence from factual content. - 100okhp3-linkedin-post
Draft a source-backed LinkedIn post from a chosen angle or named topic. Use for standalone posts, public progress updates, launch or checkpoint recaps, deadline updates, or "write a post about X". It applies voice and the final public-context scrub, then returns a draft only. - 100tweet
Find tweet ideas, plan launch posts, and draft or polish tweets with code cards, stat cards, or screenshot wraps. Use for content strategy, what to post, when to post, or an X post. - 100recoup-internal-social-ship-posts
INTERNAL — Recoup staff tooling, gated by the recoup-internal keyword. Invoke ONLY when the request explicitly includes "recoup-internal" (e.g. "recoup-internal draft a launch post"). Never use for customer-facing or artist requests. Write and ship data-grounded LinkedIn and X… - 100social-x
Write and revise X (Twitter) posts, replies, threads and launch proof in the author's voice. Use when drafting for X, from announcements to reply plans.