doctrine

Route and recover authoring flows.

Route the lesson plan handoff.

Route the lesson plan handoff.

Ship bundled agent prompts beside the main skill package.

Ship a multi-file release compendium beside the main skill.

Preserve exact package companion paths and file casing.

Preserve bundled binary assets byte for byte.

Keep the root short and emit deeper docs from prompt files.

Ship emitted docs, bundled agents, and helper files together.

Bind host facts once and reuse them across the whole package.

Produce a typed receipt envelope alongside the substantive output.

Emit a source receipt beside the skill.

Track source files that are not emitted.

Build from a named source root.

Write short, friendly greetings that sound human.

Check layout work against a short reusable checklist.

Ship deterministic greeting helpers beside the main skill.

Ship runtime metadata beside the main skill package.

Ship plugin metadata roots beside the main skill package.

FHIR API development guide for building healthcare endpoints. Use when: (1) Creating FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest), (2) Validating FHIR resources and returning proper HTTP status codes and error responses, (3) Implementing SMART on FHIR authorization and OAuth scopes, (4) Working with Bundles, transactions, batch operations, or search pagination. Covers FHIR R4 resource structures, required fields, value sets (status codes, gender, intent), coding systems (LOINC, SNOMED, RxNorm, ICD-10), and OperationOutcome error handling.

Automate payer review of prior authorization (PA) requests. This skill should be used when users say "Review this PA request", "Process prior authorization for [procedure]", "Assess medical necessity", "Generate PA decision", or when processing clinical documentation for coverage policy validation and authorization decisions.

Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.