Novu Design Workflow
novuhq/novu
Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.
Agent skill
Openevidence Webhooks Events
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas.
Install Openevidence Webhooks Events
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-webhooks-events -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-webhooks-events --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-webhooks-events .claude/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .claude/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-eventsType 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-webhooks-events -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-webhooks-events --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-webhooks-events .agents/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .agents/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-events -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-webhooks-events --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-webhooks-events .cursor/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .cursor/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-events--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-webhooks-events -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace openevidence-webhooks-events --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-webhooks-events .gemini/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .gemini/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-eventsInstalls 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-webhooks-events -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-webhooks-events .github/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .github/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-events -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-webhooks-events --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-webhooks-events .opencode/skills/openevidence-webhooks-events && 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-webhooks-events" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/openevidence-webhooks-events into .opencode/skills/openevidence-webhooks-events/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "openevidence-webhooks-events", 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-webhooks-events- GitHub stars
- 2.8k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 448 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas.
- Works in 6 steps: Define the business event, source… → Search current first-party and… → If none exists, block endpoint creation,… → …
- 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 Webhooks Events is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence webhooks events", "OpenEvidence handoffs", 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 Webhooks. 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 webhooks events
- OpenEvidence handoffs
- A matching workflow request
Example prompts
- “openevidence webhooks events”
- “OpenEvidence handoffs”
- “/openevidence-webhooks-events”
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.
- Define the business event, source feature, destination, latency need, data class, failure impact, and accountable owner.
- Search current first-party and institution-specific documentation for an explicit webhook or integration contract.
- If none exists, block endpoint creation, secret generation, signature code, and guessed event names.
- Design the minimum approved manual handoff, product-native workflow, or vendor-confirmation request.
- For any confirmed integration, require written event, auth, verification, replay, ordering, retention, PHI, and support contracts before…
- Return the supported handoff, rejected assumptions, risks, owner, and approval state.
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 Webhooks Events 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 78 tokens; SKILL.md has 448 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). 448 words, ~1,158 tokens.
Download SKILL.mdSave it as
.claude/skills/openevidence-webhooks-events/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- openevidence-webhooks-events
- description
- Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence webhooks events", "OpenEvidence handoffs", 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
- [event-or-handoff] [destination]
- version
- 1.14.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- saas, openevidence, handoffs, no-webhooks
- model
- inherit
- effort
- high
OpenEvidence Workflow Handoffs and No-Webhook Guard
Overview
Translate event-driven integration requests into supported manual or contract-confirmed handoffs. 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
- No public OpenEvidence webhook endpoint, signing method, event catalog, or retry policy was found.
- Private network behavior is not a supported integration contract.
- Documented product features and institution agreements define allowable handoffs.
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
- Define the business event, source feature, destination, latency need, data class, failure impact, and accountable owner.
- Search current first-party and institution-specific documentation for an explicit webhook or integration contract.
- If none exists, block endpoint creation, secret generation, signature code, and guessed event names.
- Design the minimum approved manual handoff, product-native workflow, or vendor-confirmation request.
- For any confirmed integration, require written event, auth, verification, replay, ordering, retention, PHI, and support contracts before implementation.
- Return the supported handoff, rejected assumptions, risks, owner, and approval state.
Show full SKILL.md (177 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 |
|---|---|
| Webhook URL requested | Do not create it without the official contract and receiving-system approval. |
| Payload example supplied by third party | Treat it as untrusted until OpenEvidence confirms provenance. |
| Manual handoff risks delay | Define operational escalation; do not fabricate automation. |
Examples
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
event=Visit note complete; destination=EHR; webhook-contract=absentExpected handoff:
webhook=blocked; handoff=approved manual copy; PHI-boundary=reviewed; owner=operationsResources
© 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-webhooks-events of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/official-docs.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Openevidence Webhooks Events 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 Webhooks Events this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Novu Design Workflownovuhq/novu | 40k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Golivemikehasa/golive-skill | 1.3k | — | ~13k | Automated safety check: Notes | MIT | |
| Stripe Appsfossasia/eventyay | 1.7k | 1 repos | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Dingtalk Messageagentscope-ai/ReMe | 3.6k | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| PR Review Provideryansongda/pay | 5.4k | — | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Golive
mikehasa/golive-skill
Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS).
Stripe Apps
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
Dingtalk Message
agentscope-ai/ReMe
钉钉消息发送技能。支持企业内部机器人（批量单聊/群聊）和 Webhook 自定义机器人两种接入方式，支持多机器人管理，支持文本、Markdown、链接、ActionCard、FeedCard等多种消息类型。
PR Review Provider
yansongda/pay
A skill your agent uses when reviewing PRs that add or modify a payment Provider in yansongda/pay - covers plugin pipeline, multi-tenant safety, signature verification, docs, and naming conventions.
Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
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 Webhooks Events
What does Openevidence Webhooks Events do?
Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas. Openevidence Webhooks Events is an agent skill from jeremylongshore/tons-of-skills-marketplace. Design safe OpenEvidence workflow handoffs while explicitly rejecting undocumented public webhooks and event schemas.
When should I use Openevidence Webhooks Events?
Openevidence Webhooks Events fits situations like: working with OpenEvidence in a healthcare organization; with openevidence webhooks events; openEvidence handoffs; A matching workflow request.
How do I install Openevidence Webhooks Events in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-webhooks-events -a claude-code`. Or copy the skill folder (skills/.curated/openevidence-webhooks-events in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/openevidence-webhooks-events in your project. Claude Code loads it when a task matches its description.
How do I install Openevidence Webhooks Events in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill openevidence-webhooks-events -a codex`. Or copy the skill folder (skills/.curated/openevidence-webhooks-events in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/openevidence-webhooks-events in your project. Codex loads it when a task matches its description.
Can I use Openevidence Webhooks Events 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-webhooks-events -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-webhooks-events, .gemini/skills/openevidence-webhooks-events, .github/skills/openevidence-webhooks-events and .opencode/skills/openevidence-webhooks-events in your project.
What does Openevidence Webhooks Events need to run?
SKILL.md names no scripts, command-line tools or credentials: Openevidence Webhooks Events 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 Webhooks Events 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 Webhooks Events 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 Webhooks Events use?
Openevidence Webhooks Events 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 Webhooks Events 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 Webhooks Events?
Skills that share tags, products or a category with Openevidence Webhooks Events: Novu Design Workflow (novuhq/novu, 40k stars), Golive (mikehasa/golive-skill, 1.3k stars), Stripe Apps (fossasia/eventyay, 1.7k stars) and Dingtalk Message (agentscope-ai/ReMe, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Openevidence Webhooks Events?
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.