Install
$ agentstack add skill-hardiktiwari-pm-operating-os-launch-post ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Launch Post
Help PMs write Slack-native launch announcements. Produces concise, celebratory posts that inform the team what shipped, who it's for, and why it matters.
When to Use
- Shipping a new feature
- Announcing an experiment rollout
- Releasing a product update
- When asked "help me write a launch post for Slack"
- Celebrating a milestone or go-live
Process / Template
1. Gather Key Information
- What shipped — feature name, experiment, or release
- Who it's for — target users or segment
- Key metrics — what success looks like (optional)
- Links — docs, dashboards, Figma, demo
- Kudos — who contributed (optional)
2. Use Slack-Native Format
- Emoji — use sparingly for visual anchor (e.g., 🚀 for launch)
- Short paragraphs — 1–2 sentences max
- Bullets — for scannability
- Links — inline, descriptive (not raw URLs)
- Tone — celebratory but informative
3. Structure the Post
Opening
- One-line hook: what shipped and why it matters
Body
- What — brief description of the change
- Who — target users or segment
- Impact — expected benefit or metric (if known)
- Links — where to learn more, try it, or see data
Closing
- Call to action (try it, give feedback) or kudos
4. Keep It Concise
- Aim for 3–5 short paragraphs or bullet blocks
- Skip internal jargon when possible
- Lead with customer value, not implementation details
Output
A Slack-ready launch post that:
- Fits naturally in a #launches or #shipped channel
- Is scannable in 30 seconds
- Celebrates the team
- Points readers to more detail if they want it
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hardiktiwari
- Source: hardiktiwari/PM-operating-OS
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.