Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/openevidence-install-auth

@820dfc8
Run it yourself

Establish authorized OpenEvidence account access through official registration and institutional pathways. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence install auth", "OpenEvidence authentication", or a matching workflow request.

  • 2 files
  • 7 KB
  • MIT
  • Updated 2 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/openevidence-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈76 tokens for metadata: the name and description. ≈973 when used: this file. ≈641 more on demand in 1 file.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈304 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

OpenEvidence Account Verification and Access

Overview

Choose the supported user access path and verify it without packages, tokens, shared accounts, or private endpoints. 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 terms require account registration for full service access and make users responsible for account confidentiality.
  • The product is intended for healthcare professionals and may verify registration information.
  • No public OpenEvidence SDK package, API token, OAuth, or service-account contract was found.

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

  1. Identify individual versus institution-managed access, professional role, approved email/device, and accountable access owner.
  2. Read current registration, terms, privacy, security, and institution-specific access instructions.
  3. Complete only the official sign-up, sign-in, or administrator-issued path; do not install similarly named packages.
  4. Enable organization-required device and account protections and keep credentials in approved user-controlled storage.
  5. Verify access with a synthetic Ask workflow and record only non-secret evidence.
  6. Document recovery, termination, role-change, and suspected-compromise contacts.

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
Package suggested Reject it unless current first-party documentation explicitly names and authenticates it.
Shared credential proposed Require separate authorized accounts.
Account compromised Change credentials through official controls and notify the security owner.

Examples

This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.

Input:

access=institution-managed; role=physician; surface=mobile; patient-data=none

Expected handoff:

registration=verified; auth=official-ui; shared-secret=no; recovery-owner=known

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[web|mobile] [individual|institution]
version
1.14.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "openevidence",
  "authentication",
  "account"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; requires authorized OpenEvidence access and qualified clinical review for patient-care use

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/openevidence-install-auth