Skill flagged — suspicious patterns detected

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

TalonForge Launch Blitz (EN/AR)

v1.0.0

Automates simultaneous submission and tracking of your product launch across 21 startup platforms with tailored listings and post-launch monitoring.

0· 62·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/talonforge-launch.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "TalonForge Launch Blitz (EN/AR)" (casperzinou/talonforge-launch) from ClawHub.
Skill page: https://clawhub.ai/casperzinou/talonforge-launch
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 talonforge-launch

ClawHub CLI

Package manager switcher

npx clawhub@latest install talonforge-launch
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The description promises automated simultaneous submissions and tracking across 21 platforms, but the package is instruction-only with no code, no required credentials, no API integrations, and no install steps. Either it is intended as a content-and-checklist generator (which does not require credentials) or it misleadingly promises automation that cannot be performed without account credentials, API access, or tooling. Also note a minor metadata inconsistency: registry metadata lists no homepage, while package.json includes a homepage URL.
!
Instruction Scope
SKILL.md instructs the AI to ask for product details, generate platform-specific copy, produce a checklist and tracker, and 'monitor' platforms for activity. It does not specify how monitoring or submissions are to be done (APIs, authenticated sessions, scraping, or user actions). The instructions are vague about authentication and give the agent broad discretion to 'monitor' and 'track' without constraints, which is scope-creep relative to a content-generation playbook.
Install Mechanism
There is no install spec and no code files to execute — the skill is instruction-only. From an installation perspective this is low risk because nothing is written to disk or downloaded by the skill package itself.
Credentials
The skill declares no required environment variables or credentials. That is consistent with a purely advisory/content-generation skill, but inconsistent with its claim of automated submissions/tracking which would normally require platform credentials or API tokens. If the skill later prompts the user for account credentials to enable automation, that would increase risk and should be considered separately.
Persistence & Privilege
The skill is not always-enabled and uses default invocation settings. It does not request system-wide config access or modify other skills. No persistence or elevated privileges are requested in the package.
What to consider before installing
This package appears to be a playbook that generates platform-specific titles/descriptions, checklists, and a tracker template — not a true automated submitter. Before installing or using it: 1) Expect to provide account credentials or API tokens yourself if you want any real automation; the skill currently does not include OAuth/integration code. 2) Be cautious if the agent later asks for login credentials or API keys — prefer to provide limited-scope tokens or use separate/dedicated accounts, and never paste passwords into an agent without understanding how they will be stored. 3) Automated submissions can violate some platforms' terms or trigger anti-bot defenses; verify each platform's API and rules. 4) The package has no installable code and an unknown source (no verified homepage in registry metadata), so treat it as a template/assistant workflow rather than a turnkey automation tool. If you need true automation, look for a skill that explicitly documents required credentials, OAuth flows, APIs used, and safe storage/usage of tokens.

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

arabicvk9747jpsse4h4h25fndfccmqf584wtjdbilingualvk9747jpsse4h4h25fndfccmqf584wtjdlatestvk9747jpsse4h4h25fndfccmqf584wtjdlaunchvk9747jpsse4h4h25fndfccmqf584wtjdmarketingvk9747jpsse4h4h25fndfccmqf584wtjdopenclawvk9747jpsse4h4h25fndfccmqf584wtjd
62downloads
0stars
1versions
Updated 1w 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...