suede-directory-submissions

Files (7)

• CARD.md
• SKILL.md
• openai.yaml · agents/
• evals.json · evals/
• directory-list.md · references/
• positioning-variations.md · references/
• submission-tracker-template.csv · references/

SKILL.md (first lines)

# Suede AI Directory Submissions Skills

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.

**Iron Law, approval is per destination:**

```
No external submission, account creation, paid placement, or review request
happens without explicit approval for that exact destination, copy, assets,
timing, and maximum cost. Approval for research or for another destination
never transfers. Any delta is re-approved before it ships.
```

## Compatibility

An agent with web access for directory research and a local tracker. Each actual submission needs separately authorized destination access; a plan requires no new account or paid placement.

## 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 `references/directory-list.md`. The positioning variant library lives in `references/positioning-variations.md`. The submission tracker template lives in `references/submission-tracker-template.csv`.

---

## Three Operating Rules

### Rule 1: Foundation before submission
Before recommending a submission, verify the directory's current official
requirements and record the source URL and check date. The linked page should be
publicly reachable, truthful, useful to the directory's audience, and measurable.
Prepare only the assets the current form requires, using real product screenshots
and approved brand files. Add pricing, legal pages, video, schema, or additional
formats when the product, jurisdiction, or verified directory rules call for them;
do not invent universal prerequisites.

### Rule 2: Destination pages before directories
Choose the most relevant verified destination for each audience: a homepage,
use-case page, integration page, comparison page, template, or documentation page.
It must accurately fulfill the listing promise and have a measurable next step.
Do not impose a fixed page count or block a suitable listing merely because an
unrelated content type does not exist.

### Rule 3: Positioning varies by directory type
Adapt the description to the directory's verified fields, audience, and rules.
Reuse approved facts, but change emphasis when that improves relevance; do not
claim that duplicate descriptions trigger a search or AI penalty without current
evidence. See `references/positioning-variations.md` for templates.

| Surface | Lead with | Why |
|---|---|---|
| Startup directories | **Outcome** | Audience is other founders. They care what it does. |
| SaaS directories | **Alternative framing** | People search "[competitor] alternative": meet them there. |
| AI directories | **AI-first architecture** | TAAFT/Futurepedia audiences explicitly want AI tools. |
| Agent/MCP directories | **Agent/MCP angle** | Use only for a live compatible capability. |
| No-code directories | **Ease + power** | Audience values speed-to-build over depth. |
| Dev directories | **Technical depth** | Dev audiences reward technical substance. |
| B2B review sites | **ROI + use case** | Buyers want outcomes and case studies. |

---

## Workflow

### Step 1: Readiness assessment (Phase 0)

Assess the selected directory against current requirements:

1. Is the product publicly accessible (no password wall)?
2. Is there a pricing page (even "free while in beta")?
3. Are privacy policy + terms live?
4. Are the required approved logo, screenshot, and video assets available?
5. Does the destination page match the proposed listing copy and CTA?
6. Is referral and conversion measurement configured?
7. Does the current directory policy allow this product, claim set, and category?
8. For review sites, are there genuine eligible users and a policy-compliant ask?
9. Who has authority to create the account, accept terms, and submit?

A missing current platform requirement, truthful destination, or submission
authority is a hard block for that directory. At the block: stop work on that
directory, name the blocker in one line ("<directory>: missing <requirement>"),
list the resolution options (obtain the requirement, substitute a truthful
destination, get explicit submission authority, or drop the directory from the
tier), and wait for the user's pick before submitting there. Other gaps are
prioritization inputs, not universal launch blockers.

### Step 2: Choose the tiers

Full catalog in `references/directory-list.md`. Summary:

| Tier | When | Illustrative candidates to verify |
|---|---|---|
| **Flagship launch** | Around a relevant launch | Product Hunt, BetaList, HN Show HN, Fazier, DevHunt |
| **Startup/SaaS** | Launch and rolling | AlternativeTo, SaaSHub, G2, Capterra, F6S |
| **AI directories** | If the product has a substantiated AI capability | TAAFT, Futurepedia, Toolify, Future Tools |
| **Agent/MCP registries** | If a live compatible integration exists | Glama, APITracker, LF MCP Registry |
| **No-code directories** | If the product genuinely serves that audience | NoCodeFinder, No Code MBA |
| **Integration marketplaces** | When the integration ships | The integration owner's official marketplace |
| **Profiles and vertical directories** | When audience and category fit | Relevant company profiles or industry-specific catalogs |

**Triage rule:** Only submit where the product is a genuine fit under the
platform's current eligibility and category rules.

### Step 3: Prepare asset variations

For each tier, prep distinct variants from
`references/positioning-variations.md` only after inspecting the destination's
current form:

From JasonColapietro/suede-creator-skills, MIT.

More from JasonColapietro/suede-creator-skills