Individual skill
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.
plugins/saas-packs/openevidence-pack/skills/openevidence-common-errors/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- openevidence Declared skill tag
- troubleshooting Declared skill tag
- quality Declared skill tag
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,725 bytesreferences/official-docs.mddoc · 2,563 bytes
Read excerpt
# OpenEvidence Answer-Quality Troubleshooting
## Overview
Separate access trouble, prompt ambiguity, evidence limitations, and unsafe interpretation before anyone acts on an answer. 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.