@gonzih/skills-dental 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,69 @@
+# skills-dental
+
+Claude Code skill suite for dentists, dental hygienists, and practice managers.
+
+## Install
+
+```bash
+npx @gonzih/skills-dental
+```
+
+Or install globally:
+
+```bash
+npm install -g @gonzih/skills-dental
+```
+
+Then restart Claude Code.
+
+## Skills
+
+### `/treatment-plan-explainer`
+Explain a dental treatment plan in patient-friendly language. Covers what's needed, why, the sequence, cost overview, and what to expect at each appointment.
+
+**Usage:**
+```
+/treatment-plan-explainer D3 #14 needs crown due to cracked cusp, D1 #18-19 composite restorations, periodontal scaling full mouth
+```
+
+---
+
+### `/patient-recall-letter`
+Write a warm recall or reactivation letter for patients overdue for a visit. Friendly tone, benefit-focused copy, and a clear call to action to schedule.
+
+**Usage:**
+```
+/patient-recall-letter Patient: Jane Smith, last seen 18 months ago, due for hygiene + perio follow-up
+```
+
+---
+
+### `/insurance-narrative`
+Write a clinical narrative for a dental insurance pre-authorization. Includes diagnosis, clinical findings, medical necessity argument, and CDT code summary.
+
+**Usage:**
+```
+/insurance-narrative Tooth #30, D2740 crown, recurrent decay under existing restoration, radiographic evidence of decay to DEJ, CDT D2740
+```
+
+---
+
+### `/consent-form-draft`
+Draft an informed consent form for a dental procedure. Covers procedure description, material risks, alternatives (including no treatment), and a patient signature block.
+
+**Usage:**
+```
+/consent-form-draft Surgical extraction #17 impacted mandibular third molar with IV sedation
+```
+
+---
+
+## Notes
+
+- All skill outputs are drafts. Clinical and legal review is required before patient use.
+- Insurance narratives should be reviewed by the treating provider before submission.
+- Consent forms must be reviewed by an attorney licensed in your jurisdiction before clinical use.
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['treatment-plan-explainer', 'patient-recall-letter', 'insurance-narrative', 'consent-form-draft'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,34 @@
+{
+  "name": "@gonzih/skills-dental",
+  "version": "1.0.0",
+  "description": "Claude Code skill suite for dentists, dental hygienists, and practice managers",
+  "type": "module",
+  "main": "install.js",
+  "bin": {
+    "skills-dental": "install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "keywords": [
+    "claude-code",
+    "claude-code-skills",
+    "dental",
+    "dentistry",
+    "treatment-plan",
+    "insurance-narrative",
+    "patient-recall",
+    "informed-consent"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18"
+  },
+  "files": [
+    "skills/",
+    "install.js",
+    "README.md",
+    "LICENSE"
+  ]
+}

package/skills/consent-form-draft/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: consent-form-draft
+description: Drafts an informed consent form for a dental procedure covering procedure description, risks, alternatives, and patient acknowledgment.
+triggers: ["consent form", "informed consent dental", "draft consent", "patient consent form"]
+---
+
+# Consent Form Draft
+
+## What this skill does
+Generates a complete informed consent form for a specified dental procedure. The form covers a plain-language description of the procedure, material risks and complications, available alternatives (including no treatment), and a patient acknowledgment and signature block. Output is suitable as a starting draft for attorney or compliance review before clinical use.
+
+## How to invoke
+/consent-form-draft [procedure name, any specific risks or patient factors to highlight]
+
+## Workflow steps
+
+### Step 1 — Identify the procedure
+Determine the procedure type (e.g., extraction, implant placement, root canal, periodontal surgery, sedation, orthodontic treatment). Identify whether the consent covers a single visit or an ongoing treatment phase.
+
+### Step 2 — Write the procedure description
+Describe the procedure in clear, patient-readable language (6th–8th grade reading level). Explain what will be done, in what area of the mouth, and approximately how long it takes. Avoid unnecessary clinical jargon; define terms when used.
+
+### Step 3 — List risks and potential complications
+Enumerate material risks specific to the procedure: common risks (e.g., soreness, swelling), less common but serious risks (e.g., nerve involvement, sinus communication, implant failure), and risks of anesthesia or sedation if applicable. Include a statement that no guarantee of outcome is made.
+
+### Step 4 — Present alternatives
+List clinically reasonable alternatives to the proposed treatment, including the alternative of no treatment and its likely consequences. The patient must understand they have a choice.
+
+### Step 5 — Acknowledgment and signature block
+Draft a patient acknowledgment section confirming they have read the form, had the opportunity to ask questions, understand the information, and consent voluntarily. Include fields for: patient name (print), patient signature, date, guardian name/signature (if minor), and provider/witness signature.
+
+## Example outputs
+A 400–600 word form with a practice name placeholder header, numbered sections, a risks checklist, an alternatives paragraph, and a formatted signature block. Includes a disclaimer that the form is a template requiring professional and legal review before use.

package/skills/insurance-narrative/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: insurance-narrative
+description: Writes a clinical narrative for a dental insurance pre-authorization including diagnosis, clinical findings, medical necessity, and CDT codes.
+triggers: ["insurance narrative", "pre-auth narrative", "prior authorization dental", "clinical narrative insurance"]
+---
+
+# Insurance Narrative
+
+## What this skill does
+Generates a concise, clinically accurate narrative letter for dental insurance pre-authorization requests. It documents the diagnosis, relevant clinical findings, why the proposed treatment is medically necessary, and references the appropriate CDT codes. Written in the formal, objective language payers expect.
+
+## How to invoke
+/insurance-narrative [procedure, tooth number(s), diagnosis, clinical findings, CDT code(s), any prior treatment history]
+
+## Workflow steps
+
+### Step 1 — Collect clinical data
+Extract or prompt for: patient age/gender (optional), tooth number(s) and surface(s), diagnosis (e.g., recurrent decay, irreversible pulpitis, periodontal disease stage/grade), clinical findings (pocket depths, bleeding on probing, radiographic findings, symptoms), CDT code(s) being submitted, and any prior treatment attempted.
+
+### Step 2 — State the diagnosis clearly
+Open with a direct clinical statement: tooth number, diagnosis, and duration or progression. Reference objective findings (radiographic evidence, probing depths, vitality test results) that support the diagnosis.
+
+### Step 3 — Describe clinical findings
+List relevant objective data in a structured format. Use clinical terminology appropriate for a dental reviewer. Include radiographic findings (periapical pathology, bone loss percentage, caries depth), periodontal measurements, or other supporting data.
+
+### Step 4 — Establish medical necessity
+Explain why the proposed treatment is the appropriate, necessary course of action. Address why less invasive alternatives are not indicated. Reference clinical guidelines where applicable (AAE, AAP, ADA).
+
+### Step 5 — CDT code summary and closing
+List each CDT code with a one-line description and the tooth/surface it applies to. Close with the treating provider's name and credentials placeholder and a request for expedited review if urgent.
+
+## Example outputs
+A formal 250–400 word narrative on practice letterhead (placeholder), structured with labeled sections: Diagnosis, Clinical Findings, Medical Necessity, Proposed Treatment, and Provider Attestation.

package/skills/patient-recall-letter/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: patient-recall-letter
+description: Writes a warm, personalized patient recall or reactivation letter explaining why they're overdue, what the appointment will cover, and making it easy to schedule.
+triggers: ["recall letter", "reactivation letter", "patient overdue letter", "bring patient back"]
+---
+
+# Patient Recall Letter
+
+## What this skill does
+Generates a warm, professional recall or reactivation letter for patients who are overdue for a hygiene visit or have not been seen in an extended period. The letter explains why regular care matters, what the appointment will include, and provides a clear, easy call-to-action to schedule. Tone is friendly and caring — never guilt-inducing.
+
+## How to invoke
+/patient-recall-letter [patient name, time since last visit, any relevant notes e.g. "needs perio follow-up"]
+
+## Workflow steps
+
+### Step 1 — Gather context
+Identify the patient's name, time elapsed since last visit, the type of recall (routine hygiene, perio maintenance, incomplete treatment, post-op check), and any personal details to include (e.g., treatment previously discussed).
+
+### Step 2 — Open with warmth
+Begin with a friendly greeting that acknowledges the patient by name and expresses genuine care. Reference how long it has been without making them feel judged.
+
+### Step 3 — Explain why it matters
+In 2–3 sentences, remind the patient why regular dental visits are important for their specific situation. Keep it benefit-focused ("catch small issues early") rather than fear-based.
+
+### Step 4 — Describe what the visit will include
+Briefly outline what their appointment will cover: exam, cleaning, X-rays if due, any follow-up items. This reduces anxiety by setting clear expectations.
+
+### Step 5 — Clear call to action
+End with a single, frictionless CTA: phone number, online booking link placeholder, or reply-to-this-letter option. Offer flexible scheduling. Close warmly with the practice name and provider signature block.
+
+## Example outputs
+A 200–300 word letter with a subject line, personalized greeting, 3–4 short paragraphs, and a bolded scheduling CTA. Suitable for print mail or email with minimal edits.

package/skills/treatment-plan-explainer/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: treatment-plan-explainer
+description: Explains a dental treatment plan in clear, patient-friendly language covering what's needed, why, sequence, cost overview, and what to expect.
+triggers: ["explain treatment plan", "patient-friendly treatment", "help patient understand treatment"]
+---
+
+# Treatment Plan Explainer
+
+## What this skill does
+Takes a clinical dental treatment plan and rewrites it in plain language a patient can understand. It covers what procedures are recommended, why each is necessary, the recommended sequence, a general cost overview, and what the patient should expect before, during, and after treatment.
+
+## How to invoke
+/treatment-plan-explainer [paste or describe the treatment plan]
+
+## Workflow steps
+
+### Step 1 — Parse the treatment plan
+Identify all procedures listed (CDT codes or plain descriptions), the tooth or area involved, and any urgency notes. Group related procedures (e.g., extractions, restorations, periodontal treatment).
+
+### Step 2 — Translate to patient language
+Rewrite each procedure in everyday English. Avoid jargon; when a clinical term is necessary, define it in parentheses. Explain *why* each procedure is recommended and what happens if it is deferred.
+
+### Step 3 — Sequence and prioritize
+Present procedures in the order they will be performed. Briefly explain why that order matters (e.g., "We address the infection first so your mouth is healthy before placing the crown").
+
+### Step 4 — Cost and insurance overview
+Provide a plain-language summary of estimated costs, insurance coverage concepts (if applicable), and any payment options to mention. Use ranges rather than exact figures unless specifics are provided.
+
+### Step 5 — What to expect
+For each major procedure, add a short "what to expect" note: preparation steps, what happens chairside, recovery time, and any post-op instructions to anticipate.
+
+## Example outputs
+A friendly, section-by-section breakdown titled "Your Personalized Treatment Plan" with headers for each procedure, a numbered sequence, a cost summary box, and a "Questions to ask your dentist" section at the end.