planning-launch-distribution
Skill1 starsChanged 3 months agoMITView on GitHub
Use when a completed product, portfolio project, or open source release needs a credible launch plan and tailored posts for channels such as LinkedIn, GitHub, developer communities, and its own website.
In this repository65 other files it gives its agents.
- analyzing-change-blast-radiusSkill
- analyzing-developer-career-opportunitiesSkill
- art-directing-web-interfacesSkill
- assessing-developer-proficiencySkill
- auditing-dependency-riskSkill
- auditing-pixel-perfect-frontendSkill
- bootstrapping-modern-web-appsSkill
- brag-slimSkill
- building-brand-guidelinesSkill
- building-conversion-product-pagesSkill
- building-developer-career-roadmapsSkill
- building-hybrid-game-assetsSkill
- building-premium-nextjs-interfacesSkill
- building-project-showcasesSkill
- building-regression-testsSkill
- building-reliable-node-api-boundariesSkill
- choosing-application-architectureSkill
- craft-premium-motionSkill
- creating-character-sprite-pipelinesSkill
- defining-brand-strategySkill
- designing-action-combatSkill
- designing-developer-portfolio-evidenceSkill
- designing-relational-data-modelsSkill
- designing-software-boundariesSkill
- designing-test-strategiesSkill
- designing-ui-systemsSkill
- designing-visual-identitiesSkill
- documenting-architecture-decisionsSkill
- editing-for-clarity-and-toneSkill
- engineering-gsap-animationsSkill
- evaluating-developer-proficiencySkill
- evolving-postgres-schemas-safelySkill
- humanizing-generated-proseSkill
- implementing-reference-faithful-uiSkill
- investigating-codebase-semanticallySkill
- managing-implementation-slicesSkill
- mapping-existing-codebase-structureSkill
- naming-brands-and-productsSkill
- optimizing-frontend-motion-performanceSkill
- orchestrating-cinematic-web-motionSkill
- planning-codebase-changes-with-evidenceSkill
- planning-engineering-workSkill
- planning-safe-refactorsSkill
- planning-written-communicationSkill
- preparing-project-launchSkill
- profiling-postgres-query-performanceSkill
- reconstructing-images-as-threejsSkill
- reviewing-api-securitySkill
- reviewing-apple-platform-interfacesSkill
- reviewing-pull-requestsSkill
- reviewing-web-securitySkill
- selecting-working-methodsSkill
- shipping-github-vercel-changesSkill
- teaching-developer-conceptsSkill
- testing-integration-boundariesSkill
- testing-playable-gamesSkill
- testing-web-applications-end-to-endSkill
- threat-modeling-applicationsSkill
- tracing-code-execution-pathsSkill
- translating-figma-to-nextjsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use a verified product story to help the right people find, understand, and try the release.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Planning Launch Distribution
Use a verified product story to help the right people find, understand, and try the release. Do not publish, post, send messages, or schedule external content without user authorization.
Workflow
- Identify audience, launch objective, available proof, release readiness, primary link and CTA. If a launch brief or showcase exists, reuse its verified facts; otherwise inspect the project before claiming functionality.
- Select only channels where the intended audience actually participates. Distinguish GitHub release/readme updates, a portfolio or product page, LinkedIn, and a relevant community. Check current posting requirements and moderation rules on the selected platforms before recommending timing or format.
- Build a small asset matrix: channel, audience angle, opening line, proof (short video, screenshot, demo or repository), CTA, destination, owner, and publication order. Adapt each post to its context; don't paste the same copy into every channel.
- Draft launch copy that leads with a concrete problem or result, demonstrates an actual product moment, states availability and limitations honestly, and makes the next action explicit. Credit collaborators and original projects where relevant. Avoid invented popularity, fake scarcity, or blanket claims of being production-ready.
- Plan a short follow-up: answer installation questions, gather reproducible reports, and observe available signals such as qualified clicks, installs, stars, demo completions, or contributor interest. Never infer installs or business impact from impressions alone.
- Deliver ready-to-review drafts, link and asset checklist, release sequence, reply plan, and lightweight feedback log. Mark links and platform limits requiring final verification. Publish only when authorized.
Boundaries
brag-slim produces the video and its initial share caption; this skill adapts the verified story to a channel and launch sequence. writing-conversion-copy owns detailed landing-page copy; shipping-github-vercel-changes owns repository merge and deployment.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.