Agent skill for directory submissions
Install it and your AI agent can submit your product to directories for you. One site at a time, in your own browser. It checks whether you're already listed, fills the form from a product profile kept on your machine, and only records a site after it sees a confirmation. You sit next to it and watch. When a CAPTCHA shows up, it stops and waits for you.
- One site at a time, in your browser
- Checks for an existing listing before filling anything
- Your product data stays on your machine
- Never pays, signs up or touches a CAPTCHA
export WHERETOSUBMIT_TOKEN=wts_...
claude plugin marketplace add \
johnwick7zz/wheretosubmit-backlink-skill
claude plugin install \
wheretosubmit@wheretosubmitHow it works
You say "submit my product to 10 free directories". It picks sites from your project through the MCP, highest DR first, skips the paid ones, and shows you the list. It starts only when you say go.
Then it goes site by site. It opens the site and searches for your product name first. Already listed? It marks that one approved and moves on. If not, it reads the whole form before typing anything, looking for hidden fees or a sign-up step. Then it fills it from your profile. When a site caps the description at 160 characters, it picks the shorter version from your profile. It won't write a sentence you never said.
It presses the site's real submit button and reads what comes back. Only a confirmation like "thanks, we'll review it", or a confirmation email, gets the site marked as submitted, with that sentence saved as the note. Each site is written to your account right away, so a run that stops halfway loses nothing.
What you need
- A Where To Submit account. Reading sites is free. Writing progress to your account needs Pro.
- An MCP token from your Account page. The MCP page has the steps.
- An agent with a browser tool. We run our own submissions with ego-browser (lite.ego.app, macOS and Windows): you and the agent share one window, so you can watch it fill a form and take over a CAPTCHA. Claude in Chrome, the Claude desktop browser and Playwright MCP work too. Without one, the agent stops.
- A mail tool, such as Gmail MCP. Some sites send a confirmation link by email. Without a mail tool, those sites get skipped.
How to install
Pick one of the three. If you use the plugin, don't also add the same server with claude mcp add, or the agent sees every tool twice.
Claude Code plugin. Installs the skill and the MCP server together, the easiest way. Put your token in the shell profile Claude Code starts from, such as ~/.zshrc, then open a new terminal.
export WHERETOSUBMIT_TOKEN=wts_...Then run these two commands inside a Claude Code session.
/plugin marketplace add johnwick7zz/wheretosubmit-backlink-skill
/plugin install wheretosubmit@wheretosubmitRun /mcp and check that wheretosubmit is connected. A 401 or a missing-variable warning means the shell that started Claude Code didn't have the variable. Set it and restart.
Other agents. The skills CLI finds the skill in the repository by itself.
npx skills add johnwick7zz/wheretosubmit-backlink-skillAdd -g to install it for all your projects. Then connect the MCP server in your agent's own config, as shown on the MCP page.
Manual copy. Download the repository from GitHub, unpack it, and copy the skill folder to wherever your agent loads skills. For Claude Code it looks like this.
cp -R skills/wheretosubmit-submit ~/.claude/skills/Then connect the MCP server and restart the session.
What happens on the first run
The agent checks the MCP connection and your plan, finds your product URL and matches it to a project in your account. Reuse one or make a new one? It asks. It won't decide that for you.
Then it creates a .wheretosubmit/ folder in your project: profile.json for the product facts, assets/ for the logo and screenshots, evidence/ for confirmation screenshots. It drafts the profile from your website and asks you to check it. Anything it can't find stays empty.
Next comes a preflight check: are the facts complete, is the logo big enough. It also reads one email to make sure the mailbox works. If it can't, it skips sites that verify by email or need an account. Then it shows you the batch and waits for your go-ahead.
Only each site's status and a one-line note go to wheretosubmit.org. The profile and the screenshots stay on your machine.
What it never does
- Pay. Even if you allow paid sites, it stops at the checkout page and hands it to you.
- Register accounts or make passwords, unless you say it's fine.
- Solve or click past a CAPTCHA. It fills in the form and leaves the CAPTCHA to you.
- Make up facts. It uses your profile and your answers, and when the text is too long it only cuts, never adds.
- Submit to the same site twice. If the first try was unclear, it puts that in the report and lets you decide.
Sites that aren't done after submit
On some sites, pressing submit is only the start. The agent tags those, and the next run deals with them first.
badge- The site wants its badge or a link on your website before it approves you. The agent saves the snippet and lists it for you. It doesn't touch your website.
verify_email- A verification email came in and the agent couldn't finish it, for example because it couldn't read the mailbox.
awaiting_review- The site reviews by hand and you're in the queue.
Every later run starts here. Badge live? It checks for the listing. Email link still waiting? It clicks it. In review for more than a week? It looks again. A live listing gets marked approved. In every case, nothing gets submitted twice.
More
Tokens and the seven tools are on the MCP page. The full workflow, the profile format and the changelog are in the GitHub repository.
More on Where To Submit
The skill submits to the same directory you can browse here. The guides explain how the bigger sites work, and the Chrome extension fills in blog comment forms.
The skill is open source under the MIT license. It uses your own browser and your own sign-ins, and it stops to ask whenever something looks off.