openevidence-pack

Plugin openevidence-pack from marketplace claude-code-plugins-plus in jeremylongshore/tons-of-skills-marketplace. Commands read from the repo's manifest — 6 days ago.

Skills (24)

• openevidence-ci-integration

  Build a repeatable acceptance gate for an OpenEvidence practice rollout without inventing an API or automating clinical judgment. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence ci integration", "OpenEvidence rollout", or a matching workflow request.

• openevidence-common-errors

  Diagnose weak, incomplete, or poorly grounded OpenEvidence results using prompt, model, citation, and workflow checks. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence common errors", "OpenEvidence troubleshooting", or a matching workflow request.

• openevidence-core-workflow-a

  Structure and review an OpenEvidence clinical consult while preserving clinician accountability and evidence traceability. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow a", "OpenEvidence clinical-consult", or a matching workflow request.

• openevidence-core-workflow-b

  Audit an OpenEvidence answer’s EvidenceGrade, citations, and applicability before it informs clinical work. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence core workflow b", "OpenEvidence citations", or a matching workflow request.

• openevidence-cost-tuning

  Evaluate OpenEvidence adoption value and access burden without inventing prices, quotas, or usage telemetry. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence cost tuning", "OpenEvidence value", or a matching workflow request.

• openevidence-data-handling

  Design a minimum-necessary OpenEvidence data-handling workflow for questions, Visits recordings, notes, and exports. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence data handling", "OpenEvidence privacy", or a matching workflow request.

• openevidence-debug-bundle

  Assemble a reproducible, privacy-safe OpenEvidence support packet for product failures without exposing credentials or patient data. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence debug bundle", "OpenEvidence support", or a matching workflow request.

• openevidence-deploy-integration

  Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence deploy integration", "OpenEvidence deployment", or a matching workflow request.

• openevidence-enterprise-rbac

  Define and verify institutional OpenEvidence access governance without inventing RBAC, SCIM, or administration APIs. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence enterprise rbac", "OpenEvidence access", or a matching workflow request.

• openevidence-hello-world

  Complete a smallest-safe OpenEvidence onboarding proof through the supported product, with no patient data or invented API key. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence hello world", "OpenEvidence onboarding", or a matching workflow request.

• openevidence-incident-runbook

  Triage an OpenEvidence safety, privacy, access, recording, or evidence incident with containment and accountable escalation. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence incident runbook", "OpenEvidence incident-response", or a matching workflow request

• openevidence-install-auth

  Establish authorized OpenEvidence account access through official registration and institutional pathways. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence install auth", "OpenEvidence authentication", or a matching workflow request.

• openevidence-local-dev-loop

  Evaluate OpenEvidence product workflows safely with synthetic cases before any clinical rollout. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence local dev loop", "OpenEvidence evaluation", or a matching workflow request.

• openevidence-migration-deep-dive

  Migrate saved Deep Consult practices to the current Snow model workflow while revalidating output and governance. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence migration deep dive", "OpenEvidence migration", or a matching workflow request.

• openevidence-multi-env-setup

  Verify a governed OpenEvidence workflow across supported web and mobile surfaces without fictitious dev or staging hosts. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence multi env setup", "OpenEvidence web", or a matching workflow request.

• openevidence-observability

  Monitor OpenEvidence workflow quality, evidence traceability, adoption, and safety signals using approved local evidence. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence observability", "OpenEvidence quality", or a matching workflow request.

• openevidence-performance-tuning

  Improve OpenEvidence question quality and reviewer efficiency through controlled prompt refinement. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence performance tuning", "OpenEvidence prompting", or a matching workflow request.

• openevidence-prod-checklist

  Gate an OpenEvidence clinical workflow for go-live across access, privacy, safety, training, support, and rollback. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence prod checklist", "OpenEvidence go-live", or a matching workflow request.

• openevidence-rate-limits

  Triage OpenEvidence access, latency, or capacity symptoms without asserting undocumented quotas or retry contracts. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence rate limits", "OpenEvidence capacity", or a matching workflow request.

• openevidence-reference-architecture

  Design a governed operating model around OpenEvidence’s supported product workflows and clinician review. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence reference architecture", "OpenEvidence architecture", or a matching workflow request.

• openevidence-sdk-patterns

  Select supported OpenEvidence interaction and prompting patterns while preventing use of nonexistent public SDKs. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence sdk patterns", "OpenEvidence patterns", or a matching workflow request.

• openevidence-security-basics

  Assess OpenEvidence security claims and institution-specific controls using current first-party evidence and accountable review. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence security basics", "OpenEvidence security", or a matching workflow request.

• openevidence-upgrade-migration

  Adopt a documented OpenEvidence feature or model change through inventory, pilot, review, training, and rollback. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence upgrade migration", "OpenEvidence change-management", or a matching workflow request.

• openevidence-webhooks-events

  Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence webhooks events", "OpenEvidence handoffs", or a matching workflow request.

Similar plugins