Directory Submissions
Directory Submissions skill from Corey Haines’ Marketing Skills collection.
Overview
Directory Submissions is a growth/marketing skill from Corey Haines’ Marketing Skills collection (github.com/coreyhaines31/marketingskills). Directory Submissions skill from Corey Haines’ Marketing Skills collection. The skill is structured around practical workflows—covering Before Starting, Core Philosophy, The Three Hard Rules, Workflow, Product Hunt Deep Dive (The Anchor Event), Reviews Playbook (G2 / Capterra / TrustRadius)—so Claude can move from context gathering to concrete artifacts (briefs, copy, checklists, or audit reports) instead of generic advice. Pair it with related skills in the same collection: `seo-audit`, `launch`, `content-strategy`.
Work with LimeDock
Using this skill? LimeDock can wire it into a durable automation you own.
Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.
We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.
Link
Installation guide
Option A — Install just this skill (recommended)
npx skills add coreyhaines31/marketingskills --skill directory-submissionsOption B — Install the full Marketing Skills collection
npx skills add coreyhaines31/marketingskillsThat unlocks related skills like `cro`, `copywriting`, `emails`, `ads`, and `seo-audit`.
Option C — Manual install (Claude Code)
git clone https://github.com/coreyhaines31/marketingskills.git /tmp/marketingskills
mkdir -p ~/.claude/skills
cp -R /tmp/marketingskills/skills/directory-submissions ~/.claude/skills/directory-submissionsClaude.ai
Customize → Skills → Upload the `directory-submissions` folder as a zip / `SKILL.md` → enable the skill.
Always skim `SKILL.md` before first use so you know its triggers and related skills.
How to use it
1. **Trigger it with directory submissions language** — mention the job by name or ask for the deliverable this skill owns. 2. **Share product context up front** — ICP, offer, URL, constraints, and any metrics. If `.agents/product-marketing.md` (or `.claude/product-marketing.md`) exists, the skill will read it first. 3. **Let it run the assessment** — answer clarifying questions before asking for final copy/strategy. 4. **Request a concrete artifact** — brief, audit, page outline, sequence, scorecard, or launch checklist. 5. **Close the loop** — feed performance data back so the next iteration compounds.
**Typical sections it covers:** Before Starting, Core Philosophy, The Three Hard Rules, Workflow, Product Hunt Deep Dive (The Anchor Event), Reviews Playbook (G2 / Capterra / TrustRadius), Destination Pages Strategy (What the Backlinks Point At), GEO (Generative Engine Optimization).
If Claude does not auto-select it, say: “Use the Directory Submissions skill (`directory-submissions`)…”.
Example prompts
- “Use the Directory Submissions skill to assess our current state and produce a prioritized action plan.”
- “Walk me through how Directory Submissions would approach this step by step, then execute on our product.”
- “Create a reusable checklist and prompt template for running Directory Submissions monthly.”
- “Review my draft plan and improve it with Directory Submissions. Call out assumptions and risks.”
Use cases and examples
- Run a full Directory Submissions workflow on a live product or campaign
- Produce a reusable Directory Submissions brief/checklist for the team
- Audit the current state and prioritize fixes for directory submissions
- Generate first-draft artifacts then refine with brand constraints
- Connect Directory Submissions output to measurement and next experiments
- Document a playbook entry so directory submissions learnings compound
- Apply the “Before Starting” guidance to a current initiative
- Apply the “Core Philosophy” guidance to a current initiative
Prerequisites
- Claude Code, Claude.ai Skills, or another Agent Skills–compatible host
- Product/brand context (ICP, offer, URLs, constraints) for grounded outputs
- Optional: `.agents/product-marketing.md` or `.claude/product-marketing.md` in the repo
- Permission to install third-party skills — audit SKILL.md first
- Optional: analytics or ad-platform access when the task needs real performance data
Tips
- Keep triggers specific so Directory Submissions fires only when that job is requested (avoids context tax).
- Load product-marketing context (ICP, voice, offer) before asking for final copy or strategy.
- Prefer one sharp deliverable per turn—brief, audit, or draft—then iterate with data.
- Audit `SKILL.md` and any scripts before production use; treat community skills as code.
- Pair with `seo-audit` and `launch` when the workflow spans channels.