Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Agent skill
Openevidence Deploy Integration
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries.
Install Openevidence Deploy Integration
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-deploy-integration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-deploy-integration --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-deploy-integration .claude/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .claude/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integrationType 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-deploy-integration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-deploy-integration --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-deploy-integration .agents/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .agents/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-deploy-integration --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-deploy-integration .cursor/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .cursor/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integration--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-deploy-integration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-deploy-integration --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-deploy-integration .gemini/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .gemini/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integrationInstalls 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-deploy-integration -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-deploy-integration .github/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .github/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integration -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-deploy-integration --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-deploy-integration .opencode/skills/openevidence-deploy-integration && 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-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-deploy-integration into .opencode/skills/openevidence-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-deploy-integration", 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-deploy-integration- GitHub stars
- 2.8k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 427 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries.
- Works in 6 steps: Select one bounded workflow and define… → Confirm account eligibility, feature… → Design training for prompting,… → …
- 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 Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence deploy integration", "OpenEvidence deployment", or a matching workflow request.
Its SKILL.md is about 1.1k 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 DevOps & Cloud, covering Deployment. 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 deploy integration
- OpenEvidence deployment
- A matching workflow request
Example prompts
- “openevidence deploy integration”
- “OpenEvidence deployment”
- “/openevidence-deploy-integration”
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.
- Select one bounded workflow and define users, patients affected, systems touched, success criteria, and explicit exclusions.
- Confirm account eligibility, feature availability, agreement terms, data handling, consent, and support path.
- Design training for prompting, EvidenceGrade, citation verification, professional judgment, and failure escalation.
- Pilot with synthetic scenarios, then a small authorized cohort under heightened review.
- Review quality, safety signals, adoption, workflow burden, and unresolved controls before expansion.
- Record launch/no-launch, rollback trigger, owners, training evidence, and next review date.
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 Deploy Integration loads about 1.1k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 427 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). 427 words, ~1,122 tokens.
Download SKILL.mdSave it as
.claude/skills/openevidence-deploy-integration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openevidence-deploy-integration
- description
- Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence deploy integration", "OpenEvidence deployment", 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
- [practice-plan-path] [workflow]
- version
- 1.14.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, openevidence, deployment, change-management
- model
- inherit
- effort
- high
OpenEvidence Practice Rollout Plan
Overview
Treat rollout as clinical workflow change, not software API deployment. 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
- OpenEvidence is delivered through documented end-user product surfaces.
- Institution-specific availability, integrations, commitments, and data terms require written confirmation.
- A rollout needs clinical, privacy, security, operational, and training ownership.
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
- Select one bounded workflow and define users, patients affected, systems touched, success criteria, and explicit exclusions.
- Confirm account eligibility, feature availability, agreement terms, data handling, consent, and support path.
- Design training for prompting, EvidenceGrade, citation verification, professional judgment, and failure escalation.
- Pilot with synthetic scenarios, then a small authorized cohort under heightened review.
- Review quality, safety signals, adoption, workflow burden, and unresolved controls before expansion.
- Record launch/no-launch, rollback trigger, owners, training evidence, and next review date.
Show full SKILL.md (169 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 |
|---|---|
| Feature not documented | Exclude it until OpenEvidence or the contract owner confirms support. |
| Governance owner missing | Do not launch the workflow. |
| Pilot creates unsafe reliance | Pause, retrain, and reassess before resuming. |
Examples
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
workflow=Ask for guideline summaries; cohort=5 clinicians; phase=pilotExpected handoff:
decision=conditional-go; controls=verified; rollback=defined; review=14dResources
© 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-deploy-integration of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Openevidence Deploy Integration 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 Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Mirrord Operator
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
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 Deploy Integration
What does Openevidence Deploy Integration do?
Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries. Openevidence Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries.
When should I use Openevidence Deploy Integration?
Openevidence Deploy Integration fits situations like: working with OpenEvidence in a healthcare organization; with openevidence deploy integration; openEvidence deployment; A matching workflow request.
How do I install Openevidence Deploy Integration in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-deploy-integration -a claude-code`. Or copy the skill folder (skills/.curated/openevidence-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/openevidence-deploy-integration in your project. Claude Code loads it when a task matches its description.
How do I install Openevidence Deploy Integration in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-deploy-integration -a codex`. Or copy the skill folder (skills/.curated/openevidence-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/openevidence-deploy-integration in your project. Codex loads it when a task matches its description.
Can I use Openevidence Deploy Integration 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-deploy-integration -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-deploy-integration, .gemini/skills/openevidence-deploy-integration, .github/skills/openevidence-deploy-integration and .opencode/skills/openevidence-deploy-integration in your project.
What does Openevidence Deploy Integration need to run?
SKILL.md names no scripts, command-line tools or credentials: Openevidence Deploy Integration 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 Deploy Integration 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 Deploy Integration 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 Deploy Integration use?
Openevidence Deploy Integration 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 Deploy Integration use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Deploy Integration?
Skills that share tags, products or a category with Openevidence Deploy Integration: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Mirrord Operator (metalbear-co/mirrord, 5.4k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openevidence Deploy Integration?
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.