suede-directory-submissions
Suede-affiliated directory distribution strategy for selecting listings, sequencing submissions, tailoring positioning, and verifying backlinks. Use when a product needs startup, SaaS, AI, MCP, marketplace, or review-directory submissions and a measurable tracker. NOT FOR: broader launch orchestration (use suede-launch-packaging), scalable destination-page production (use suede-programmatic-seo), or citation and search auditing (use suede-seo-audit).
npx skills add JasonColapietro/suede-creator-skills --skill suede-directory-submissions --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill instructs the agent to treat directory distribution as a verifiable discovery layer rather than a chaos of submissions. It directs building a backlink and buyer-discovery foundation by selecting appropriate directories, sequencing around launch moments, adapting truthful positioning, and checking that each listing and backlink actually landed. It emphasizes using current directory requirements, preparing assets, and ensuring destination pages match proposed listing copy and CTAs, plus configuring referral and conversion measurement.
How it works
- Read product-marketing context if available, and use it for questions only if not already covered.
- Follow the Three Operating Rules: verify directory requirements (source URL and check date), ensure destination page matches listing copy and CTA, and adapt positioning per directory type.
- Use the provided tiering to choose where to submit (Flagship, Startup/SaaS, AI, Agent/MCP, No-code, Integrations, Profiles/vertical).
- Prepare asset variations per tier using positioning templates, ensuring assets (logo, screenshots, video) and copy stay within verified form limits.
- Build and maintain a submission tracker in the references/submission-tracker-template.csv, draft exact field values and assets for each submission, obtain explicit approval before submission, and log outcomes.
- For each live listing, log the canonical URL and inspect link behavior (rel header, redirects) and record the method and check date.
- When crafting destination pages, match each listing to the most truthful page (home, use-case, template, or other) and ensure the page satisfies the listing promise.
- Apply KPIs and tracking to measure listings, referring links, sessions, conversions, reviews, and related metrics per the template.
When to use it
Use when a product needs startup, SaaS, AI, MCP, marketplace, or review-directory submissions and a measurable tracker. Not for broader launch orchestration, scalable destination-page production, or citation/search auditing.
What it can touch
- Uses the tracker spreadsheet at references/submission-tracker-template.csv to log submissions.
- References directory and positioning materials at references/directory-list.md and references/positioning-variations.md for asset variations and copy templates.
- Requires reading current directory requirements, official help pages, and registered rules for each platform.
Caveats
- Do not promise outcomes not stated (e.g., guaranteed rankings or traffic).
- Do not rely on unverified directories or misstate requirements; hard blocks exist if requirements or authority to submit are missing.
- It emphasizes truthful positioning and realistic expectations rather than claims of authority, traffic, or ranking.
# Suede Directory Distribution Suede treats directory distribution as a verifiable discovery layer, not a submission-count contest. Build the user's backlink and buyer-discovery foundation by selecting the right directories, sequencing them around real launch moments, adapting truthful positioning, and checking that each listing and backlink actually landed. ## Before Starting **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. --- ## Core Philosophy Directory submissions can add discovery surfaces, referral paths, and backlinks, but their value varies by product, directory, listing quality, and current platform rules. Treat each benefit as a hypothesis to verify with listing status, referral analytics, search data, and qualified outcomes. A directory plan complements destination pages and other distribution; it does not guarantee authority, citation, traffic, ranking, or leads. The full directory catalog lives in `r
- Before Starting
- Core Philosophy
- Three Operating Rules
- Rule 1: Foundation before submission
- Rule 2: Destination pages before directories
- Rule 3: Positioning varies by directory type
- Workflow
- Step 1: Readiness assessment (Phase 0)
- Step 2: Choose the tiers
- Step 3: Prepare asset variations
- Step 4: Batch submit
- Flagship Launch Listing
- Preparation milestones
- Launch and follow-through
What does the suede-directory-submissions skill do?
Suede-affiliated directory distribution strategy for selecting listings, sequencing submissions, tailoring positioning, and verifying backlinks. Use when a product needs startup, SaaS, AI, MCP, marketplace, or review-directory submissions and a measurable tracker. NOT FOR: broader launch orchestration (use suede-launch-packaging), scalable destination-page production (use suede-programmatic-seo), or citation and search auditing (use suede-seo-audit).
How do I install it?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-directory-submissions --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.