Launch Blitz
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill is a coherent launch-submission helper, but it directs the agent to publish across many public platforms and monitor results without clear approval, credential, or stop boundaries.
Before using this skill, treat it as a public-posting workflow: ask it to draft submissions first, review every listing, choose which platforms to use, and only authorize posting from accounts you are comfortable using. Do not provide passwords directly to the agent.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A wrong, premature, or unwanted listing could be published across many public launch sites at once.
This directs the agent toward broad public posting across many services, but the instructions do not require explicit user review or approval immediately before submission.
Prepares and submits your product launch to all major startup directories simultaneously
Require the agent to generate drafts first, let the user choose platforms, and obtain explicit confirmation before each public submission or social post.
The agent may need access to the user's launch-platform accounts, creating risk if credentials, browser sessions, or broad account permissions are used without clear limits.
The workflow requires actions through third-party accounts, but the artifacts do not define how authentication should be handled, which accounts may be used, or what permissions are acceptable.
ProductHunt — submit (needs account, 12am PST timing)
Declare required account access, avoid password collection, prefer user-driven login/OAuth where possible, and confirm the exact account and platform before posting.
The agent could continue checking launch sites or related metrics after the initial task unless the user sets clear limits.
The skill describes ongoing activity after the initial submission. It is bounded and purpose-aligned, but the artifacts do not state how the user starts, stops, or limits this monitoring.
Monitors each platform for approval/activity ... Reports results after 24h, 48h, 7 days
Ask the user to approve any scheduled monitoring, define the data sources, and provide a clear stop condition.