Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
Agent skill
Openevidence Install Auth
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Establish authorized OpenEvidence account access through official registration and institutional pathways.
Install Openevidence Install Auth
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-install-auth -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-install-auth --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-install-auth .claude/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .claude/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-authType 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-install-auth -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-install-auth --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-install-auth .agents/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .agents/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-auth -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-install-auth --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-install-auth .cursor/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .cursor/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-auth--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-install-auth -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-install-auth --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-install-auth .gemini/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .gemini/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-authInstalls 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-install-auth -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-install-auth .github/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .github/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-auth -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-install-auth --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-install-auth .opencode/skills/openevidence-install-auth && 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-install-auth" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-install-auth into .opencode/skills/openevidence-install-auth/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-install-auth", 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-install-auth- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 443 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Establish authorized OpenEvidence account access through official registration and institutional pathways.
- Works in 6 steps: Identify individual versus… → Read current registration, terms,… → Complete only the official sign-up,… → …
- 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 Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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.
Its SKILL.md is about 1.2k 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 Backend & APIs, covering Authentication. 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 install auth
- OpenEvidence authentication
- A matching workflow request
Example prompts
- “openevidence install auth”
- “OpenEvidence authentication”
- “/openevidence-install-auth”
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.
- Identify individual versus institution-managed access, professional role, approved email/device, and accountable access owner.
- Read current registration, terms, privacy, security, and institution-specific access instructions.
- Complete only the official sign-up, sign-in, or administrator-issued path; do not install similarly named packages.
- Enable organization-required device and account protections and keep credentials in approved user-controlled storage.
- Verify access with a synthetic Ask workflow and record only non-secret evidence.
- Document recovery, termination, role-change, and suspected-compromise contacts.
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 Install Auth loads about 1.2k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 443 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). 443 words, ~1,158 tokens.
Download SKILL.mdSave it as
.claude/skills/openevidence-install-auth/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openevidence-install-auth
- description
- 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.
- 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
- [web|mobile] [individual|institution]
- version
- 1.14.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, openevidence, authentication, account
- model
- inherit
- effort
- high
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
- Identify individual versus institution-managed access, professional role, approved email/device, and accountable access owner.
- Read current registration, terms, privacy, security, and institution-specific access instructions.
- Complete only the official sign-up, sign-in, or administrator-issued path; do not install similarly named packages.
- Enable organization-required device and account protections and keep credentials in approved user-controlled storage.
- Verify access with a synthetic Ask workflow and record only non-secret evidence.
- Document recovery, termination, role-change, and suspected-compromise contacts.
Show full SKILL.md (170 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 |
|---|---|
| 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=noneExpected handoff:
registration=verified; auth=official-ui; shared-secret=no; recovery-owner=knownResources
© 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-install-auth of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Openevidence Install Auth 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 Install Auth this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Supabase Development and Debuggingsupabase/agent-skills | 2.7k | 3 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Better Auth Best Practiceslatitude-dev/latitude-llm | 4.7k | 7 repos | ~1.6k | Automated safety check: Pass | MIT | |
| Gitnexus Exploringaws-samples/sample-kolya-br-proxy | 106 | 12 repos | ~749 | Automated safety check: Pass | MIT-0 | |
| Supabasecurvenote/curvenote | 170 | 5 repos | ~2.2k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Supabase Development and Debugging
supabase/agent-skills
General Supabase skill for database, auth, Edge Functions, Realtime and storage work, plus client libraries, migrations, security audits, debugging and reading logs.
Better Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
- Official
Gitnexus Exploring
aws-samples/sample-kolya-br-proxy
A skill your agent uses when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase.
Supabase
curvenote/curvenote
A skill your agent uses when doing ANY task involving Supabase.
- Official
Gemini Live API Dev
google-gemini/gemini-skills
A skill your agent uses when building real-time, bidirectional streaming applications with the Gemini Live API, or migrating legacy Live models (2.0/2.5/3.1) to Gemini 3.8 Live.
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 Install Auth
What does Openevidence Install Auth do?
Establish authorized OpenEvidence account access through official registration and institutional pathways. Openevidence Install Auth is an agent skill from jeremylongshore/tons-of-skills-marketplace. Establish authorized OpenEvidence account access through official registration and institutional pathways.
When should I use Openevidence Install Auth?
Openevidence Install Auth fits situations like: working with OpenEvidence in a healthcare organization; with openevidence install auth; openEvidence authentication; A matching workflow request.
How do I install Openevidence Install Auth in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-install-auth -a claude-code`. Or copy the skill folder (skills/.curated/openevidence-install-auth in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/openevidence-install-auth in your project. Claude Code loads it when a task matches its description.
How do I install Openevidence Install Auth in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-install-auth -a codex`. Or copy the skill folder (skills/.curated/openevidence-install-auth in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/openevidence-install-auth in your project. Codex loads it when a task matches its description.
Can I use Openevidence Install Auth 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-install-auth -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-install-auth, .gemini/skills/openevidence-install-auth, .github/skills/openevidence-install-auth and .opencode/skills/openevidence-install-auth in your project.
What does Openevidence Install Auth need to run?
SKILL.md names no scripts, command-line tools or credentials: Openevidence Install Auth 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 Install Auth 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 Install Auth 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 Install Auth use?
Openevidence Install Auth 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 Install Auth use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 Install Auth?
Skills that share tags, products or a category with Openevidence Install Auth: Fortify Development (coollabsio/coolify, 63k stars), Supabase Development and Debugging (supabase/agent-skills, 2.7k stars), Better Auth Best Practices (latitude-dev/latitude-llm, 4.7k stars) and Gitnexus Exploring (aws-samples/sample-kolya-br-proxy, 106 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openevidence Install Auth?
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.