← ClaudeAtlas

shadow-scoutlisted

Competitor and design-inspiration research that kicks off a client website project — the research front-end that runs before a build skill's discovery/kickoff step. Use this whenever the user mentions landing a new website client, starting a site build for a business or niche, or asks who a client's competitors are, what other sites in the space look like, or where to find design inspiration or reference sites for a web project — even if they never say the word "research". Also use proactively when a website build is about to start and no SCOUT.md research file exists yet. Input is a niche plus optional client name, location, and known competitors. Output is a research/SCOUT.md file containing competitors to differentiate from, niche clichés to ban, aspirational design references with named stealable patterns, and signature-element ideas — ready to hand to a website build skill's discovery/brief step. Research only — this skill never builds pages; that's a separate step.
TheShadowLeader/shadow-scout · ★ 0 · Web & Frontend · score 67
Install: claude install-skill TheShadowLeader/shadow-scout
# shadow-scout Research a client's competitive landscape and gather design inspiration before a website build. The output serves two opposite purposes, and keeping them separate is the whole point: - **Competitors** show what the niche does — so the new site can *differentiate from* it. - **Aspirational references** show award-level craft (usually from *outside* the niche) — so the build can *borrow from* it. Mixing these up produces sites that look like a nicer version of the same template every competitor uses. The deliverable, `SCOUT.md`, is a research front-end: it feeds directly into whatever build skill runs next — hand it to that skill's discovery / brief / kickoff step (for example, a build skill that reads a `DISCOVERY.md` and a `PROJECT_BRIEF.md` would use `SCOUT.md` to seed the brand-direction section), or straight into your own manual discovery process if you aren't running one. ## Inputs Required: the niche (e.g. "boutique physiotherapy clinic"). Helpful when available: client name, city/market, known competitors, main services, and anything the user already likes. If only the niche is given, proceed — don't interrogate. If even the niche is unclear, ask one short question. If the user can't be asked (non-interactive run), proceed with clearly labeled assumptions. ## Process Work through four sweeps. Use web search and fetch pages to verify — every URL in the output must come from an actual search result or fetched page. Never invent or recall-from-memory