How do I install the Market Gap Microsite skill?

Run npx skillmds@latest add danielonpurpose/market-gap-microsite in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Market Gap Microsite safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Market Gap Microsite?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Market Gap Microsite free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Market Gap Microsite?

DanielOnPurpose (@danielonpurpose) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Market Gap Microsite by danielonpurpose

Name: Market Gap Microsite
Author: DanielOnPurpose

Market Gap Microsite

Recruitment pipeline — turn foot-traffic / market data into a market-gap analysis map and a branded recruitment microsite that shows a target brand its footprint, your market's gap, and demand proof. Use when the user wants to pitch a new retail/restaurant brand, work with trade-area data, or update the gap-analysis template.

File contents

Market-Gap Microsite Pipeline

A recruitment pipeline: show a target brand its regional footprint, your market's gap, and the anchor-demand proof that the catchment is real.

The building blocks

A template map + guide (edit only a clearly marked BRAND DATA section of the HTML).
One worked example folder to clone from.
Trade-area source data (foot-traffic reports, visit counts).
A target note per brand.

Design rules (hard-won — never break)

No straight-line distance rings. They never match road-mile labels and discredit the map. Show distance as connecting lines + a sidebar instead.
Road miles + drive times everywhere, never straight-line distance.
Keep a constant anchor (e.g. a major retailer) across brands — it's the proof the catchment is real. Only the brand's locations and projection change per pitch.
The map must show region-wide location density so the gap is visually obvious — a zoomed-in map that hides the pattern misses the point.
Verify pin alignment and the anchor cross-reference data before showing anyone.
Keep the map a single static HTML file (no framework/build) so it drops into any microsite.
A star icon marks your target location.

Pipeline steps

Ingest the brand's trade-area report(s) → extract locations, visit counts, catchment data.
Clone the template to a new brand folder; fill the BRAND DATA section per the guide.
Verify the map locally (serve over HTTP, not file://) — check rules 1–7.
Write/update the PRD and the brand target note.
Build the microsite from the reference template: your branding, hero, a catchment explainer section, and the embedded gap map.
Package per the ship-site skill (folder + zip; host drop = folder, not zip).
File everything back into your knowledge base and update the outreach tracker with the new target's status.

Outreach step (often forgotten)

The microsites exist to power a cold-outreach campaign. After a site ships, offer the outreach emails / broker contact list for this brand — that phase gets left dangling otherwise.

---name: market-gap-micrositedescription: Recruitment pipeline — turn foot-traffic / market data into a market-gap analysis map and a branded recruitment microsite that shows a target brand its footprint, your market's gap, and demand proof. Use when the user wants to pitch a new retail/restaurant brand, work with trade-area data, or update the gap-analysis template.---# Market-Gap Microsite PipelineA recruitment pipeline: show a target brand its regional footprint, your market's gap, and the anchor-demand proof that the catchment is real.## The building blocks- A **template** map + guide (edit only a clearly marked BRAND DATA section of the HTML).- One **worked example** folder to clone from.- Trade-area **source data** (foot-traffic reports, visit counts).- A **target note** per brand.## Design rules (hard-won — never break)1. **No straight-line distance rings.** They never match road-mile labels and discredit the map. Show distance as connecting lines + a sidebar instead.2. **Road miles + drive times everywhere**, never straight-line distance.3. **Keep a constant anchor** (e.g. a major retailer) across brands — it's the proof the catchment is real. Only the brand's locations and projection change per pitch.4. The map must show **region-wide location density** so the gap is visually obvious — a zoomed-in map that hides the pattern misses the point.5. Verify pin alignment and the anchor cross-reference data before showing anyone.6. Keep the map a **single static HTML file** (no framework/build) so it drops into any microsite.7. A star icon marks your target location.## Pipeline steps1. **Ingest** the brand's trade-area report(s) → extract locations, visit counts, catchment data.2. **Clone** the template to a new brand folder; fill the BRAND DATA section per the guide.3. **Verify** the map locally (serve over HTTP, not file://) — check rules 1–7.4. **Write/update the PRD** and the brand target note.5. **Build the microsite** from the reference template: your branding, hero, a catchment explainer section, and the embedded gap map.6. **Package** per the `ship-site` skill (folder + zip; host drop = folder, not zip).7. **File everything** back into your knowledge base and update the outreach tracker with the new target's status.## Outreach step (often forgotten)The microsites exist to power a cold-outreach campaign. After a site ships, offer the outreach emails / broker contact list for this brand — that phase gets left dangling otherwise.

Frequently asked questions