MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Agent skill
Openevidence Reference Architecture
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Design a governed operating model around OpenEvidence’s supported product workflows and clinician review.
Install Openevidence Reference Architecture
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .claude/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .claude/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .agents/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .agents/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .cursor/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .cursor/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/openevidence-reference-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .gemini/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .gemini/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .github/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .github/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-reference-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/openevidence-reference-architecture .opencode/skills/openevidence-reference-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "openevidence-reference-architecture" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-reference-architecture into .opencode/skills/openevidence-reference-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-reference-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
openevidence-reference-architecture- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 450 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design a governed operating model around OpenEvidence’s supported product workflows and clinician review.
- Works in 6 steps: Map users, patient touchpoints, product… → Draw trust boundaries for credentials,… → Place clinician review before any care… → …
- Working with OpenEvidence in a healthcare organization
- SKILL.md covers Overview, Prerequisites, Tool Discipline and Current Contract, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Openevidence Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use
It sits in Agent Workflows. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- Working with OpenEvidence in a healthcare organization
- With openevidence reference architecture
- OpenEvidence architecture
- A matching workflow request
Example prompts
- “openevidence reference architecture”
- “OpenEvidence architecture”
- “/openevidence-reference-architecture”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebFetch, Write, Edit
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Map users, patient touchpoints, product features, source evidence, record systems, support, and governance owners.
- Draw trust boundaries for credentials, PHI, recordings, copied outputs, citations, and third-party communications.
- Place clinician review before any care decision and define how evidence is verified and uncertainty recorded.
- Use only documented handoffs; label desired integrations as vendor-confirmation questions, not architecture facts.
- Add access lifecycle, monitoring, incident response, downtime alternative, retention, and rollback.
- Review the model with clinical, privacy, security, legal, operations, and records owners.
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWebFetchWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
openevidence.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use
From compatibility in the SKILL.md frontmatter.
Context cost
Openevidence Reference Architecture loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 80 tokens; SKILL.md has 450 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 450 words, ~1,155 tokens.
Download SKILL.mdSave it as
.claude/skills/openevidence-reference-architecture/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openevidence-reference-architecture
- description
- 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.
- allowed-tools
- Read, Glob, Grep, WebFetch, Write, Edit
- compatibility
- Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use
- argument-hint
- [architecture-notes-path] [workflow]
- version
- 1.14.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, openevidence, architecture, governance
- model
- inherit
- effort
- high
OpenEvidence Human-in-the-Loop Operating Model
Overview
Map people, product surfaces, evidence review, governed records, and incident paths without fabricating integrations. 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 documented surface comprises product workflows such as Ask, Visits, and Dialer, subject to current availability.
- No public API, webhook, SDK, or infrastructure deployment contract was found.
- Clinical decisions and official records remain owned by qualified people and approved systems.
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
- Map users, patient touchpoints, product features, source evidence, record systems, support, and governance owners.
- Draw trust boundaries for credentials, PHI, recordings, copied outputs, citations, and third-party communications.
- Place clinician review before any care decision and define how evidence is verified and uncertainty recorded.
- Use only documented handoffs; label desired integrations as vendor-confirmation questions, not architecture facts.
- Add access lifecycle, monitoring, incident response, downtime alternative, retention, and rollback.
- Review the model with clinical, privacy, security, legal, operations, and records owners.
Show full SKILL.md (173 more words)Show less
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 |
|---|---|
| Private endpoint appears in design | Remove it until a signed/current contract documents it. |
| AI output becomes system of record automatically | Insert human review and approved record controls. |
| No downtime path | Block go-live until one exists. |
Examples
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
workflow=Ask-to-clinical-note; systems=OpenEvidence+EHR; integration=manual-copyExpected handoff:
boundaries=6; human-gates=2; undocumented-integrations=0; review=pendingResources
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/openevidence-reference-architecture of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Openevidence Reference Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Openevidence Reference Architecture this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Openevidence Reference Architecture
What does Openevidence Reference Architecture do?
Design a governed operating model around OpenEvidence’s supported product workflows and clinician review. Openevidence Reference Architecture is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design a governed operating model around OpenEvidence’s supported product workflows and clinician review.
When should I use Openevidence Reference Architecture?
Openevidence Reference Architecture fits situations like: working with OpenEvidence in a healthcare organization; with openevidence reference architecture; openEvidence architecture; A matching workflow request.
How do I install Openevidence Reference Architecture in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a claude-code`. Or copy the skill folder (skills/.curated/openevidence-reference-architecture in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/openevidence-reference-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Openevidence Reference Architecture in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a codex`. Or copy the skill folder (skills/.curated/openevidence-reference-architecture in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/openevidence-reference-architecture in your project. Codex loads it when a task matches its description.
Can I use Openevidence Reference Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-reference-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/openevidence-reference-architecture, .gemini/skills/openevidence-reference-architecture, .github/skills/openevidence-reference-architecture and .opencode/skills/openevidence-reference-architecture in your project.
What does Openevidence Reference Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Openevidence Reference Architecture is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebFetch, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use.
Does Openevidence Reference Architecture access the network?
SKILL.md names 1 domain. As links in the text: openevidence.com. This is read from the text; nothing was executed.
Is Openevidence Reference Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Openevidence Reference Architecture use?
Openevidence Reference Architecture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Openevidence Reference Architecture use?
About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 641 tokens, read only when the agent opens those files.
What are the alternatives to Openevidence Reference Architecture?
Skills that share tags, products or a category with Openevidence Reference Architecture: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openevidence Reference Architecture?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.