medirecords-integration

Complete MediRecords FHIR/REST API integration guide for Dr. Sophia AI consultations. Covers two-phase workflow (FHIR Encounter creation + REST notes append), patient search, SOAP note formatting, and troubleshooting. Use when integrating MediRecords API, creating consultations, debugging FHIR/REST endpoints, or saving AI consultations to patient records.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%Weight 40%Scale 1-5

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

Highly actionable, well-structured content with excellent progressive disclosure and copy-paste code. It loses points for missing validation checkpoints in the consultation-creation workflow and for some verbose, date-stamped sections that add token cost without durable value.

Suggestions

Add explicit validation checkpoints to the Quick Start workflow (e.g., check each response status, verify encounterId is present before Phase 2, retry on transient errors) so the destructive write operation has a feedback loop.

Move or remove the 'Verified Test Results' section and hard-coded date ('October 22, 2025') — time-sensitive verification artifacts add tokens and decay; keep only durable operational facts.

Trim the duplicated status/error information between 'What Works vs What Doesn't' and 'Common Issues Quick Reference' into a single table to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes FHIR/API knowledge, but the 'What Works vs What Doesn't' and 'Verified Test Results' sections plus hard-coded test dates ('October 22, 2025') add padding and time-sensitive noise not placed in a deprecated section.	3 / 5
Actionability	Copy-paste ready JavaScript with concrete endpoints, headers, and request bodies, plus a specific HTTP error cause/fix table — fully executable and covers the common cases.	5 / 5
Workflow Clarity	The two-phase process is clearly sequenced with numbered Quick Start steps, but the workflow lacks validation/verification checkpoints (response checking, retry-on-error) for a write operation creating medical records, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	A clear overview with one-level-deep, well-signaled references to real bundle files (api-credentials.md, fhir-schemas.md, troubleshooting-guide.md) and a test script, matching the level-5 anchor.	5 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 strong, specific description that clearly conveys both capabilities and natural trigger conditions with a distinct niche. It only loses a point on trigger-term breadth (missing synonyms/extensions).

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'two-phase workflow (FHIR Encounter creation + REST notes append), patient search, SOAP note formatting, and troubleshooting' — with comprehensive coverage, matching the level-5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' (complete integration guide covering the two-phase workflow) and 'when' ('Use when integrating MediRecords API, creating consultations...'), matching the level-5 anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'integrating MediRecords API, creating consultations, debugging FHIR/REST endpoints' cover the domain well but lack synonyms and file extensions, falling just below level 5.	4 / 5
Distinctiveness Conflict Risk	The 'MediRecords', 'FHIR/REST API', and 'Dr. Sophia AI consultations' niche is distinct with clear triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: skill-builder-package/examples/medirecords-integration/SKILL.md
Commit: 93ed392

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.