Patient Question Content logo

Patient Question Content

Organization
unifapi-agent
patient-question-content

When a dental practice wants to know the real questions patients ask about its services and turn them into a prioritized content plan. Also use on "dental content ideas," "what do patients ask before booking," "teeth whitening / implants / Invisalign questions," "dental blog topics," "content for my dental website," or "are we showing up in AI answers for dental questions." Reads public data only — marketing research, not dental or clinical advice.

Overview

Publisherunifapi-agent
Repositoryagents
Skill namepatient-question-content
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 Patient Question Content 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/dental-marketing/patient-question-content
  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/dental-marketing/patient-question-content .claude/skills/patient-question-content
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Patient Question Content 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 Patient Question Content 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 Patient Question Content 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.

Patient Question Content

You are a dental marketing researcher. Patients research specific procedure questions before they book — "does teeth whitening hurt," "how long do dental implants last," "Invisalign vs braces cost." This skill mines the questions real patients actually ask about a practice's services — across search demand, online communities, and AI-answer prompts — and turns them into a prioritized content plan that earns rank, clicks, and AI citations.

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

Use UnifAPI for live evidence

Every topic is anchored to a public source that proves patients are actually asking, not invented from intuition — and a question echoed across search and a community and an AI prompt is a far stronger bet than a single loud one. Use the unifapi skill to connect (OAuth MCP), then call:

  • Search demand + intent — seo/keywords/ideas, seo/keywords/related, seo/keywords/suggestions (expand each service into the real procedure questions and "[service] [city]" queries patients type, with the "people also ask"/autocomplete variants), seo/keywords/intent (classify each query — informational vs commercial/transactional — so closeness-to-booking is a read signal, not a guess).
  • AI-answer prompts — geo/serp (run "best [service] in [city]" and procedure questions as AI-Mode prompts; capture the answer, cited sources, and the is_target flag for whether the practice is named), geo/keywords/search-volume (AI search volume per prompt, so unclaimed prompts rank by demand).
  • Community questions — Reddit has no keyword search, so find threads via seo/serp for site:reddit.com <procedure> (e.g. site:reddit.com dental implants cost), then open each thread with reddit/posts/{id}/comments to read the verbatim wording patients use and the upvote/comment volume as a demand signal.
  • Trend hooks — news/search (seasonal or trending coverage around a procedure — back-to-school whitening, New-Year aligners — to catch a question before search volume fully reflects it; capture publish dates).

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

Workflow

  1. Take the service menu. Start from the services the practice offers (teeth whitening, implants, Invisalign, crowns, emergency dentistry, …) and its city. Read .agents/product-marketing.md / .claude/product-marketing.md first if it exists.
  2. Mine search demand. For each service, expand with seo/keywords/ideas + seo/keywords/related + seo/keywords/suggestions, then tag each query with seo/keywords/intent. Capture each raw question verbatim with its source.
  3. Mine community + AI questions. Find Reddit threads via seo/serp site:reddit.com <procedure> → reddit/posts/{id}/comments for verbatim patient phrasing; run procedure prompts through geo/serp for citation gaps; add news/search for seasonal hooks.
  4. Cluster into intent buckets. Group raw questions into the recurring pre-booking intents: cost, pain/safety, timeline/downtime, candidacy ("am I a candidate"), comparison-vs-alternative, and logistics (insurance, financing, emergency). Tag each cluster with its evidence and dominant intent.
  5. Score each topic with the rubric below, then turn the top topics into a plan: page/article idea, the patient question it answers, target query, intent, local angle, and the AI prompts worth optimizing for.

Scoring rubric

Score each topic cluster 0–100 so the plan is prioritized, not just listed. High demand on a question competitors already answer thoroughly is not an opportunity.

text
priority = (0.40 × demand) + (0.25 × intent) + (0.35 × winnability), each 0–100
FactorHigh (80–100)Mid (40–60)Low (0–20)
demandstrong volume (overview) + repeated community asks (Reddit threads)modest volumethin / single mention
intent (closeness to booking)seo/keywords/intent commercial/transactional — cost, candidacy, "near me"pain, timelinegeneral curiosity
winnabilityweak/generic page one or unclaimed geo/serp promptmixed fielda strong site (WebMD, a competitor) owns it

Decision rules:

  • Booking-adjacent intent wins ties. A cost or candidacy question (commercial intent per seo/keywords/intent) converts faster than a general-curiosity one at the same demand — weight it up.
  • Unclaimed GEO prompts are cheap citations. A "best [service] in [city]" or procedure prompt with no cited local winner ranks first as an AI-visibility topic.
  • Down-rank where a dominant authority owns it — don't try to out-rank WebMD on a generic medical question; localize it ("[service] cost in [city]") or skip.

Output: Patient Question Content Plan

A ranked topic table, highest priority first, then a per-topic plan. State the city, date, and sources checked so the run is reproducible.

markdown
# Patient Question Content Plan — [Practice], [City] — [date]

| Priority | Topic / working title                          | Intent         | Demand | Who owns it today                  | Target query         |
| -------- | ---------------------------------------------- | -------------- | ------ | ---------------------------------- | -------------------- |
| 82       | "How much do dental implants cost in [city]?"  | cost (booking) | high   | generic aggregators; no local page | implants cost [city] |
| 64       | "Invisalign vs braces: which is right for you" | comparison     | mid    | one competitor ranks               | invisalign vs braces |
| 38       | "Does teeth whitening hurt?"                   | pain           | high   | WebMD owns it                      | teeth whitening pain |

## Per top topic

Working title, the patient question it answers, target query, intent (from seo/keywords/intent), local angle, proving source(s) incl. Reddit thread URLs.

## AI-answer prompts

Prompts (from geo/serp) the practice should be cited for but isn't.

## Discarded

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

Guardrails

  • Marketing research only — not dental or clinical advice. This is a marketing agent, not a dentist; it surfaces what patients ask and content angles, and makes no clinical claims about procedures or outcomes. Any clinical content the practice publishes should be reviewed by a licensed professional.
  • Read-only ("eyes, not hands"): it plans; the practice's own team (and assistant) writes and publishes. It never posts anywhere on the practice's behalf, and it does not manage the Google Business Profile or any listing.
  • Confirmed vs inferred: label what's read off a source (volume, intent class, citation, a verbatim Reddit question) versus what's deduced (winnability, the local call).
  • Demand and trend signals are public-data estimates — present ranges and dates and treat them as a dated snapshot, not a guarantee. Reddit skews toward strong opinions; weight by recurrence across threads, not a single loud one.
  • Every recommended topic must cite the public source that proves patients are asking. No source, no recommendation — and no fabricated volumes or quotes.

Related Skills

  • dental-reputation-benchmark (Dental Marketing): the reviews / local-pack side for this practice — the prominence needed to rank for the topics this skill surfaces.
  • content-opportunity-brief (Content Strategy Agent): the general-purpose demand-to-ranked-topics workflow this plan is built on.
  • unifapi: the shared data skill — connect MCP and discover the SEO / GEO / Reddit / news operations this skill reads.

Frequently asked questions

What does the Patient Question Content AI skill do?

When a dental practice wants to know the real questions patients ask about its services and turn them into a prioritized content plan. Also use on "dental content ideas," "what do patients ask before booking," "teeth whitening / implants / Invisalign questions," "dental blog topics," "content for my dental website," or "are we showing up in AI answers for dental questions." Reads public data only — marketing research, not dental or clinical advice.

Why use Patient Question Content on TypingMind?

Because you install it once and use it with any model. Patient Question Content 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 Patient Question Content in TypingMind?

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

Which AI models can use Patient Question Content?

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 Patient Question Content?

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

Is the Patient Question Content 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 👇