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.
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/listing-distribution && cp -r /tmp/listing-distribution/plugins/demand-generation/skills/listing-distribution ~/.claude/skills/listing-distributionSKILL.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. ## 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.
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.
Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.
Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.