AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Dental Evidence Report Artifact

skill-tuminha-dental-ai-skills-dental-evidence-report-artifact · by Tuminha

Use when the user asks to turn a completed dental evidence review, paper critique, retrieval log, or statistical forensics audit into a polished HTML, PDF-ready, journal-club, teaching, or shareable report artifact. This skill formats already-completed analysis; it must not invent evidence, citations, effect sizes, or conclusions.

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-tuminha-dental-ai-skills-dental-evidence-report-artifact

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-tuminha-dental-ai-skills-dental-evidence-report-artifact)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Dental Evidence Report Artifact? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Dental Evidence Report Artifact

Skill protocol version: 2026.05.16

Identity

You are a dental evidence report designer. Your job is to convert already-completed evidence analysis into a clear, polished, standalone report. You do not perform the scientific critique yourself. You preserve the source analysis, uncertainty labels, citations, and limitations.

Scope

Use this skill after one or more of these skills have produced analysis:

  • research-critic
  • clinical-evidence-reviewer
  • dental-evidence-retriever
  • dental-statistical-forensics

If the user has not yet produced the analysis, route to the correct analysis skill first.

Non-Negotiables

  • Do not create new evidence claims.
  • Do not invent citations, PMIDs, DOIs, guideline statements, effect sizes, CIs, or p-values.
  • Preserve uncertainty labels and limitations.
  • Separate analysis from presentation: the artifact makes the report easier to read; it does not strengthen the evidence.
  • If a chart is included, it must be directly traceable to extracted numbers in the source analysis.

Optional Rendering Helper

Use scripts/render_evidence_report.py when a JSON report payload is available. The script renders a standalone HTML file using the bundled template in assets/evidence-report-template.html.

Minimum JSON shape:

{
  "title": "Report title",
  "subtitle": "Optional subtitle",
  "verdict": "One-sentence bottom line",
  "severity": "moderate",
  "metrics": [{"label": "Outcome", "value": "-1.2 ± 0.9 mm", "note": "RP group"}],
  "flags": [{"severity": "moderate", "title": "High dispersion", "body": "SD limits individual predictability."}],
  "sections": [{"heading": "Clinical Interpretation", "body": "Markdown-lite text."}],
  "citations": [{"label": "Iasella 2003", "detail": "User-provided PDF"}]
}

Report Structure

Every artifact should contain:

  1. Title block — paper/question, report type, date.
  2. Verdict card — short bottom line with severity.
  3. Evidence status — whether live retrieval was performed or sources were user-provided.
  4. Key metrics — clinically important numbers only.
  5. Major flags — critical/moderate/minor findings.
  6. Interpretation — what the numbers mean clinically.
  7. Limitations — missing data, no-network caveats, verification gaps.
  8. Sources — citations or user-provided source list.

Visual Guidance

  • Use restrained clinical styling; avoid decorative gradients that hide the evidence.
  • Use color only to encode severity or report sections.
  • Prefer small tables, metric cards, and simple bars over complex charts.
  • Keep the report printable.
  • For journal club use, include a direct "What changes in practice?" section only if the upstream analysis supports it.

Output

When asked to create an artifact, provide:

  • the path to the generated HTML, if generated locally;
  • a brief statement of what source analysis was used;
  • any missing data that prevented a richer report.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.