openevidence-hello-world
Provides starter templates and code patterns for querying OpenEvidence clinical data.
Install
mkdir -p .claude/skills/openevidence-hello-world && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2750" && unzip -o skill.zip -d .claude/skills/openevidence-hello-world && rm skill.zipInstalls to .claude/skills/openevidence-hello-world
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a minimal working OpenEvidence example.Key capabilities
- →Perform clinical queries with specified context and evidence level
- →Check drug interactions for multiple medications and patient contexts
- →Search for medical guidelines based on condition, source, and year
How it works
This skill demonstrates core OpenEvidence API functionality by executing clinical queries, checking drug interactions, and looking up medical guidelines using provided code snippets.
Inputs & outputs
When to use openevidence-hello-world
- →Test clinical query connectivity
- →Check drug-to-drug interactions
- →Retrieve medical guideline citations
- →Validate API authentication
About this skill
OpenEvidence Verified-User Onboarding
Overview
Verify account access and the Ask evidence-review loop using a synthetic clinical question. Keep inputs minimal, separate observed facts from assumptions, and leave consequential decisions with the named accountable owner.
Prerequisites
- A clearly bounded workflow, accountable clinical owner, and organizational policy
- Current first-party OpenEvidence documentation and applicable institution agreements
- Synthetic or properly authorized minimum-necessary data
Tool Discipline
Use Read, Glob, and Grep to inspect supplied policies, plans, and evidence. Use WebFetch only for current first-party OpenEvidence documentation. Use Write or Edit only when the user requests a named deliverable with an approved destination. Never expose credentials, PHI, recordings, or unrestricted environment output.
Current Contract
- Full service access requires account registration and may include professional verification.
- The supported onboarding surface is the website or mobile application; no public API-key flow is documented.
- The first proof must avoid patient data and clinical action.
Authentication
Use only the official OpenEvidence web/mobile sign-in or an institution-approved access path. Do not invent API keys, OAuth clients, SDK credentials, service accounts, or private endpoints. Never ask a user to reveal a password, session token, cookie, or recovery code.
Instructions
- Confirm the intended user, approved device, organizational policy, and whether an institutional account path applies.
- Register or sign in through the official product; never request or fabricate an API key.
- Submit a synthetic, non-urgent clinical question containing no identifiable patient facts.
- Confirm the answer displays sources and, when present, EvidenceGrade; open at least one citation.
- Record surface, timestamp, result, and any access limitation without copying account secrets.
- End with the product unmodified except for the authorized test history and identify the clinical-review training needed next.
Approval Boundaries
Do not create or share accounts; change access, roles, agreements, consent, retention, or security settings; enter PHI; record a conversation; copy content into another system; contact a patient; make a diagnosis or treatment decision; submit billing; transmit a support packet; run a production pilot; or represent vendor capabilities without explicit approval from the accountable owner. A qualified professional remains responsible for clinical decisions.
Output
Return scope, current first-party evidence and date, data classification, workflow or findings, citations reviewed, assumptions rejected, clinical and governance owners, approval state, unresolved risk, and the exact next action. Redact patient and credential data.
Error Handling
| Condition | Response |
|---|---|
| Verification blocked | Use the official account/support path; do not impersonate a professional. |
| No citations visible | Treat onboarding as failed and capture a redacted support packet. |
| Real patient details supplied | Stop, remove them through approved means if possible, and notify the privacy owner. |
Examples
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
surface=web; user=verified clinician; question=synthetic guideline comparison
Expected handoff:
access=verified; answer=received; citation=open; patient-data=none
Resources
Limitations
- →Authentication errors occur with invalid credentials
- →Not found errors indicate an invalid API endpoint
- →Rate limits can be hit with too many requests
How it compares
This skill provides ready-to-use code examples for common OpenEvidence API interactions, simplifying the initial setup and testing compared to building queries from scratch.
Compared to similar skills
openevidence-hello-world side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openevidence-hello-world (this skill) | 7 | 2mo | Review | Beginner |
| mcp-builder | 136 | 5mo | Review | Advanced |
| telegram-mini-app | 62 | 8mo | Review | Advanced |
| stripe-integration | 48 | 4mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
telegram-mini-app
davila7
Expert in building Telegram Mini Apps (TWA) - web apps that run inside Telegram with native-like experience. Covers the TON ecosystem, Telegram Web App API, payments, user authentication, and building viral mini apps that monetize. Use when: telegram mini app, TWA, telegram web app, TON app, mini app.
stripe-integration
wshobson
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
backend-dev-guidelines
langfuse
Comprehensive backend development guide for Langfuse's Next.js 14/tRPC/Express/TypeScript monorepo. Use when creating tRPC routers, public API endpoints, BullMQ queue processors, services, or working with tRPC procedures, Next.js API routes, Prisma database access, ClickHouse analytics queries, Redis queues, OpenTelemetry instrumentation, Zod v4 validation, env.mjs configuration, tenant isolation patterns, or async patterns. Covers layered architecture (tRPC procedures → services, queue processors → services), dual database system (PostgreSQL + ClickHouse), projectId filtering for multi-tenant isolation, traceException error handling, observability patterns, and testing strategies (Jest for web, vitest for worker).
swapper-integration
shapeshift
Integrate new DEX aggregators, swappers, or bridge protocols (like Bebop, Portals, Jupiter, 0x, 1inch, etc.) into ShapeShift Web. Activates when user wants to add, integrate, or implement support for a new swapper. Guides through research, implementation, and testing following established patterns.
copilot-sdk
github
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.