Distribution Launcher
Plan + track the directory layer of a web-product launch (SaaS / AI / agent-MCP / no-code / dev / B2B). The agent reads the bundled 72-directory registry to pick the right tier mix, writes per-tier positioning that avoids anti-spam flags, and records every submission as a brand-pinned activity event (the volume KPI) via the agentboard coordination peer. 12 registry items + 13 learnings (incl. community-mined Reddit/YouTube launch tactics) + 6 recipes + 4 enforcement scripts. Multilingual EN/DE/RO/FR/ES/RU/HE/AR. Guidance-only meta-package — no callable API; the agent's own LLM does the work following SKILL.md. Adapted from corey/marketingskills (MIT).
Every launch checklist tells you to submit to 100+ directories. I built this skill and then argued with that advice, because the job changed: directory profiles are now a source AI systems read when deciding what to recommend. A stale profile makes AI recommend the product you stopped selling, and those pages never expire on their own. So this skill optimises for fewer, current listings. It carries a registry of 72 directories across 7 tiers and 8 locales, every entry stamped with a lastVerified date, and a verifier that enforces a 180-day window at an 85% fresh floor. It stops you at a 9-item readiness gate (7 hard blocks, 2 soft) before a single form gets filled, and it writes different positioning per tier so you do not trip anti-spam by pasting one description into forty forms. On Product Hunt it sets honest expectations: one documented Product-of-the-Day run turned 1,200 trials into 8 paying customers. It pulls category from icp-discovery, copy from copy-engine, assets from media-generator, hands the run-up to post-writer, and the post-launch spike to outbound-engine. Guidance-only: your agent does the thinking, this gives it the map.
Features5
Filter 72 directories by category, MCP signals and locale instead of blasting all of them
Run a 9-item readiness gate with 7 hard blocks before any form gets filled
Enforce a 180-day freshness window at an 85% floor so AI never cites a dead profile
Vary framing and length per tier so duplicate descriptions stop tripping anti-spam
Plan the 30-day build-in-public on-ramp and the follow-up that converts the spike
Videos1 video
DemoDistribution Launcher · Demo video
Demo · SpiderMediaArticles about Distribution Launcher2 articles
Directory backlinks are dead. Directory profiles are what AI reads now.
opvs.ai21 Jul 2026Directory backlinks are dead. Directory profiles are what AI reads now.
Every launch checklist still says submit to 100+ directories. That advice inverted, because AI now reads directory profiles to decide what to recommend, and a stale profile makes it recommend the product you no longer sell. Here is the skill I built around submitting to fewer.
Videos1 video
DemoDistribution Launcher · Demo video
Demo · SpiderMediaArticles about Distribution Launcher2 articles
Showing all 2
SKILL.mdthe file your agent reads
SKILL.md loads when you open this tab.
What's new6 releases · newest first · from the package's CHANGELOG
v0.3.32026-11-09Latest
Marketplace listing update: added the launch explainer film (`media.demo_video_url`). No code, schema, copy or guidance changes; hero and screenshots unchanged from 0.3.2.
v0.3.22026-07-22
Marketplace visibility + card asset kit. No behaviour change. - **Tier `internal` → `beta`.** The package has been published and HEALTHY since 2026-06-17 but was hidden from customers. It now appears in marketplace search and installs like every other @di-atomic skill. - **Added the SPEC-3 card asset kit** — top-level `media:` block with a 16:9 hero + 3 explanatory panels (dark-board chalk house style), plus `marketing.long_description` (first-person) and 5 verb-led `marketing.features[]`. The card was previously title-only. - **Confirmed the nested bundle shape** shipped in 0.3.1 against `verify-packaging.mjs` (6 pass / 0 warn / 0 FAIL), so `skill_read` resolves SKILL.md + schema.yaml + references/ + recipes/ + registry/ + learnings/. No content changes to references/, recipes/, registry/, learnings/, scripts/.
v0.3.12026-06-22
Bundle shape migration: flat `skills: []` → nested `skills: [{id, schema}]` with SKILL.md and all layers co-located under `skills/distribution-launcher/`. Root-level `SKILL.md` alone was 404-ing `skill_read`.v0.3.02026-06-17
Converted to a guidance-only meta-package per OPVS spec (2026-06-17 "guidance-only skills are first-class"): - **Removed** `schema.yaml` and the 2 method declarations. distribution-launcher's "methods" were always LLM reasoning + a coordination-peer write, never a callable backend — `getDirectoryPlan` is the agent reading the bundled `directory-registry.yaml`, `logSubmission` is a write delegated to the **agentboard** peer. Declaring `base_url` + `auth` against a non-existent backend was 404'ing at runtime. Schema preserved at `source/legacy/client-v0.2.0/schema.yaml` for provenance. - **Added** `skills: []` + 9 `peer_dependencies` (4 upstream OPVS coordination skills + 5 @di-atomic siblings) — the canonical guidance-only shape. Peer ranges use live marketplace versions. - **Fixed** `docs` block — `readme: ./README.md` (marketplace listing), `skill_guide: ./SKILL.md` (what `skill_read` returns), `changelog: ./CHANGELOG.md`. - **Added** `README.md` + this `CHANGELOG.md` at bundle root (security-review required-docs check). - **Reframed** SKILL.md to guidance-only: "Available Operations" → "What this skill does (guidance-only)"; Instructions/Error-Handling/Limitations no longer present a phantom HTTP API; access is via `skill_read`. Version bumped to 0.3.0 in frontmatter. - Kept `provider_config` as the OPVS_PAT/OPVS_API_URL placeholder (CLI 0.4.2 validator still requires it for `skills:[]` packages; harmless — no method calls it). No content changes to references/, recipes/, registry/, learnings/, scripts/.
v0.2.02026-06-16
v2.1 7-layer retrofit + v2.2 Coordination (shipped to marketplace at 100/100, package_id 3fe95957-e821-4663-b107-8c2d1542f8a9): - **Added** the 4 missing v2.1 layers on top of the v0.1.0 base: `learnings/` (10 KI entries → later 13), `registry/` (12 evidence-bundled items + registry.json), `recipes/` (6 use-case workflows), `instructions/` (AGENTS.md + DEPLOYMENT.md). - **Added** Layer 7 `scripts/`: verify-readiness · verify-positioning-variants · verify-registry-freshness (+ verify-coordination at v2.2). - **Added** 3 community-mined learnings (Reddit/YouTube): PH visibility≠customers · don't-blast-directories · 30-day build-in-public window. - **Added** v2.2 `## Coordination` cross-references (SKILL.md + schema.yaml `guidance.uses` + verify-coordination.mjs). - **Added** `references/skill-composition.md` (cross-skill map) + `references/spidergate-routing.md`.
v0.1.02026-05-14
Initial release. Adapted from corey/marketingskills `directory-submissions` (MIT, commit 906c2fb). 2 methods (getDirectoryPlan + logSubmission) + the bundled 72-entry directory-registry.yaml + 4 references. Shipped through Stage 6, then paused at Stage 7 for the v2.1 retrofit.
Showing all 6
