mkl-write-launch-post

Draft factual project announcements and launch posts with evidence-based claims.

11|1|Updated Sep 13, 2026
One-click install
npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-launch-post-00200200
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mkl-write-launch-post
Source: https://github.com/00200200/maintainer-skills-lab/tree/main/providers/cursor/.cursor/skills/mkl-write-launch-post
Command: npx skills add https://github.com/00200200/maintainer-skills-lab --skill mkl-write-launch-post-00200200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing launch posts and project announcements often leads to overclaiming, invented metrics, or vague marketing language that erodes reader trust. This Skill produces factual drafts that clearly separate shipped work from plans and keep every claim grounded in evidence. ## Core Features & Use Cases - Audience and platform targeting: Establishes the audience, platform, and state of the work (release, merged change, open PR, or plan) before drafting. - Evidence-based claims: Requires verification of revisions, demos, and project links before stating availability, and rejects fabricated testimonials, adoption numbers, or performance claims. - Length and CTA discipline: Measures drafts against platform character limits and prefers one relevant invitation over competing calls to action. - Use Case: After merging a --dry-run feature tested only on Linux, generate a launch post that announces the preview mode, notes the untested Windows support, and invites users to report issues. ## Quick Start Draft a launch post for my project's new dry-run feature, noting it is tested on Linux but not Windows.

Frequently Asked Questions about mkl-write-launch-post

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a factual GitHub launch post for a new feature?▼

Start with the concrete problem and what the project now lets users do, citing the merged change as evidence. State tested platforms and known limitations explicitly, and end with one relevant invitation such as reporting integration issues.

How to announce an open PR or planned feature without overclaiming?▼

Keep open PRs and planned capabilities explicitly separate from shipped behavior in the draft. Frame aspirations as aspirations and never present unmerged work as available functionality.

Can I include adoption or performance numbers in a launch post?▼

Only include numbers about adoption, performance, time saved, stars, or customers when you have evidence for them. The drafting process rejects invented metrics and fabricated testimonials.

Does the skill handle platform character limits like Twitter or LinkedIn?▼

Yes, for a stated length limit it measures the draft using the platform's actual counting rules when available. When rules are unavailable, it states the counting assumption used.

What are the limitations of AI-drafted launch announcements?▼

The draft cannot verify claims beyond the evidence you supply, so unresolved factual questions are listed separately for your review. Publishing remains a separate action requiring your authorization.