dental-ai-skills
CLAUDE.md7 starsChanged 47 days agoMITView on GitHub
A collection of AI skills (structured markdown protocols) for dental professionals. Each skill is a SKILL.md file that gives AI models (Claude, GPT, etc.) specialized dental knowledge and output formats. The literature skills hand off to each other automatically when the user crosses from search, to appraisal, to numerical audit, to clinical recommendation, to artifact presentation.
In this repository9 other files it gives its agents.
The file
We split this CLAUDE.md into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 44
Do not change the output schema of any skill without updating the README and TESTING.md.
- Distinctive: line 45
Every clinical claim in a skill's instructions must be defensible — no unsourced absolutes.
- Distinctive: line 46
Keep skills focused: one job per skill.
- Distinctive: line 48
Bias-tool fidelity: Use each tool's native judgment categories — do not force AMSTAR 2, Newcastle-Ottawa, QUADAS, JBI into RoB 2's "Low / …
- Distinctive: line 54
Run smoke tests before pushing:
- Distinctive: line 58
Run the relevant manual tests in TESTING.md before pushing changes.
- Very specific: line 59
Keep agents/openai.yaml metadata aligned with each skill's SKILL.md.
- Distinctive: line 60
Prefer minimal diffs and clear commit messages.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dental AI Skills — Project Instructions
What This Repo Is
A collection of AI skills (structured markdown protocols) for dental professionals. Each skill is a SKILL.md file that gives AI models (Claude, GPT, etc.) specialized dental knowledge and output formats.
Skills
| Skill | Folder | Purpose |
| Dental Author Disclosures | dental-author-disclosures/ | Dated, sourced register of author and sponsor relationships. No score, no inference of bias from a name, a talk or a membership. |
| Research Critic | research-critic/ | Single-paper appraisal (PICO, bias tools in native formats, dental-specific red flags, claim-to-evidence map, Study Credibility score). Single-paper, internal-credibility focused. |
| Clinical Evidence Reviewer | clinical-evidence-reviewer/ | Body-of-evidence reviews with runtime-aware retrieval mode, PICO, GRADE certainty per critical outcome, guideline vs expert-consensus distinction, citation policy with uncertainty labels. |
| Dental Evidence Retriever | dental-evidence-retriever/ | Literature-search workflow (PICO → PubMed/Cochrane/guideline-body/registry strategies → retrieval log). Honest about runtime — no fabricated citations. |
| Dental Paper Fetch | dental-paper-fetch/ | Gets the free full-text PDF and figures of a paper by PMID, DOI, PMCID or title. Legal open-access sources only. Reports paywalled papers with their link. No way around paywalls or bot checks. |
| Dental Statistical Forensics | dental-statistical-forensics/ | Deep numerical audit (SD/range, CIs, effect sizes, MCID, individual predictability, unit-of-analysis errors, clustering, multiplicity, missing data, measurement reliability, model appropriateness). |
| Dental Evidence Report Artifact | dental-evidence-report-artifact/ | Converts completed evidence analysis into HTML/PDF-ready reports without adding new scientific claims. |
| Dental Content Creator | dental-content-creator/ | Audience-aware dental content with platform adaptations and no-overclaim guardrails. |
| Dental Image Generator | dental-image-generator/ | AI-generated clinical illustrations and patient visuals via OpenAI's Images API (gpt-image-2.5-sunburst, paid). |
Literature-skill workflow
PMID, DOI or title → dental-paper-fetch → full-text PDF and figures for the skills below
(free legal copies only; paywalled papers reported with their link)
Clinical question → dental-evidence-retriever → clinical-evidence-reviewer
(search strategy + log) (GRADE per outcome, guidelines)
↘ numerical audit → dental-statistical-forensics
Single paper → research-critic → dental-statistical-forensics
(Study Credibility) (numbers, SD/CI/MCID, model validity)
↘ funding and relationships → dental-author-disclosures
(sourced register, no score)
Completed analysis → dental-evidence-report-artifact
(HTML/PDF-ready report, teaching artifact)The literature skills hand off to each other automatically when the user crosses from search, to appraisal, to numerical audit, to clinical recommendation, to artifact presentation.
Rules for Contributing
- Do not change the output schema of any skill without updating the README and TESTING.md.
- Every clinical claim in a skill's instructions must be defensible — no unsourced absolutes.
- Keep skills focused: one job per skill. Literature skills can exceed ~150 lines because the protocols are non-trivial, but they must still pass the "one job" test.
- Citation honesty is non-negotiable. Skills that demand citations must also branch on whether retrieval is actually possible in the runtime. No fabricated DOIs/PMIDs.
- Bias-tool fidelity. Use each tool's native judgment categories — do not force AMSTAR 2, Newcastle-Ottawa, QUADAS, JBI into RoB 2's "Low / Some concerns / High" labels.
- Numerical honesty is non-negotiable. Distinguish statistical significance, effect magnitude, precision, dispersion, measurement error, clinical threshold, and individual predictability. Never claim "predictable" clinical outcomes from a favorable mean alone.
- Validate skill metadata before pushing:
python3 scripts/validate_skills.py - Run smoke tests before pushing:
python3 scripts/smoke_test_repo.py - Run the relevant manual tests in TESTING.md before pushing changes.
- Keep
agents/openai.yamlmetadata aligned with each skill'sSKILL.md. - Prefer minimal diffs and clear commit messages.
- Methodology updates (case definitions, appraisal tools, guideline-body URLs, GRADE handbook revisions) require updating the "Methodology Review Date" block at the bottom of the affected skill.
Francisco Summary (final response format)
- Close finished work with the Francisco Summary block defined in
~/.claude/CLAUDE.md: 🧑⚕️ what this means in plain terms, 🙋 what you need to do, 🤖 what an agent can do without you, 💡 what I propose, and a 🟢/🟡/🔴 flag. It goes first in the final response, not last, and is skipped on quick answers and lookups.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

