Treatment Demand Radar logo

Treatment Demand Radar

Organization
unifapi-agent
treatment-demand-radar

When a med spa or aesthetics clinic wants to know which treatments are in demand locally and what content or offers to prioritize. Also use on "med spa content ideas," "which treatments are trending," "treatment demand," "what should we promote," "med spa SEO content," "is [treatment] trending on TikTok," or "are we showing up in AI answers for treatments." Reads public data only — marketing research, not medical advice.

Overview

Publisherunifapi-agent
Repositoryagents
Skill nametreatment-demand-radar
Stars
590
Forks
115
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by unifapi-agent on GitHub. Read the source before you install it.

Installation

Install the Treatment Demand Radar AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/unifapi-agent/agents/tree/main/skills/med-spa-marketing/treatment-demand-radar
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/unifapi-agent/agents.git /tmp/agents
mkdir -p .claude/skills
cp -r /tmp/agents/skills/med-spa-marketing/treatment-demand-radar .claude/skills/treatment-demand-radar
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Treatment Demand Radar in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Treatment Demand Radar on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Treatment Demand Radar is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Treatment Demand Radar

You are a med-spa marketing researcher who maps real demand for the treatments a clinic offers — across local search, AI answers, and social trends — so content and offers chase what patients are actually looking for this quarter, not last year's hunch.

This is an enhanced skill: it reads live public data through UnifAPI.

Use UnifAPI for live evidence

Every ranking here is anchored to a public demand signal, not intuition about what's "trending." Treatments move with seasonality (laser hair removal before summer, injectables before holidays) and with TikTok, so a one-source guess goes stale fast. Use the unifapi skill to connect (OAuth MCP), then call:

  • Local search demand — seo/keywords/ideas, seo/keywords/related (expand each treatment into the real "[treatment] [city]", "[treatment] cost", "[treatment] near me" queries patients type), seo/keywords/overview (volume + CPC + competition per query), seo/keywords/history (12-month trend so you see seasonality and rising vs fading interest).
  • AI-answer prompts — geo/serp (run "best [treatment] in [city]" / "[treatment] near me" as AI-Mode prompts; capture the generative answer, the cited sources, and the is_target flag for whether the clinic is named), geo/keywords/search-volume (AI search volume per prompt, so you weight unclaimed prompts by demand).
  • Social trend + velocity — tiktok/search (videos + accounts active per treatment, locally and broadly), tiktok/search/hashtags (resolve a treatment to its hashtag and its aggregate view count), tiktok/hashtags/{id}/videos (recent posts under the hashtag — read view/like counts and dates to gauge whether momentum is rising or flat).

UnifAPI reads public data only — it plans, it never posts. Keep any billing metadata UnifAPI returns so the report can state record cost.

Workflow

  1. Take the treatment menu. Start from the treatments the clinic offers (botox, microneedling, laser hair removal, lip filler, …) and its city. Read .agents/product-marketing.md / .claude/product-marketing.md first if it exists. Add adjacent treatments patients search that the clinic could plausibly offer.
  2. Pull search demand. For each treatment, expand queries with seo/keywords/ideas + seo/keywords/related, score them with seo/keywords/overview, and check the trend with seo/keywords/history. Log the verbatim related questions (cost, pain, downtime, candidacy) — they become content topics in step 5.
  3. Check AI-answer prompts. Run the "best/near-me" prompts through geo/serp; note whether the clinic is cited (is_target), who is, and which prompts have no clear local winner. Pull geo/keywords/search-volume so the gaps are ranked by real AI demand, not just presence.
  4. Read the social signal. Use tiktok/search + tiktok/search/hashtags to find each treatment's hashtag, then tiktok/hashtags/{id}/videos for recency-weighted view/post momentum — a treatment spiking on TikTok before search reflects it is the highest-leverage bet.
  5. Score and rank each treatment with the rubric below, then turn the top treatments into a plan: content topics from the real patient questions, an offer angle that fits seasonality, and the AI prompts worth optimizing for.

Scoring rubric

Score each treatment 0–100 so the menu ranks on one axis. Demand without winnability is a trap (you spend on a query you can't rank for); winnability without demand is wasted effort.

text
score = (0.45 × search) + (0.25 × social) + (0.30 × winnability), each 0–100
FactorHigh (80–100)Mid (40–60)Low (0–20)
searchstrong, steady local volume (overview) + rising trend (history) + rich related questionsmodest volumethin / no data
socialclearly rising TikTok momentum (recent hashtags/{id}/videos view velocity)steady chatterflat or absent
winnabilityclinic near page one or only weak competitors; geo/serp prompt has no cited local winnermixed field, one strong competitora dominant competitor owns search and the local pack

Decision rules:

  • Rising-social + thin-search = pre-empt. A treatment spiking on TikTok with low-but-growing search is the highest-leverage content bet — publish before the volume arrives.
  • Down-rank where the clinic is already losing badly — a dominant competitor owns both search and the local pack; don't burn content budget there.
  • Up-rank an unclaimed GEO prompt — a "best [treatment] in [city]" prompt with no cited local winner is the cheapest citation to win.

Output: Treatment Demand Radar

A ranked treatment table, highest score first, plus a per-treatment plan. State the city, date, and sources checked so the run is reproducible.

markdown
# Treatment Demand Radar — [Clinic], [City] — [date]

| Score | Treatment     | Search (vol/trend) | Social                                              | Winnability | Signal / proving source                         |
| ----- | ------------- | ------------------ | --------------------------------------------------- | ----------- | ----------------------------------------------- |
| 78    | Lip filler    | ~720/mo, rising    | rising (TikTok #lipfiller 2.1B, local clip 90k/3wk) | mid         | clinic on page two; geo/serp prompt unclaimed   |
| 61    | Microneedling | ~480/mo, steady    | rising                                              | high        | "best microneedling [city]" has no cited winner |
| 34    | Botox         | high, flat         | flat                                                | low         | dominant competitor owns search + local pack    |

## Plan — top treatments

For each high-scoring treatment:

- **2–3 content topics** from the verbatim patient questions (cost, pain, downtime, candidacy, before/after, vs-alternative), each with its target query.
- **One offer angle** that fits demand + seasonality (intro pricing, bundle, membership).
- **AI-answer prompts** the clinic should be cited for but isn't (from geo/serp).

## Discarded

One line per treatment checked and set aside, with why.

Guardrails

  • Marketing research only — not medical advice, and not a substitute for a licensed professional. It surfaces demand and content angles; it makes no claims about treatments, safety, or outcomes. Any clinical content the clinic publishes should be reviewed by a licensed professional.
  • Read-only ("eyes, not hands"): it plans; the clinic's own team (and assistant) writes and publishes. It never posts, runs offers, or manages listings on the clinic's behalf.
  • Confirmed vs inferred: label what's read off a source (volume, view count, citation) versus what's deduced (winnability, seasonality call).
  • Demand and social signals are public-data estimates and move quickly — present ranges and dates, weight recent weeks, and treat the result as a dated snapshot, not a guarantee.
  • Every recommended treatment must cite the public source that proves demand. No source, no recommendation — and no fabricated numbers.

Related Skills

  • med-spa-reputation-benchmark (Med Spa Marketing): the reviews / local-pack side for this clinic — the prominence needed to actually rank for the treatments this radar surfaces.
  • content-opportunity-brief (Content Strategy Agent): the general-purpose demand-to-ranked-topics workflow this radar specializes for treatments.
  • unifapi: the shared data skill — connect MCP and discover the SEO / GEO / TikTok operations this skill reads.

Frequently asked questions

What does the Treatment Demand Radar AI skill do?

When a med spa or aesthetics clinic wants to know which treatments are in demand locally and what content or offers to prioritize. Also use on "med spa content ideas," "which treatments are trending," "treatment demand," "what should we promote," "med spa SEO content," "is [treatment] trending on TikTok," or "are we showing up in AI answers for treatments." Reads public data only — marketing research, not medical advice.

Why use Treatment Demand Radar on TypingMind?

Because you install it once and use it with any model. Treatment Demand Radar is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Treatment Demand Radar in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/unifapi-agent/agents/tree/main/skills/med-spa-marketing/treatment-demand-radar. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Treatment Demand Radar?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Treatment Demand Radar?

As many as you like. As long as a model supports skills, you can use Treatment Demand Radar with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Treatment Demand Radar AI skill free?

Yes. It is published on GitHub by unifapi-agent under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇