CtrlK
BlogDocsLog inGet started
Tessl Logo

dentist-agent

Emergency dental assistant (Dr. Molar) for triage, first aid, and severity classification of broken/chipped/cracked teeth, delivered over web, Slack, or Telegram. Use for non-diagnostic dental guidance only.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-organized conversational triage skill with concrete assessment prompts and safety guardrails, but it names capabilities (first-aid steps, pain relief, severity routing) without providing the actual procedural detail or an explicitly sequenced triage workflow.

Suggestions

Spell out the actual first-aid instructions and pain-management specifics instead of listing them only as capability bullets, so the guidance is directly actionable.

Add an explicitly sequenced triage workflow (assess symptoms -> classify severity -> route to ER vs. next-day dentist -> give first aid) with the decision criteria for each severity tier.

Define how the named tools (assess_emergency, pain_relief) are invoked or what they return, so Claude can use them concretely rather than treating them as labels.

DimensionReasoningScore

Conciseness

A lean ~38-line body with no concept-explanation bloat (it does not explain what teeth or dental procedures are); sections are short and each broadly earns its place, assuming Claude's competence.

3 / 3

Actionability

The assessment checklist ('ask about: What happened, Pain level 1-10, loose/displaced, bleeding, broken piece') and guardrails are concrete, but the actual first-aid procedures, pain-management specifics, and severity-classification logic are only listed as capability bullets rather than written out — missing key details.

2 / 3

Workflow Clarity

Assessment questions are listed and there is an ER-redirect checkpoint in the guardrails, but the assess -> classify severity -> route (ER vs next-day dentist) -> first-aid triage flow is not explicitly sequenced with validation checkpoints, leaving the routing decision criteria implicit.

2 / 3

Progressive Disclosure

Under 50 lines with no external references needed and no bundle files present; content is well-organized into clearly labeled sections (Skills, Tools, Channels, Guardrails), meeting the simple-skill allowance for a top score.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, third-person description that names concrete capabilities, includes natural trigger terms, and provides an explicit use-when clause with a clear, non-conflicting niche. It avoids vague fluff and over-claims while staying brief.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'triage, first aid, and severity classification of broken/chipped/cracked teeth' — matching the anchor for several specific concrete actions rather than a single domain mention.

3 / 3

Completeness

Explicitly answers what it does (triage, first aid, severity classification) and when to use it via the 'Use for non-diagnostic dental guidance only' clause, satisfying the 'Use when...' equivalent trigger requirement.

3 / 3

Trigger Term Quality

Natural user-facing terms like 'broken/chipped/cracked teeth', 'dental', 'emergency', and 'first aid' give good coverage of what a patient would actually say; not merely technical jargon.

3 / 3

Distinctiveness Conflict Risk

The dental-emergency niche with concrete tooth-injury triggers is clearly distinct and unlikely to fire for unrelated skills; no overlap risk with generic helpers.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Atmosphere/atmosphere
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.