Walkthrough
alexanderop/walkthrough
Generates a self-contained HTML file with an interactive, clickable Mermaid diagram (flowchart or ER diagram) that explains how a codebase feature, flow, architecture, or database schema works.
Links entities extracted by OpenMed to UMLS Metathesaurus CUIs using the USER'S OWN UTS API key, with nothing from the Metathesaurus bundled or cached.
$ npx skills add maziyarpanahi/openmed --skill linking-umls-concepts -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maziyarpanahi/openmed linking-umls-concepts --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/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/linking-umls-concepts .claude/skills/linking-umls-concepts && 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 "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .claude/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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/maziyarpanahi/openmed/tree/master/skills/linking-umls-conceptsType 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 maziyarpanahi/openmed --skill linking-umls-concepts -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maziyarpanahi/openmed linking-umls-concepts --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/linking-umls-concepts .agents/skills/linking-umls-concepts && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .agents/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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 maziyarpanahi/openmed --skill linking-umls-concepts -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maziyarpanahi/openmed linking-umls-concepts --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/linking-umls-concepts .cursor/skills/linking-umls-concepts && 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 "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .cursor/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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/maziyarpanahi/openmed.git --path skills/linking-umls-concepts--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 maziyarpanahi/openmed --skill linking-umls-concepts -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maziyarpanahi/openmed linking-umls-concepts --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/linking-umls-concepts .gemini/skills/linking-umls-concepts && 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 "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .gemini/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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 maziyarpanahi/openmed linking-umls-conceptsInstalls 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 maziyarpanahi/openmed --skill linking-umls-concepts -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/linking-umls-concepts .github/skills/linking-umls-concepts && 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 "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .github/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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 maziyarpanahi/openmed --skill linking-umls-concepts -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maziyarpanahi/openmed linking-umls-concepts --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/linking-umls-concepts .opencode/skills/linking-umls-concepts && 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 "linking-umls-concepts" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/linking-umls-concepts into .opencode/skills/linking-umls-concepts/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "linking-umls-concepts", 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.
linking-umls-conceptsLinks entities extracted by OpenMed to UMLS Metathesaurus CUIs using the USER'S OWN UTS API key, with nothing from the Metathesaurus bundled or cached.
Linking Umls Concepts is an agent skill from maziyarpanahi/openmed. Links entities extracted by OpenMed to UMLS Metathesaurus CUIs using the USER'S OWN UTS API key, with nothing from the Metathesaurus bundled or cached. Use when the user wants to normalize concepts across vocabularies to a single CUI, resolve synonyms via the UMLS, filter by semantic type, or cross-walk between SNOMED CT, ICD-10, RxNorm and MeSH through their shared CUI. Trigger keywords: UMLS, CUI, Metathesaurus, UTS API key, semantic type, TUI, MetaMap, QuickUMLS, concept normalization, cross-vocabulary. Pairs…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Diagrams and Database schema design. The repository describes itself as: Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android… The licence is Apache-2.0.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 34d7b8c. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
uts-ws.nlm.nih.govAlso links to:
nlm.nih.govuts.nlm.nih.govdocumentation.uts.nlm.nih.govlhncbc.nlm.nih.govgithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
API_KEYUTS_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Linking Umls Concepts loads about 2k tokens when it runs. Until then it costs about 198 tokens; SKILL.md has 619 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.
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.
The full file from maziyarpanahi/openmed at commit 34d7b8c, republished under its Apache-2.0 licence (© maziyarpanahi). 619 words, ~2,039 tokens.
.claude/skills/linking-umls-concepts/SKILL.md (or your agent's skills folder).Resolve concept spans that OpenMed extracts to UMLS Metathesaurus concepts.
The atom is the CUI (Concept Unique Identifier, e.g. C0011860): one CUI
unifies synonyms from many source vocabularies (SNOMED CT, ICD-10-CM, RxNorm,
MeSH, LOINC), making the CUI the natural hub for cross-vocabulary normalization.
Every concept also carries one or more semantic types (TUIs, e.g. Disease or
Syndrome T047) for type-based filtering.
Hard licensing boundary — read first. The UMLS Metathesaurus is license-restricted. OpenMed and this skill never bundle, ship, or cache Metathesaurus content. Concept linking runs out-of-process against the NLM UTS (UMLS Terminology Services) REST API using the user's own UTS API key. A free UTS account + API key is required (request at uts.nlm.nih.gov and accept the UMLS license). The Metathesaurus stays user-supplied: your code holds only the key (from the environment) and stores only returned CUIs/strings.
C0027051).normalizing-rxnorm) or SNOMED (mapping-to-snomed).The UTS REST API base is https://uts-ws.nlm.nih.gov/rest. Authentication uses
your API key as the apiKey query parameter (the modern, simplest method).
import os, requests
UTS = "https://uts-ws.nlm.nih.gov/rest"
API_KEY = os.environ["UTS_API_KEY"] # USER's own key — never hardcoded
VERSION = "current" # or a fixed release like 2024AB
def search(term: str, sabs: str | None = None, count: int = 10) -> list[dict]:
"""Search the Metathesaurus for a term; optionally restrict source vocabs."""
params = {"string": term, "apiKey": API_KEY, "pageSize": count}
if sabs: # e.g. "SNOMEDCT_US,RXNORM,ICD10CM"
params["sabs"] = sabs
r = requests.get(f"{UTS}/search/{VERSION}", params=params, timeout=15)
r.raise_for_status()
return r.json().get("result", {}).get("results", [])
def concept(cui: str) -> dict:
"""Pull a concept's preferred name and semantic types."""
r = requests.get(f"{UTS}/content/{VERSION}/CUI/{cui}",
params={"apiKey": API_KEY}, timeout=15)
r.raise_for_status()
return r.json().get("result", {})
def crosswalk(cui: str, target_sab: str) -> list[dict]:
"""Atoms of a CUI in a target vocabulary (the cross-walk)."""
r = requests.get(f"{UTS}/content/{VERSION}/CUI/{cui}/atoms",
params={"apiKey": API_KEY, "sabs": target_sab,
"pageSize": 50}, timeout=20)
r.raise_for_status()
return r.json().get("result", [])
hits = search("type 2 diabetes") # -> [{ui: 'C0011860', name: ...}, ...]
sct = crosswalk("C0011860", "SNOMEDCT_US") # CUI -> SNOMED CT codes/search/{version} for candidate CUIs./content/.../CUI/{cui} and keep only the expected group.confidence to choose one CUI./CUI/{cui}/atoms?sabs=.openmed.analyze_text(..., output_format="dict") returns entities, each a dict
with text, label, confidence, start, end. Use the label to pick the
semantic-type group you keep:
import openmed
note = "History of myocardial infarction; started on lisinopril."
result = openmed.analyze_text(
note,
model_name="disease_detection_superclinical", # Disease category
output_format="dict",
)
# OpenMed label -> acceptable UMLS semantic-type groups (TUI prefixes)
KEEP_STY = {
"DISEASE": {"Disease or Syndrome", "Sign or Symptom", "Neoplastic Process"},
"DRUG": {"Pharmacologic Substance", "Clinical Drug"},
"CHEM": {"Pharmacologic Substance", "Organic Chemical"},
}
for ent in result["entities"]:
for hit in search(ent["text"], count=5):
cui = hit["ui"]
stys = {s["name"] for s in concept(cui).get("semanticTypes", [])}
if not KEEP_STY.get(ent["label"]) or stys & KEEP_STY[ent["label"]]:
print(ent["text"], ent["start"], ent["end"], "->", cui, hit["name"])
breakKeep OpenMed's start/end offsets beside each CUI for traceability. Store only
CUIs and codes — never the raw note, never a local copy of the Metathesaurus.
current drifts at each UMLS release. Pin
a release (e.g. 2024AB) for stable, auditable mappings; record it.sabs to the vocabularies you are
licensed for and actually need; this both narrows results and respects per-source
license terms inside UMLS.© maziyarpanahi, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/linking-umls-concepts of maziyarpanahi/openmed.
Open the folder on GitHubat commit 34d7b8c
Linking Umls Concepts 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 |
|---|---|---|---|---|---|---|
| Linking Umls Concepts this skillmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Walkthroughalexanderop/walkthrough | 141 | — | ~3.4k | Automated safety check: Notes | None | |
| Managedcode Orleans Graphmanagedcode/dotnet-skills | 486 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Datamodellmnimbalyst/nimbalyst | 1.9k | — | ~713 | Automated safety check: Pass | MIT | |
| Drizzle Erdhiroppy/mf-dashboard | 418 | — | ~627 | Automated safety check: Pass | MIT | |
| Entity ModelAI-Unified-Process/marketplace | 142 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
alexanderop/walkthrough
Generates a self-contained HTML file with an interactive, clickable Mermaid diagram (flowchart or ER diagram) that explains how a codebase feature, flow, architecture, or database schema works.
managedcode/dotnet-skills
Integrate ManagedCode.Orleans.Graph into an Orleans-based .NET application for grain-call policy enforcement, deadlock detection, live-call telemetry, and Mermaid graph diagnostics.
nimbalyst/nimbalyst
Create visual data models for database schemas using Nimbalyst's DataModelLM editor.
hiroppy/mf-dashboard
A skill your agent uses when needing to visualize database schema, generate ERD diagrams from Drizzle ORM schemas, or understand table relationships
AI-Unified-Process/marketplace
Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules.
TencentCloudBase/CloudBase-AI-Toolkit
[Deprecated] Optional advanced tool for complex data modeling.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
maziyarpanahi/openmed
Fills in a model card for an OpenMed clinical NER or de-identification model from its evaluation reports: intended use, metrics, subgroups and limitations.
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
maziyarpanahi/openmed
Suggests candidate ICD-10-CM diagnosis and ICD-10-PCS procedure codes for clinical text extracted by OpenMed, with rationale for a certified coder to review.
maziyarpanahi/openmed
Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.
maziyarpanahi/openmed
Finds social risks such as housing instability or food insecurity in clinical notes and proposes matching ICD-10-CM Z-codes for a coder to confirm.
Categories
Links entities extracted by OpenMed to UMLS Metathesaurus CUIs using the USER'S OWN UTS API key, with nothing from the Metathesaurus bundled or cached. Linking Umls Concepts is an agent skill from maziyarpanahi/openmed. Links entities extracted by OpenMed to UMLS Metathesaurus CUIs using the USER'S OWN UTS API key, with nothing from the Metathesaurus bundled or cached.
Linking Umls Concepts fits situations like: the user wants to normalize concepts across vocabularies to a single CUI; resolve synonyms via the UMLS; filter by semantic type; cross-walk between SNOMED CT.
Run `npx skills add maziyarpanahi/openmed --skill linking-umls-concepts -a claude-code`. Or copy the skill folder (skills/linking-umls-concepts in maziyarpanahi/openmed) into .claude/skills/linking-umls-concepts in your project. Claude Code loads it when a task matches its description.
Run `npx skills add maziyarpanahi/openmed --skill linking-umls-concepts -a codex`. Or copy the skill folder (skills/linking-umls-concepts in maziyarpanahi/openmed) into .agents/skills/linking-umls-concepts in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maziyarpanahi/openmed --skill linking-umls-concepts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/linking-umls-concepts, .gemini/skills/linking-umls-concepts, .github/skills/linking-umls-concepts and .opencode/skills/linking-umls-concepts in your project.
Going by SKILL.md and its folder, Linking Umls Concepts needs credentials named API_KEY and UTS_API_KEY. Our summary lists: Python 3; A credential in API_KEY; A credential in UTS_API_KEY.
SKILL.md names 6 domains. In commands or code: uts-ws.nlm.nih.gov; the agent is likely to contact it when it follows the instructions. As links in the text: nlm.nih.gov, uts.nlm.nih.gov, documentation.uts.nlm.nih.gov, lhncbc.nlm.nih.gov and github.com. This is read from the text; nothing was executed.
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.
Linking Umls Concepts is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Linking Umls Concepts: Walkthrough (alexanderop/walkthrough, 141 stars), Managedcode Orleans Graph (managedcode/dotnet-skills, 486 stars), Datamodellm (nimbalyst/nimbalyst, 1.9k stars) and Drizzle Erd (hiroppy/mf-dashboard, 418 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,506 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 11, 2026.
Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.