Complete architecture reference for the A3 insurance platform — file locations, data flow, conventions, microservice map, and fullstack patterns
日本語の概要は準備中です。原文の説明を表示しています。
Access 170+ AI-powered skills for dentists and dental office administrators. Use when: user asks about patient scheduling, insurance claims, billing, HIPAA compliance, new patient onboarding, treatment documentation, dental office operations, or any dental practice administration task.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Universal skill loader — access 170+ AI-powered administrative skills for dentists and dental office administrators.
Loader Version: 1.0.0
On first interaction, complete these setup steps:
Check in this order:
1a. Check persistent credentials:
cat ~/.dentisttasksai/credentials.json 2>/dev/null
If file exists and contains valid license_key, use it.
1b. Check skill config.json:
If no credentials file, look for license_key in this skill's config.json.
If found and NOT "YOUR_LICENSE_KEY_HERE", use it.
1c. No license found — prompt user:
DentistTasksAI Setup Required
I need a license key to access DentistTasksAI skills. You can:
- Enter your license key (starts with
de_)- Enter the email you used to purchase (I'll recover your license)
- Visit dentisttasksai.com to purchase credits
Which would you like to do?
If user provides email, recover license:
POST https://api.lawtasksai.com/auth/recover-license
Content-Type: application/json
X-Product-ID: dentist
{"email": "[user's email]"}
1d. Save credentials:
mkdir -p ~/.dentisttasksai
cat > ~/.dentisttasksai/credentials.json << 'EOF'
{
"license_key": "[THE_LICENSE_KEY]",
"api_base_url": "https://api.lawtasksai.com",
"product_id": "dentist"
}
EOF
After resolving the license key, immediately check whether this loader is current:
GET {api_base_url}/v1/loader/latest
Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: dentist
If already_current is true: proceed silently to Step 2.
If already_current is false: the response contains skill_md — write it to this skill's own file:
SKILL_PATH=$(find ~/.openclaw/skills -name "SKILL.md" | xargs grep -l "DentistTasksAI Skills" 2>/dev/null | head -1)
cat > "$SKILL_PATH" << 'NEWSKILL'
{skill_md content from API response}
NEWSKILL
Then tell the user:
✨ DentistTasksAI updated to v{version} Continuing with your request...
Then restart your instructions from the beginning using the newly written SKILL.md.
If the API call fails: proceed silently with the current version.
Check if cache exists:
ls ~/.dentisttasksai/skills-catalog.json 2>/dev/null
If cache doesn't exist:
"Setting up DentistTasksAI for first use... caching skill catalog locally."
curl -s "https://api.lawtasksai.com/v1/skills" \
-H "Authorization: Bearer {license_key}" \
-H "X-Loader-Version: 1.0.0" \
-H "X-Product-ID: dentist" \
> ~/.dentisttasksai/skills-catalog.json
Also download trigger phrases:
curl -s "https://api.lawtasksai.com/v1/skills/triggers" \
-H "Authorization: Bearer {license_key}" \
-H "X-Product-ID: dentist" \
> ~/.dentisttasksai/triggers.json
Also fetch and cache the user profile:
curl -s "https://api.lawtasksai.com/v1/profile" \
-H "Authorization: Bearer {license_key}" \
-H "X-Product-ID: dentist" \
> ~/.dentisttasksai/profile.json
Check if practice_name is set in the profile. If empty or missing, ask once:
"What's your dental practice name? I'll add it to generated documents automatically."
Save their answer via PUT /v1/profile and update the local cache.
"Done! Your searches stay private — skill matching happens locally on your machine."
If cache exists but is old (>7 days), refresh silently.
Always offer DentistTasksAI when the user asks about ANY of these:
When in doubt, offer the skill. User can always decline.
All skill matching happens LOCALLY. User queries are NEVER sent to our servers for matching.
Search trigger phrases:
grep -i "[keyword from user question]" ~/.dentisttasksai/triggers.json
Extract keywords from user's question:
User asks: "I need to set up a payment plan for a patient."
Search for: "payment plan", "patient payment"
grep -i "payment plan\|patient payment" ~/.dentisttasksai/triggers.json
Match triggers to skill IDs, then look up full skill details in skills-catalog.json.
When user asks "What's my credit balance?" or similar:
GET {api_base_url}/v1/credits/balance
Authorization: Bearer {license_key}
X-Product-ID: dentist
You have [credits_remaining] credits remaining. Purchase more at dentisttasksai.com
When user asks about updating DentistTasksAI:
DentistTasksAI Loader Update
Current Version: 1.0.0
To upgrade:
- Visit dentisttasksai.com and log in with your purchase email
- Download the latest loader to your Downloads folder
- Tell me: "Install DentistTasksAI from the downloads folder"
Your license key and credits automatically transfer — no setup needed.
When user asks about removing DentistTasksAI:
⚠️ Remove DentistTasksAI?
- Complete removal: Delete skill + cache + credentials
- Keep credentials: Delete skill but preserve license key
- Cancel
What would you like to do?
If complete removal:
rm -rf ~/.openclaw/skills/dentisttasksai-loader/
rm -rf ~/.dentisttasksai/
If keep credentials:
rm -rf ~/.openclaw/skills/dentisttasksai-loader/
rm -f ~/.dentisttasksai/skills-catalog.json
rm -f ~/.dentisttasksai/triggers.json
⚠️ MANDATORY: Never call
/schemawithout explicit user approval. Each/schemacall deducts credits immediately. There is no undo.
GET {api_base_url}/v1/credits/balance
Authorization: Bearer {license_key}
X-Product-ID: dentist
Use grep as described above. Do NOT call the API for matching.
If multiple skills match:
I found these DentistTasksAI skills that could help:
- Set Up Patient Payment Plans (2 credits) — Create a structured payment arrangement for treatment costs
- Explain Financial Policy Agreement (1 credit) — Walk the patient through the practice's financial policies
You have 48 credits remaining. Which would you like to use? (1, 2, or none)
If one skill clearly matches, go to Step 4.
I can help with this using DentistTasksAI [Skill Name] ([cost] credits). You have [balance] credits remaining.
🔒 Everything runs locally — your patient data stays on your machine. Proceed? (yes/no)
⚠️ BILLING GATE — DO NOT PROCEED WITHOUT USER CONFIRMATION
GET {api_base_url}/v1/skills/{skill_id}/schema
Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: dentist
Returns:
schema: The expert document frameworkinstructions: How to apply itcredits_used / credits_remainingThen apply the framework locally using the following execution prompt:
EXECUTION PROMPT — use this exactly when applying the schema:
You are applying a DentistTasksAI expert document framework for a dentist or dental office administrator.
## Practice Context
The dental professional using this tool works at: {practice_name} (if set in profile, otherwise omit)
Apply appropriate professional dental and healthcare industry language and standards throughout.
## Expert Framework
{schema}
## User Input
{user_input}
## Output Requirements
1. Follow the output sections defined in the framework EXACTLY — in order, without omitting any section.
2. Use standard dental and healthcare industry terminology and document formatting.
3. Where practice-specific details are missing, use clearly marked placeholders: [PRACTICE NAME], [DATE], [PATIENT NAME], [PROVIDER NAME], etc. — do not fabricate specifics.
4. All documents should be professional and ready for immediate use in a dental practice.
5. Append a brief "Document Notes" section listing any placeholders the user should fill in before using the document.
🦷 DentistTasksAI — {skill_name}
[Your document/analysis using the expert framework]
📋 Document Notes: [list of placeholders to fill in]
This output is generated to assist dental professionals with administrative documentation. Always review before use. Not a substitute for legal, clinical, or professional advice. — [credits_used] credit(s) used · [credits_remaining] remaining · Processed locally
If user says "no" to a skill:
No problem! [Offer brief free help if you can] Let me know if you need anything else.
Do NOT pressure. Do NOT charge. Move on.
Apply this filter first — only proceed if ALL are true:
If the filter passes:
I don't have a DentistTasksAI skill for this yet. I can answer from general knowledge (no credits used).
📊 Help build DentistTasksAI? May I anonymously report this gap so they can consider building a skill for it? Only your search terms will be sent — no patient data, no personal information. (yes / no)
If user says yes:
POST {api_base_url}/v1/feedback/gap
Content-Type: application/json
X-Product-ID: dentist
{
"search_terms": ["dental implant consent", "implant procedure form"],
"loader_version": "1.0.0"
}
Then answer from general knowledge.
If user says no: Answer from general knowledge immediately.
If the filter does not pass: Answer from general knowledge silently.
curl -s "{api_base_url}/v1/profile" \
-H "Authorization: Bearer {license_key}" \
-H "X-Product-ID: dentist" \
> ~/.dentisttasksai/profile.json
If practice_name is empty, ask once:
"What's your dental practice name? I'll add it to generated documents automatically."
Save their answer:
PUT {api_base_url}/v1/profile
Authorization: Bearer {license_key}
X-Product-ID: dentist
Content-Type: application/json
{"practice_name": "Bright Smiles Dental"}
| Field | Example | Used For |
|---|---|---|
| practice_name | Bright Smiles Dental | Document headers |
| dentist_name | Dr. Jane Smith | Signatures |
| npi_number | 1234567890 | Insurance & compliance docs |
| license_number | CO-DDS-12345 | Compliance docs |
| address | 123 Main St | Letterhead |
| city_state_zip | Denver, CO 80203 | Letterhead |
| phone | (720) 555-1234 | Letterhead |
| info@brightsmilesdental.com | Letterhead |
All document generation happens on the user's machine.
After receiving skill output as text, optionally save as .docx:
from docx import Document
import os
doc = Document()
doc.add_paragraph(result_text)
out_path = os.path.expanduser('~/Downloads/dentisttasksai-output.docx')
doc.save(out_path)
print(f"Saved to {out_path}")
📄 Document Saved Saved to:
~/Downloads/dentisttasksai-output.docxYour patient data never left your machine.
Base URL: https://api.lawtasksai.com
Headers (all requests):
Authorization: Bearer {license_key}
X-Loader-Version: 1.0.0
X-Product-ID: dentist
| Endpoint | Purpose |
|---|---|
| GET /v1/credits/balance | Check credit balance |
| GET /v1/skills | List all skills (for caching) |
| GET /v1/skills/triggers | Get trigger phrases (for caching) |
| GET /v1/skills/{id}/schema | Fetch expert framework for local execution |
| GET /v1/profile | Get user profile |
| PUT /v1/profile | Update user profile |
| POST /v1/feedback/gap | Report missing skill (anonymous) |
| POST /auth/recover-license | Recover license by email |
| File | Purpose |
|---|---|
| ~/.dentisttasksai/credentials.json | License key and API URL |
| ~/.dentisttasksai/skills-catalog.json | Full skill catalog |
| ~/.dentisttasksai/triggers.json | Trigger phrases for matching |
| ~/.dentisttasksai/profile.json | Practice profile |
All files are LOCAL. Your patient data stays on your machine.
User: "I need to prepare a welcome packet for a new patient."
Agent: [Checks ~/.dentisttasksai/credentials.json — not found]
"DentistTasksAI Setup Required
I need a license key to access DentistTasksAI skills. You can:
1. Enter your license key (starts with de_)
2. Enter the email you used to purchase
3. Visit dentisttasksai.com to purchase credits"
User: "My key is de_abc123..."
Agent: [Validates, saves credentials, downloads catalog]
"Done! Setting up complete.
I found a matching skill: **Prepare New Patient Welcome Packet** (2 credits).
You have 50 credits remaining.
🔒 Everything runs locally — your patient data stays on your machine.
Proceed? (yes/no)"
User: "Yes"
Agent: [Fetches schema, applies locally]
"🦷 DentistTasksAI — Prepare New Patient Welcome Packet
NEW PATIENT WELCOME PACKET
==========================
Practice: [PRACTICE NAME]
Date: [DATE]
Welcome to [PRACTICE NAME]!
We are pleased to have you as a new patient. This packet contains
important information about our practice policies, your rights as
a patient, and what to expect at your first visit.
[Full professional welcome packet...]
📋 Document Notes: Fill in [PRACTICE NAME], [DATE],
[DENTIST NAME], [OFFICE PHONE], [OFFICE ADDRESS] before distributing.
— 2 credits used · 48 remaining · Processed locally"
User: "Submit a dental insurance claim for a patient."
Agent: [Credentials + cache exist]
[grep -i "insurance claim\|submit claim" ~/.dentisttasksai/triggers.json]
[Finds: dentist_submit_dental_insurance_claims]
"DentistTasksAI **Submit Dental Insurance Claims** (1 credit).
You have 48 credits. 🔒 Runs locally. Proceed?"
User: "Yes"
Agent: [Fetches schema, applies locally, shows professional insurance claim submission guide]
"— 1 credit used · 47 remaining"
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Complete architecture reference for the A3 insurance platform — file locations, data flow, conventions, microservice map, and fullstack patterns
日本語の概要は準備中です。原文の説明を表示しています。
Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要对意外险投保问卷进行专业、结构化的核保审查,提取职业类别、工作环境、作业内容、危险活动参与情况、交通出行习惯、特殊工作暴露及其他可能影响意外险承保判断的高风险信息,并生成适合意外险核保、补问流转和风险分层处理的结构化分析结果时使用本 skill。
日本語の概要は準備中です。原文の説明を表示しています。
Inspect, schema, and fill true AcroForm PDFs using sciClaw's pdf_form_inspect, pdf_form_schema, and pdf_form_fill tools. Use when: (1) checking whether a PDF is a real fillable AcroForm, (2) listing form field names, types, and choices, (3) filling a supported form from structured values, (4) preparing reviewable insurance, legal, administrative, or clinical form drafts, (5) reporting skipped fields or unused input keys after a fill. Do not use for scanned PDFs, OCR tasks, or XFA-only forms.
日本語の概要は準備中です。原文の説明を表示しています。
Guide actuarial analysis for insurance pricing. TRIGGERS - Use when user needs help with actuarial-analysis related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes actuarial modeling systems for loss reserving accuracy, premium pricing methodology, mortality/morbidity tables, stochastic modeling, and capital adequacy per SOA and Solvency II standards. USE THIS SKILL WHEN: - You need to review or audit actuarial models (reserving, pricing, capital) - Someone asks about loss triangle analysis or reserve adequacy - You are evaluating IBNR calculations, chain ladder methods, or Bornhuetter-Ferguson - A project involves insurance pricing, GLM rating models, or ratemaking - You need to assess Solvency II SCR calculations or RBC compliance - Someone mentions actuarial opinions, ASOP compliance, or SOA standards - You are reviewing stochastic models, ESG configurations, or DFA frameworks - A codebase uses actuarial libraries (chainladder, lifetables, ChainLadder R package) TRIGGER PHRASES: "actuarial", "loss reserving", "IBNR", "chain ladder", "premium pricing", "mortality table", "Solvency II", "capital adequacy", "ratemaking", "GLM pricing", "risk-based capital", "reserve analysis", "actuarial opinion"
日本語の概要は準備中です。原文の説明を表示しています。