Submit to WorthToTry for Openclaw

Automate AI tool submissions to WorthToTry by auditing a product page, drafting its listing, and returning a review link.

fspecii
v0.1.0
Aug 23, 2026
0
1k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install worthtotry-skill

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install worthtotry-skill using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Submit to WorthToTry?

Submit to WorthToTry is an Openclaw Skills workflow for listing AI products in the WorthToTry directory and weekly launch board. It audits a public product page, prepares optimized listing copy, checks readiness, and opens a draft through the WorthToTry API or MCP server.

The skill removes account, API-key, and browser-consent requirements from the standard submission path. It keeps the product owner in control: the owner opens the emailed or generated review link, adds required assets and the founder’s first comment, and submits the listing for review.

Submit to WorthToTry Use Cases

  • Submit my AI tool to WorthToTry without creating an account.
  • List a product or launch it on the WorthToTry AI directory.
  • Audit a product page for title, logo, metadata, social image, duplicate, and badge readiness.
  • Draft listing copy including the name, tagline, description, categories, pricing, and open-source status.
  • Understand why a WorthToTry submission was rejected or sent back.
  • Generate a review link while preserving the founder’s control over the final submission.
  • Explain the optional WorthToTry badge and its verified-filter and vote-tiebreaker benefits.

How Submit to WorthToTry Works

  1. Confirm the scope: the skill can open a draft but cannot publish, select a launch date, pay for placement, upload the screenshot, or write the first comment.
  2. Collect the public product URL and owner email, then use the no-account REST endpoint for the shortest workflow.
  3. Run the readiness audit before submitting anything. The audit fetches the page, scores it out of 100, returns pass, warn, fail, or info statuses, and provides a suggested listing.
  4. Resolve each non-passing check. Fix the product site when possible, quote the provided fix to the owner when site access is unavailable, and stop if the host is already listed.
  5. Review the extracted listing fields and improve them using the product context and the founder’s own launch note. Keep every field within WorthToTry’s enforced limits.
  6. Submit the draft with the product URL and any corrected listing fields. Omitted fields fall back to the audit extraction.
  7. Return the review URL, readiness score, and every warning. The owner opens the link to capture a screenshot, upload a logo if needed, add the first comment, and submit for review.
  8. Track the lifecycle from draft to pending, approved, and published with get_my_submissions, including any rejection reason.

Submit to WorthToTry Setup

Fast REST setup

No account, API key, OAuth flow, or browser consent screen is needed for the basic submission request:

curl -X POST https://worthtotry.com/api/v1/submissions \
  -H 'content-type: application/json' \
  -d '{"url":"https://theirproduct.com","email":"[email protected]"}'

The response tells WorthToTry to email the owner a completion link. Use the REST API reference for the full endpoint and optional fields.

Optional MCP setup

Use MCP when the person already has the server connected or needs authenticated submission tracking. Add the server once:

claude mcp add --transport http worthtotry https://worthtotry.com/api/mcp/

For clients using a configuration file, register an HTTP MCP server at https://worthtotry.com/api/mcp/. Read-only tools work without authorization. submit_tool and get_my_submissions request the submit and read:submissions scopes; the client opens a browser for one-time approval. If the client cannot complete OAuth, use the REST API and a personal access token instead.

Before submission

  • Read the listing field rules and readiness-check reference.
  • Run check_submission_readiness against a public, reachable product page.
  • Ask the owner for a founder note before drafting.
  • Show the proposed listing copy to the owner before sending it.
  • Explain that the owner must open the review link and finish the submission.

Submit to WorthToTry Data Schema & Taxonomy

Listing fields

Field Constraints or behavior
url Public product URL; private, loopback, invalid, or unreachable URLs are rejected.
email Owner email used for the completion link in the REST flow.
name Maximum 40 characters.
tagline Maximum 60 characters and no trailing period.
description Between 40 and 600 characters.
firstComment Founder’s note, maximum 200 characters, entered by the owner in the review form.
targetKeyword Optional, maximum 100 characters, one keyword with no commas.
categories At least 1 and at most 3 categories.
pricing Correct the extracted pricing classification when needed.
openSource Boolean describing whether the product is open source.

Readiness taxonomy

Check ID Typical status Blocking behavior
title pass or fail Quality issue only; does not block submission.
meta-description pass or warn Quality issue only.
og-image pass or warn Quality issue only.
logo pass or fail Quality issue; the owner may need to upload a logo.
duplicate pass or fail The only blocking check; a failed duplicate check makes submittable false.
badge info Optional; earns a verified mark, verified-filter inclusion, and vote tiebreaker.

Generated and returned data

  • suggestedListing: extracted draft listing produced by the readiness audit.
  • submittable: boolean indicating whether the URL can be submitted.
  • fix: actionable remediation text for each readiness check.
  • detail: existing listing information when a duplicate host is found.
  • slug: identifier returned for the created draft.
  • status: initially draft, then potentially pending, approved, or published.
  • reviewUrl: owner-facing link for screenshot capture, logo upload, first comment, and final review submission.
  • readinessScore: audit score out of 100.
  • warnings: checklist of remaining issues that may cause the listing to return.
  • rejectionReason: explanation available when tracking a rejected submission.

First comments and launch stories must be plain prose without Markdown links, HTML links, iframes, bare URLs, or www. addresses. These fields are handled through REST rather than MCP.

Submit to WorthToTry Advanced Features

  • No-account REST submission path for fast, low-friction directory launches.
  • MCP integration with six tools: search_tools, get_tool, list_categories, check_submission_readiness, submit_tool, and get_my_submissions.
  • Automated readiness scoring with per-check statuses, remediation text, and a generated suggested listing.
  • Duplicate-host protection that stops repeat submissions and points owners to the existing listing.
  • Draft-only permissions that prevent agents from falsely promising publication, launch dates, paid promotion, or approval.
  • Optional badge guidance that accurately explains verified status, filter inclusion, and vote tiebreaking without presenting the badge as mandatory.
  • Structured status tracking across draft, pending, approved, and published states.
  • Strict content validation for listing limits, founder comments, and launch-story text.
  • Owner handoff workflow that preserves human approval for screenshots, logos, founder commentary, and final review submission.
  • Practical error handling for authorization failures, unreachable sites, unsafe URLs, duplicate hosts, and rejected submissions.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*