Claude Skill

Teach your agent to submit here

Say this to your agent. It fetches the skill, reads your product page, runs the 7 readiness checks, writes the listing and submits it. You get one email with one link. Clicking it is the whole of your part — there is no account to make and no key to fetch.

What it does with that

There is nothing to install by hand and no server to connect. The skill is one Markdown file at a URL; an agent fetches it the way it fetches anything else, and it says what to do next.

If you would rather keep a copy — pinned to a version, or on a machine with no network — the same files are in an archive below.

1. Your agent fetches the skill

curl https://worthtotry.com/skill.md

2. It audits the page and submits, with your address

curl -X POST https://worthtotry.com/api/v1/submissions \
  -H 'content-type: application/json' \
  -d '{"url":"https://yourtool.com","email":"you@yourcompany.com"}'

3. You click the link we email you

That is the whole of your part.

What is inside

5 files: one entry point and 4 references the agent pulls in only when it needs them.

FileWhat it covers
SKILL.mdThe workflow: audit, draft, submit, hand back
references/listing-fields.mdField limits, categories, the no-links rule
references/readiness-checks.mdThe 7 audit checks and the fix for each
references/rest-api.mdThe endpoint, its body and what it returns
references/mcp-tools.mdThe same job over MCP, for agents that prefer it

The agent reads SKILL.md and pulls in a reference only when it needs one, so a question about categories does not cost it the whole REST spec.

Nothing goes up without your click

The skill states the ceiling in its opening lines, because an agent that oversells what it can do is worse than no agent. It can write and send a submission. It cannot make one real: that takes the link we email to the address on it, so a listing cannot appear for a product whose owner never agreed to it.

  • It audits your page and reports every fix it cannot apply itself
  • It drafts copy that fits the limits, and shows it to you before sending
  • It cannot confirm the submission, choose a launch date, or pay for anything — there is no endpoint that would let it
  • It cannot decide whether the listing is published. Every submission is reviewed, and anything the review will not pass waits for a person

The other ways in

Fetching the URL is the short path, and everything else here reaches the same place. The archive is the same files, for pinning a version or for a machine with no network. The MCP server carries the same guidance in its instructions and tool descriptions, for an agent already set up that way. And the browser form takes a URL and drafts the listing from your page exactly as the agent would.

The agent skill, answered

What is the WorthToTry agent skill?

Markdown at a URL — 5 files, with one entry point — that an agent reads before it touches the directory. It carries the submission workflow, the 7 readiness checks and the fix for each, the field limits, the rule that maker-written text may not contain links, and exactly where the agent's authority stops.

How do I install it?

You do not install anything. Say this to your agent: "Install the skill at https://worthtotry.com/skill.md and list my product on WorthToTry." It fetches the file the way it fetches any other page, and the file says what to do next. If you would rather keep a copy — pinned to a version, or on a machine with no network — the same files are in an archive on the skill page.

Do I need an account, a key, or the MCP server?

None of the three. The submission is one POST carrying the product URL and the owner's email address, and we email them a link that finishes it. The MCP server does the same job with a session attached and is worth connecting only if the agent is already set up that way.

Can the skill list my product without me?

No, and the skill says so in its opening lines. It can write and send a submission, but nothing happens until the link we email is clicked, so a listing cannot appear for a product whose owner never agreed to it. Confirming, choosing a launch date and paying are not exposed to an agent at all. Publication is not the agent's decision either: every submission is reviewed, and anything the review will not pass waits for a person.