Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Launch Blitz

v1.0.0

Automatically formats, submits, and tracks your product launch across 21 major startup directories with tailored listings and status monitoring.

0· 60·0 current·0 all-time
byzinou@casperzinou

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for casperzinou/launch-blitz.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Launch Blitz" (casperzinou/launch-blitz) from ClawHub.
Skill page: https://clawhub.ai/casperzinou/launch-blitz
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install launch-blitz

ClawHub CLI

Package manager switcher

npx clawhub@latest install launch-blitz
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's stated purpose is to auto-format, submit, and track listings across 21 platforms. However, SKILL.md and the package.json list no integration methods (APIs, endpoints, or automation tools) and the manifest declares no credentials or env vars. Many listed platforms (e.g., ProductHunt, Betalist, Hacker News, X) require authenticated accounts or platform-specific submission flows — the required access is missing, so the declared capability is disproportionate to the provided requirements.
!
Instruction Scope
Runtime instructions are high-level and open-ended ('Run the launch blitz'; 'Your AI will ask...') but give no safe, constrained procedure for performing submissions. They don't specify whether submissions are done via official APIs, web automation, or manual guidance. That vagueness can cause the agent to (a) ask the user for account credentials or cookies, (b) instruct local browser automation, or (c) send data to unspecified endpoints — any of which increases risk.
Install Mechanism
There is no install spec and no code files to execute beyond the SKILL.md and a minimal package.json. This reduces risk from downloaded/embedded binaries. However, because it's instruction-only, the agent's runtime behavior will depend entirely on the agent environment and available tools (browser, HTTP client, automation), which is not described.
!
Credentials
The manifest declares no required environment variables or primary credential, yet the skill's tasks inherently require account credentials or API keys for multiple third-party services. The absence of declared credential requirements is disproportionate and ambiguous — the agent may solicit credentials interactively or ask users to paste tokens into chat, which is risky.
Persistence & Privilege
The skill is not marked 'always:true' and uses normal autonomous invocation settings. It does not request system-level persistence or configuration changes in the manifest. That said, because instructions are open-ended, the agent could be instructed to store credentials or logs elsewhere if the user provides them — the manifest does not authorize or describe any storage behavior.
What to consider before installing
This skill's goal (automated multi-platform submission) reasonably requires platform accounts, APIs, or browser automation, but the skill provides none of those details. Before installing or using it, ask the author: which integration methods are used for each platform (API vs manual web form), how authentication is handled (OAuth/app tokens vs passwords), and where/if credentials are stored. Do not paste account passwords into chat — prefer short-lived API tokens or OAuth redirects. If you plan to test it, use throwaway accounts and a dummy product. If the author cannot supply concrete integration docs or a safe auth flow, treat the skill as risky and avoid giving it real credentials.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ecvpyc5aaebc8kte64v7nz184vfeh
60downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Launch Blitz Skill

Auto-submit your product to 21 platforms

What It Does

Prepares and submits your product launch to all major startup directories simultaneously:

  • Formats your listing for each platform's requirements
  • Generates titles, descriptions, and tags
  • Tracks submission status
  • Ensures maximum compounding effect from simultaneous launch

Supported Platforms

  1. ProductHunt
  2. Betalist
  3. Uneed
  4. TrustMRR
  5. Fazier
  6. OpenAlternative
  7. Microlaunch
  8. Peerlist
  9. TinyLaunch
  10. SaaSHub
  11. Indie Hackers
  12. Hacker News (Show HN)
  13. Toolfolio
  14. Tiny Startup
  15. SideProjectors
  16. AlternativeTo
  17. LaunchIgniter
  18. PeerPush
  19. SaaS Genius
  20. There's an AI for That
  21. DevHunt

Setup Instructions

Tell your AI: "Run the launch blitz."

Your AI will ask:

  1. "Product name?"
  2. "Tagline (under 140 chars)?"
  3. "URL?"
  4. "Price?"
  5. "Category? (AI / Productivity / Developer Tools / etc.)"
  6. "What makes it unique? (1-2 sentences)"
  7. "Any alternatives it competes with?"
  8. "Launch date?"

What Gets Generated

For each platform:

  • Platform-specific title (some have character limits)
  • Short description (140 chars)
  • Medium description (280 chars)
  • Long description (500 chars)
  • Tags/categories
  • Direct submission URL

Launch Day Checklist

Your AI generates and tracks:

## Launch Day Checklist
- [ ] ProductHunt — submit (needs account, 12am PST timing)
- [ ] Betalist — submit (needs approval, submit 2 weeks early)
- [ ] Hacker News — Show HN post
- [ ] Indie Hackers — story post
- [ ] All others — submit listings
- [ ] X launch thread (English)
- [ ] X launch thread (Arabic, if applicable)
- [ ] Track all submissions in launch tracker

Launch Tracker Template

# Launch Tracker — [PRODUCT]

| # | Platform | Submitted | Status | URL | Notes |
|---|---|---|---|---|---|
| 1 | ProductHunt | ⏳ | Pending | | |
| 2 | Betalist | ⏳ | Pending | | |
| ... | ... | ... | ... | ... | ... |
| 21 | DevHunt | ⏳ | Pending | | |

Post-Launch

After submissions, the AI:

  1. Monitors each platform for approval/activity
  2. Tracks upvotes, comments, and traffic
  3. Reports results after 24h, 48h, 7 days
  4. Suggests follow-up actions based on performance

Version

1.0 by TalonForge

Comments

Loading comments...