From openevidence-pack
Installs @openevidence/sdk via npm or pip and configures API key authentication for clinical decision support in Node.js or Python projects.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openevidence-pack:openevidence-install-authThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Set up OpenEvidence Medical AI API for clinical decision support and evidence-based queries.
Set up OpenEvidence Medical AI API for clinical decision support and evidence-based queries.
npm install @openevidence/sdk
# API key from OpenEvidence developer portal
export OPENEVIDENCE_API_KEY="your-api-key-here"
echo 'OPENEVIDENCE_API_KEY=your-api-key' >> .env
import { OpenEvidenceClient } from '@openevidence/sdk';
const client = new OpenEvidenceClient({
apiKey: process.env.OPENEVIDENCE_API_KEY,
organization: process.env.OPENEVIDENCE_ORG_ID
});
const result = await client.query({ question: 'What are first-line treatments for Type 2 diabetes?' });
console.log(`Answer: ${result.answer.substring(0, 100)}...`);
console.log(`Citations: ${result.citations.length} references`);
import openevidence
client = openevidence.Client(api_key=os.environ['OPENEVIDENCE_API_KEY'])
result = client.query(question='What are first-line treatments for Type 2 diabetes?')
print(f'Answer: {result.answer[:100]}...')
print(f'Citations: {len(result.citations)} references')
| Error | Code | Solution |
|---|---|---|
| Invalid API key | 401 | Verify credentials in dashboard |
| Permission denied | 403 | Check API scopes/permissions |
| Rate limited | 429 | Implement backoff |
After auth, proceed to openevidence-hello-world.
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin openevidence-pack5plugins reuse this skill
First indexed Jul 10, 2026
Install and configure OpenEvidence SDK/API authentication. Use when setting up a new OpenEvidence integration. Trigger: "install openevidence", "setup openevidence", "openevidence auth".
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.