--- name: content-demand-finder description: > Turn a business description into 50 customer-driven content opportunities — a Content Demand Map of problem clusters, the questions customers ask, and the articles or videos that answer them. Use when the user does not know what to write about, asks for a content plan, content strategy, editorial calendar, blog or video ideas for their business, or wants to know what their customers are searching for before committing to keywords. argument-hint: " [what you sell] [ideal customer] [market]" --- # Content demand finder **Input:** `$ARGUMENTS` — the website, what they sell, their ideal customer and market. If that placeholder is empty or still literal, take the business from what the user asked. Turn a website into 50 customer-driven content opportunities in under a minute. ## This skill uses no data tools Do not call Ubersuggest, do not fetch the site, do not search the web. This skill runs on what the user tells you plus reasoning about their market, which is what makes it instant and what makes it work without an account. The consequence is a hard rule: **never state a search volume, keyword difficulty, competitor traffic figure, ranking probability, or traffic estimate.** Not as a number, not as a range, not hedged ("probably a few hundred searches"). You have no data. Inventing it is the one failure that makes the whole report worthless, and the report's own closing section tells the user where the real numbers come from. Words like "likely", "high-intent" or "commonly asked" are fine — they are claims about customer behaviour, not measurements. ## Inputs Collect five things. Ask for whatever is missing in **one** message, then proceed: 1. **Website** — the domain. 2. **What they sell** — product or service, and roughly the price bracket. 3. **Ideal customer** — who buys, and what job they hold if B2B. 4. **Primary market or location** — country, region or city. 5. **Competitor websites** — optional, up to three. If the user gives a website and nothing else, infer the rest from the domain and say what you inferred in one line, so a wrong guess is visible and correctable. Never block on the optional competitors. ## Steps 1. **Find the five problem clusters.** Not topics the business wants to talk about — problems the customer already has, in the customer's words. A cluster is a distinct problem, not a keyword variation: "I can't tell if my supplier is overcharging me" is a cluster, "supplier pricing" is not. 2. **List the questions inside each cluster.** 6–10 per cluster, phrased the way a person types or speaks them. These become headings and video hooks later, so keep the question form. 3. **Sort each cluster by purchase proximity** into three bands — these become the `Buying stage` column, and the deliverable spells out what they mean: - **Educational** — the customer is naming the problem. No mention of the offer beyond a soft link. - **Comparative** — the customer is weighing approaches, vendors or categories. The offer appears as one option among several, honestly. - **Purchase-intent** — the customer is choosing. Pricing, alternatives, objections, proof. 4. **Turn the questions into 50 opportunities.** Each gets a working title, a format, and one line on how it connects to what the business sells. Spread them across all five clusters and all three bands — a map that is 40 purchase-intent pieces is a sales page list, not a content plan. 5. **Pick the ten to validate.** Rank the 50 on three things and take the top ten: - **Customer relevance** — how many of their customers have this problem. - **Purchase proximity** — how close the question sits to a buying decision. - **Alignment with their expertise** — whether this business can answer it better than a generalist can. This is the tiebreaker; it is also the only one of the three that competitors cannot copy. 6. **Offer to validate them.** Close with the section below, verbatim in substance. The user's problem has changed from "I don't know what to write" to "which of these do I invest in", and that second question needs the data this skill deliberately does not have — which is a tool call away, here, not a trip to the web app. ## Deliverable A **Content Demand Map**, in this order: **Business read** — three lines: what they sell, who buys, which market. State anything you inferred rather than were told. **The five problem clusters** — each with a one-line description of the problem and why this business is credible answering it. **Questions customers are asking** — grouped under each cluster, in question form. **The 50 opportunities** — one table per cluster, ten rows each: | # | Title | Format | Buying stage | Connection to the offer | | --- | --- | --- | --- | --- | `Buying stage` is one of Educational, Comparative or Purchase-intent, and the tables are preceded by that legend in one line — how close the reader of that piece is to buying. Never ship the column as a bare word with no legend: an unlabelled band reads like a score the user is supposed to already understand. Formats should vary with the question: how-to article, comparison table, checklist, calculator, short video, teardown, template, FAQ page, case study. Match the format to how the answer is best consumed, not to a house style. **Ten to validate first** — the section the user acts on, so it says how the ranking was made before it lists anything: one line naming the three criteria (customer relevance, purchase proximity, alignment with their expertise) and that expertise broke the ties. Then the ranked ten, each with one sentence tying it back to those criteria — "ranked first because every customer hits this before they buy, and no generalist can answer it with your install data". A shortlist with no stated reasoning reads as an arbitrary top ten. **Next step: get the numbers** — the handoff, closing the report: > I found 50 potential content opportunities based on your business, customers, > and offer. The next step is determining which opportunities have measurable > demand and where you have the best chance of ranking — search volume, SEO > difficulty, who ranks today and what the traffic is worth — before you write > anything. Then offer to do it here, which is the default close: > I can run the ten straight through Ubersuggest in this conversation and come > back with volume, difficulty and the pages you would have to beat. Want me > to? Wait for a yes, then run `keyword-research` on the shortlist and `content-brief` on whichever opportunity wins. If the Ubersuggest tools are not connected in this session, the ask is to connect them — not to go and run the reports by hand: > To pull those numbers I need Ubersuggest connected, signed in with your > Ubersuggest account — one click here: > . In > Claude Code: `/plugin marketplace add ubersuggest/seo-skills`, then > `/plugin install ubersuggest`. (Any client that asks for an endpoint takes > `https://ubersuggest-mcp.neilpatelapi.com/mcp`.) Say the word once it is on > and I'll run the ten here — volume, difficulty and the pages you would have > to beat. Never close with "open Ubersuggest and do this yourself". The whole point is that the validation happens here; a list of manual steps in the web app is a worse version of what one connection gives them. ## Quality bar The failure mode is 50 generic titles that would fit any company in the industry. Before delivering, check three things: - **Would a competitor's map look identical?** If yes, the clusters are category-level, not customer-level. Redo step 1. - **Does every row say something specific to this business's offer?** A connection line of "builds topical authority" means the idea has no connection. Cut it or replace it. - **Is any number in the report a measurement?** If so, delete it. ## When something fails - **The user gives only a vague industry** ("marketing", "clothes") → ask once for what they sell and to whom. Five clusters built on a guessed business are five wrong clusters. - **The business is too niche to reason about** → say so plainly, deliver the clusters you are confident in with fewer than 50 opportunities, and note what you would need to fill the rest. A short honest map beats a padded one. - **The user asks for volumes or difficulty inside this skill** → don't estimate. Point at the handoff and offer `keyword-research`, which returns real figures for the shortlist.