Skip to content
FunCoding

Search

Search docs, Skills and MCP

listing-distribution

Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.

浏览器自动化2kplugins/demand-generation/skills/listing-distribution/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/cbrock84/headcount/listing-distribution/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Listing distribution

Low effort, compounding, and consistently under-done. Also easy to do in a way that wastes weeks.

Choosing where to list

Judge each by whether real buyers use it, not by domain authority. The directories worth the time are the ones your buyers already consult during evaluation.

  • Category review sites — highest value where they exist for your category. Buyers read these during active evaluation.
  • Curated niche directories — moderate traffic, good qualification, usually a real editorial bar.
  • Launch platforms — a spike, not a channel. Worth doing once, with preparation.
  • Bulk submission lists — mostly worthless, and the low-quality end carries real risk. Skip them.

Preparing once, reusing everywhere

Assemble a kit before submitting anywhere: descriptions at several lengths, logo and screenshots at the common sizes, category selections, feature list, pricing summary, and the founder or company details these forms always want. Submissions then take minutes instead of an afternoon each.

Keep the positioning identical across listings. Inconsistent descriptions across directories are both a brand problem and a signal problem.

Review platforms

The listings that most influence buyers. Claim the profile, complete it fully, and keep it current — a stale listing with old pricing costs deals.

Ask for reviews from customers at a success moment, never with an incentive tied to sentiment. Respond to every negative review specifically and without defensiveness; prospects read the responses more carefully than the reviews.

Comparison and alternative pages

Pages targeting "X versus Y" and "alternatives to X" capture buyers already in evaluation, which is the highest-intent traffic available.

Write them honestly. Name where the competitor is genuinely better — a comparison that finds you superior on every axis is not believed, and buyers checking it against their own experience will discount the whole page. Keep them current; a comparison against a competitor's two-year-old feature set is worse than nothing.

Maintaining

Set a periodic sweep: listings drift out of date, and an aggregator showing your old pricing will outrank your own page for some queries.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • List everywhere available. Directories with no traffic cost maintenance and dilute nothing but your attention.
  • Let listing copy drift from the positioning of record. Every stale listing is a competing description of the product.
  • Solicit reviews only after a customer complains, or only from customers you know are happy. Both distort the signal you are buying.

Similar Skills

webapp-testing
anthropics/skills180k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser-testing-with-devtools
addyosmani/agent-skills103k

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.

Browser automation

webapp-testing
ComposioHQ/awesome-claude-skills77k

webapp-testing

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Browser automation

browser
code-yeongyu/oh-my-openagent70k

browser

Drives a real browser through the omowright library from the js eval kernel: sites the user is already signed into, forms and clicks, JS-rendered pages, screenshots, web QA, extension popups, a human handoff for login, CAPTCHA or OTP, and a browser you own for scraping, bot-scored targets, network capture and QA traces. Use for any interactive browser task; not for a plain search or an unblocked static fetch.

Browser automation

agent-browser
shanraisshan/claude-code-best-practice67k

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Browser automation

cherry-regression-test
CherryHQ/cherry-studio52k

cherry-regression-test

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Browser automation