openevidence-ci-integration
Ci Integration for OpenEvidence. Trigger: "openevidence ci integration".
What this skill does
# OpenEvidence CI Integration
## Overview
Set up CI/CD for OpenEvidence clinical decision support integrations: run unit tests with mocked evidence query and citation responses on every PR, validate live API connectivity for clinical queries on merge to main. OpenEvidence provides AI-powered medical evidence retrieval and clinical decision support, so CI pipelines verify query formatting, evidence parsing, citation extraction, and response quality scoring.
## GitHub Actions Workflow
```yaml
# .github/workflows/openevidence-ci.yml
name: OpenEvidence CI
on:
pull_request:
paths: ['src/openevidence/**', 'tests/**']
push:
branches: [main]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm test -- --reporter=verbose
integration-tests:
if: github.ref == 'refs/heads/main'
needs: unit-tests
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with: { node-version: '20' }
- run: npm ci
- run: npm run test:integration
env:
OPENEVIDENCE_API_KEY: ${{ secrets.OPENEVIDENCE_API_KEY }}
```
## Mock-Based Unit Tests
```typescript
// tests/openevidence-service.test.ts
import { describe, it, expect, vi } from 'vitest';
import { queryEvidence, extractCitations } from '../src/openevidence-service';
vi.mock('../src/openevidence-client', () => ({
OpenEvidenceClient: vi.fn().mockImplementation(() => ({
query: vi.fn().mockResolvedValue({
answer: 'Current evidence supports early intervention with GLP-1 agonists...',
confidence: 0.92,
citations: [
{ title: 'NEJM 2025 Meta-Analysis', doi: '10.1056/NEJMoa2501234', year: 2025 },
{ title: 'Lancet Diabetes Review', doi: '10.1016/S2213-8587(25)00123', year: 2025 },
],
evidenceLevel: 'high',
}),
listQueries: vi.fn().mockResolvedValue({
queries: [{ id: 'q_abc', question: 'GLP-1 efficacy', status: 'completed' }],
}),
})),
}));
describe('OpenEvidence Service', () => {
it('queries clinical evidence with citations', async () => {
const result = await queryEvidence('GLP-1 agonist efficacy for type 2 diabetes');
expect(result.confidence).toBeGreaterThan(0.9);
expect(result.citations).toHaveLength(2);
});
it('extracts citation DOIs from response', async () => {
const citations = await extractCitations('q_abc');
expect(citations[0].doi).toMatch(/^10\.\d+/);
});
});
```
## Integration Tests
```typescript
// tests/integration/openevidence.integration.test.ts
import { describe, it, expect } from 'vitest';
const hasKey = !!process.env.OPENEVIDENCE_API_KEY;
describe.skipIf(!hasKey)('OpenEvidence Live API', () => {
it('queries clinical evidence', async () => {
const res = await fetch('https://api.openevidence.com/v1/query', {
method: 'POST',
headers: {
'Authorization': `Bearer ${process.env.OPENEVIDENCE_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({ question: 'Aspirin dosing for secondary prevention' }),
});
expect(res.status).toBe(200);
const body = await res.json();
expect(body).toHaveProperty('answer');
expect(body).toHaveProperty('citations');
});
});
```
## Error Handling
| CI Issue | Cause | Fix |
|----------|-------|-----|
| `401 Unauthorized` | Invalid API key | Regenerate at openevidence.com account settings |
| Empty citations array | Query too vague for evidence matching | Use specific clinical terms with condition and intervention |
| Low confidence score | Insufficient published evidence | Check evidence level field and handle `low` confidence gracefully |
| Rate limit (429) | Too many queries in test suite | Add throttling between clinical queries (1 req/sec) |
| Response timeout | Complex query requiring deep search | Increase fetch timeout to 30s for clinical evidence lookups |
## Resources
- [OpenEvidence Platform](https://www.openevidence.com/)
- [OpenEvidence API Documentation](https://docs.openevidence.com/)
- [GitHub Actions Secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets)
## Next Steps
See `openevidence-deploy-integration`.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.