openevidence-core-workflow-b
Facilitates the retrieval of medical literature and generation of evidence-based reports using OpenEvidence.
Install
mkdir -p .claude/skills/openevidence-core-workflow-b && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8982" && unzip -o skill.zip -d .claude/skills/openevidence-core-workflow-b && rm skill.zipInstalls to .claude/skills/openevidence-core-workflow-b
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.
Execute OpenEvidence secondary workflow: DeepConsult Research Synthesis.Key capabilities
- →Search medical evidence databases
- →Create citation collections
- →Grade evidence using clinical frameworks
- →Generate structured evidence reports
How it works
The workflow searches medical literature, builds citation collections, grades findings using frameworks like GRADE, and generates formatted reports.
Inputs & outputs
When to use openevidence-core-workflow-b
- →Search medical literature databases
- →Create clinical citation collections
- →Generate evidence summaries
- →Filter studies by evidence level
About this skill
OpenEvidence EvidenceGrade and Citation Review
Overview
Treat the displayed grade as a navigation aid, then perform a source-level review of every material claim. 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
- The official user guide documents lettered EvidenceGrade output and links to its methodology.
- A grade summarizes evidence strength; it is not a patient-specific recommendation or correctness guarantee.
- Citation review must consider source type, date, population, outcome, and fit to the decision.
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
- List each material claim that could change diagnosis, treatment, safety, documentation, or patient communication.
- Capture the displayed EvidenceGrade and any caveats without treating the grade as the conclusion.
- Open the supporting citations and map each claim to the exact source or mark it unsupported.
- Check guideline authority, publication date, study population, intervention, comparator, outcomes, and limitations.
- Identify disagreements, indirectness, missing subgroups, or newer evidence that alters applicability.
- Return a clinician-review table with supported, uncertain, contradicted, and not-assessed claims.
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 |
|---|---|
| Citation unavailable | Mark the linked claim unverified; do not rely on a summary alone. |
| Grade missing | Continue source-level review and state that no grade was available. |
| Source is indirect | Describe the inference and require clinical judgment. |
Examples
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
response=de-identified excerpt; decision=screening interval; review=all material claims
Expected handoff:
claims=6; supported=4; uncertain=2; grade=recorded; clinician-signoff=required
Resources
When not to use it
- →Scenarios involving patient identifiers
- →Workflows requiring non-clinical research
Prerequisites
Limitations
- →HIPAA-compliant and SOC 2 Type II certified , never include patient identifiers
- →Exceeded 60 queries/minute triggers rate limiting
How it compares
It automates the synthesis of clinical evidence and grading rather than performing simple keyword searches.
Compared to similar skills
openevidence-core-workflow-b side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openevidence-core-workflow-b (this skill) | 0 | 2mo | Review | Advanced |
| azure-ai-document-intelligence-ts | 0 | 5mo | Review | Intermediate |
| mcp-builder | 136 | 5mo | Review | Advanced |
| telegram-mini-app | 62 | 8mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
azure-ai-document-intelligence-ts
microsoft
Extract text, tables, and structured data from documents using Azure Document Intelligence (@azure-rest/ai-document-intelligence). Use when processing invoices, receipts, IDs, forms, or building custom document models.
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.
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.
nodejs-backend-patterns
wshobson
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.