Clinical Trials Database
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
Write SNOMED CT Expression Constraint Language (ECL) queries to search and constrain concepts.
$ npx skills add aehrc/pathling --skill snomed-ecl -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aehrc/pathling snomed-ecl --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/aehrc/pathling.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/snomed-ecl .claude/skills/snomed-ecl && 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 "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .claude/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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/aehrc/pathling/tree/main/.agents/skills/snomed-eclType 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 aehrc/pathling --skill snomed-ecl -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aehrc/pathling snomed-ecl --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aehrc/pathling.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/snomed-ecl .agents/skills/snomed-ecl && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .agents/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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 aehrc/pathling --skill snomed-ecl -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aehrc/pathling snomed-ecl --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aehrc/pathling.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/snomed-ecl .cursor/skills/snomed-ecl && 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 "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .cursor/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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/aehrc/pathling.git --path .agents/skills/snomed-ecl--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 aehrc/pathling --skill snomed-ecl -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aehrc/pathling snomed-ecl --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aehrc/pathling.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/snomed-ecl .gemini/skills/snomed-ecl && 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 "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .gemini/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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 aehrc/pathling snomed-eclInstalls 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 aehrc/pathling --skill snomed-ecl -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aehrc/pathling.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/snomed-ecl .github/skills/snomed-ecl && 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 "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .github/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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 aehrc/pathling --skill snomed-ecl -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aehrc/pathling snomed-ecl --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aehrc/pathling.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/snomed-ecl .opencode/skills/snomed-ecl && 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 "snomed-ecl" agent skill from https://github.com/aehrc/pathling/tree/main/.agents/skills/snomed-ecl into .opencode/skills/snomed-ecl/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "snomed-ecl", 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.
snomed-eclWrite SNOMED CT Expression Constraint Language (ECL) queries to search and constrain concepts.
Snomed Ecl is an agent skill from aehrc/pathling. Write SNOMED CT Expression Constraint Language (ECL) queries to search and constrain concepts. Use when writing ECL queries, constraining SNOMED concepts, filtering clinical terminology, or creating FHIR value sets with ECL. Trigger keywords include ECL, Expression Constraint Language, SNOMED query, SNOMED expression, ECL syntax, descendant of, ECL v2, implicit value set, FHIR value set, terminology server.
Its SKILL.md is about 5k 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 Research & Science, covering Clinical and healthcare research. The repository describes itself as: Tools that make it easier to use FHIR and clinical terminology within data analytics, built on Apache Spark. The licence is Apache-2.0.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 56a3b4a. 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 json and xml).
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:
snomed.infohl7.orgAlso links to:
docs.snomed.orgontoserver.csiro.auterminology.hl7.orgFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Snomed Ecl loads about 5k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 1,497 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 aehrc/pathling at commit 56a3b4a, republished under its Apache-2.0 licence (© aehrc). 1,497 words, ~4,993 tokens.
.claude/skills/snomed-ecl/SKILL.md (or your agent's skills folder).You are an expert in SNOMED CT Expression Constraint Language (ECL), a formal syntax for representing computable rules that define bounded sets of clinical meanings.
ECL is used to:
ECL queries return zero or more SNOMED CT concept codes with no duplicates. Evaluations are version-specific to the SNOMED CT edition being used.
Concepts can be referenced by concept ID with optional display term:
73211009
73211009 |Diabetes mellitus|Display terms are for readability only and must be enclosed in pipe characters |.
*Returns all active and inactive concepts.
^ 32570481000036109Returns all concepts that are members of the specified reference set.
ECL provides operators to navigate the SNOMED CT hierarchy:
| Operator | Meaning | Example |
|---|---|---|
< | Descendants only (excludes concept itself) | < 73211009 |
<< | Descendants or self (includes concept itself) | << 73211009 |Diabetes mellitus| |
<! | Immediate children only | <! 404684003 |
<<! | Immediate children or self | <<! 404684003 |
> | Ancestors only (excludes concept itself) | > 73211009 |
>> | Ancestors or self (includes concept itself) | >> 73211009 |
>! | Immediate parents only | >! 40541001 |
>>! | Immediate parents or self | >>! 40541001 |
Find all types of diabetes:
<< 73211009 |Diabetes mellitus|Find immediate subtypes of a disease:
<! 64572001 |Disease|Find all ancestors of appendicitis:
> 74400008 |Appendicitis|Combine constraints using boolean operators:
| Operator | Function | Example |
|---|---|---|
AND | Intersection | << 19829001 AND << 301867009 |
OR | Union | << 73211009 OR << 38341003 |
MINUS | Difference | << 73211009 MINUS << 46635009 |
Find procedures on the heart:
<< 71388002 |Procedure| AND << 80891009 |Heart structure|Find diabetes or hypertension:
<< 73211009 |Diabetes mellitus| OR << 38341003 |Hypertensive disorder|Find all diabetes except type 1:
<< 73211009 |Diabetes mellitus| MINUS << 46635009 |Type 1 diabetes mellitus|Constrain concepts based on their attributes (relationships):
< 19829001 |Disorder of lung| : 116676008 |Associated morphology| = 79654002 |Edema|This finds lung disorders with edema as the associated morphology.
Both the attribute type and value can use hierarchy operators:
<< 404684003 |Clinical finding| :
<< 47429007 |Associated with| = << 267038008 |Edema|This finds clinical findings with any "associated with" attribute whose value is edema or a subtype of edema.
Use commas to separate multiple attribute constraints:
<< 404684003 |Clinical finding| :
<< 363698007 |Finding site| = << 39057004 |Pulmonary valve structure|,
<< 116676008 |Associated morphology| = << 415582006 |Stenosis|This finds clinical findings at the pulmonary valve site with stenosis morphology.
Use curly braces to specify that attributes must be in the same role group:
<< 125605004 |Fracture of bone| :
{
<< 363698007 |Finding site| = << 272673000 |Bone structure of tibia|,
<< 116676008 |Associated morphology| = << 72704001 |Fracture|
}Constrain an attribute value by its own attributes:
<< 404684003 |Clinical finding| :
<< 363698007 |Finding site| = (
<< 91723000 |Anatomical structure| :
<< 272741003 |Laterality| = << 7771000 |Left|
)This finds clinical findings on the left side of the body.
Use dot notation to traverse relationships in reverse:
< 125605004 |Fracture of bone| . 363698007 |Finding site|This returns all the finding sites (anatomical structures) that are referenced by fracture concepts.
Specify how many times an attribute can occur:
<< 373873005 |Pharmaceutical / biologic product| :
[1..3] << 127489000 |Has active ingredient| = << 372687004 |Amoxicillin|The cardinality syntax is [min..max] where:
[n..n] - exactly n occurrences[n..*] - n or more occurrences[0..n] - zero to n occurrences[1..*] - one or more occurrencesECL supports filters to further constrain results based on concept properties:
<< 73211009 |Diabetes mellitus| {{ term = "type 1" }}This finds diabetes concepts whose term contains "type 1".
<< 404684003 |Clinical finding| {{ definitionStatus = defined }}This finds fully defined clinical findings.
* {{ module = 900000000000207008 |SNOMED CT core module| }}This finds concepts in the core SNOMED CT module.
* {{ effectiveTime = "20230131" }}This finds concepts with a specific effective time.
<< 73211009 {{ active = true }}This finds active diabetes concepts.
History supplements augment ECL query results with inactive SNOMED CT concepts that are semantically linked to the active results. As SNOMED CT evolves, previously recorded concepts become inactivated. Rather than querying older editions, history supplements use historical association reference sets to retrieve both active and relevant inactive concepts from the current edition.
History supplements use double braces with a plus sign prefix, appended after an ECL expression:
<< 195967001 |Asthma| {{ + HISTORY ( 900000000000527005 |SAME AS association reference set| ) }}The general form expands to a union of the original query with a member filter on the specified reference set:
@ecl_query OR ^ @history_refset_query {{ M targetComponentId = @ecl_query }}Three standardised profiles provide different precision/recall trade-offs:
| Profile | Keyword | Use case | Reference sets used |
|---|---|---|---|
| Minimum | HISTORY-MIN | Clinical decision support (high precision) | SAME AS |
| Moderate | HISTORY-MOD | Clinical research and audit (balanced) | SAME AS, REPLACED BY, WAS A, PARTIALLY EQUIVALENT TO |
| Maximum | HISTORY-MAX | Patient identification (high recall) | All subtypes of 900000000000522004 |Historical association reference set| |
HISTORY-MIN returns only one-to-one equivalent inactive concepts:
<< 195967001 |Asthma| {{ + HISTORY-MIN }}HISTORY-MOD includes replacements and partial equivalences:
<< 195967001 |Asthma| {{ + HISTORY-MOD }}HISTORY-MAX includes all possible historical associations:
<< 195967001 |Asthma| {{ + HISTORY-MAX }}The following forms are all equivalent to HISTORY-MAX:
<< 195967001 |Asthma| {{ + HISTORY-MAX }}
<< 195967001 |Asthma| {{ + HISTORY (< 900000000000522004 |Historical association reference set|) }}
<< 195967001 |Asthma| {{ + HISTORY (*) }}
<< 195967001 |Asthma| {{ + HISTORY }}You can specify a particular association reference set directly:
<< 195967001 |Asthma| {{ + HISTORY ( 900000000000527005 |SAME AS association reference set| ) }}Find all referral-to-service procedures, including inactive concepts that have a SAME AS association with an active match:
<< 306206005 |Referral to service| {{ + HISTORY-MIN }}Find all types of breast pain, including any historically associated inactive concepts:
<< 53430007 |Pain of breast| {{ + HISTORY-MAX }}MOVED FROM association reference set (900000000000525002) is not fully supported by the template pattern because its directional semantics are reversed.Operators are evaluated in this order (highest to lowest):
:()MINUSANDORUse parentheses to override default precedence:
(<< 73211009 |Diabetes mellitus| OR << 38341003 |Hypertensive disorder|)
AND << 404684003 |Clinical finding|ECL can be used to define implicit value sets when working with FHIR terminology servers. This allows you to dynamically define value sets using ECL expressions rather than enumerating all concepts.
FHIR terminology servers support ECL through implicit value set URLs with this pattern:
http://snomed.info/sct?fhir_vs=ecl/[uri-encoded-ecl]The ECL expression must be URI-encoded in the URL. For example:
http://snomed.info/sct?fhir_vs=ecl/%3C%3C%2073211009This represents the ECL expression << 73211009 (all descendants of diabetes mellitus).
You can specify a particular SNOMED CT edition and version:
http://snomed.info/sct/[edition]/version/[version]?fhir_vs=ecl/[uri-encoded-ecl]For example, to use the Australian edition:
http://snomed.info/sct/32506021000036107/version/20230831?fhir_vs=ecl/%3C%3C%2073211009When no edition or version is specified, the terminology server uses its default edition (or the International Edition if no default is configured).
You can define a ValueSet resource that uses ECL as a filter. This is the structured approach for defining ECL-based value sets:
JSON format:
{
"resourceType": "ValueSet",
"id": "diabetes-disorders",
"url": "http://example.org/fhir/ValueSet/diabetes-disorders",
"name": "DiabetesDisorders",
"title": "Diabetes disorders",
"status": "active",
"compose": {
"include": [
{
"system": "http://snomed.info/sct",
"filter": [
{
"property": "constraint",
"op": "=",
"value": "<< 73211009 |Diabetes mellitus|"
}
]
}
]
}
}XML format:
<ValueSet xmlns="http://hl7.org/fhir">
<id value="diabetes-disorders"/>
<url value="http://example.org/fhir/ValueSet/diabetes-disorders"/>
<name value="DiabetesDisorders"/>
<title value="Diabetes disorders"/>
<status value="active"/>
<compose>
<include>
<system value="http://snomed.info/sct"/>
<filter>
<property value="constraint"/>
<op value="="/>
<value value="<< 73211009 |Diabetes mellitus|"/>
</filter>
</include>
</compose>
</ValueSet>constraint to indicate an ECL expression.= for ECL constraints.ECL-based value sets can be used with standard FHIR terminology operations:
$expand operation:
GET [base]/ValueSet/$expand?url=http://snomed.info/sct?fhir_vs=ecl/%3C%3C%2073211009This expands the value set to return all concepts matching the ECL expression.
$validate-code operation:
GET [base]/ValueSet/$validate-code?url=http://snomed.info/sct?fhir_vs=ecl/%3C%3C%2073211009&code=44054006&system=http://snomed.info/sctThis checks if a specific code is valid within the ECL-defined value set.
All procedures on the heart:
{
"system": "http://snomed.info/sct",
"filter": [
{
"property": "constraint",
"op": "=",
"value": "<< 71388002 |Procedure| : << 363704007 |Procedure site| = << 80891009 |Heart structure|"
}
]
}Pharmaceutical products containing paracetamol:
{
"system": "http://snomed.info/sct",
"filter": [
{
"property": "constraint",
"op": "=",
"value": "<< 373873005 |Pharmaceutical / biologic product| : << 127489000 |Has active ingredient| = << 387517004 |Paracetamol|"
}
]
}All active diabetes concepts:
{
"system": "http://snomed.info/sct",
"filter": [
{
"property": "constraint",
"op": "=",
"value": "<< 73211009 |Diabetes mellitus| {{ active = true }}"
}
]
}Use display terms for readability: Include |display term| after concept IDs to make queries self-documenting.
Prefer << over < when appropriate: If you want to include the concept itself in results, use << (descendants or self).
Be specific with attributes: Use the most specific attribute type that matches your intent.
Use role grouping when necessary: SNOMED CT uses role groups to disambiguate relationships. Use {} when you need attributes to be in the same group.
Consider cardinality: When the number of relationships matters, use cardinality constraints.
Test incrementally: Build complex queries incrementally, testing each part before adding more constraints.
Be aware of version differences: ECL results depend on the SNOMED CT version. Queries may return different results across versions.
Use filters for non-structural constraints: When constraining based on metadata (terms, status, modules), use filter syntax {{ }}.
Document complex queries: Add comments or documentation explaining the clinical intent of complex ECL expressions.
Validate against the specification: The current version is ECL v2.2. Ensure your implementation supports the features you're using.
Use ECL for dynamic FHIR value sets: When defining FHIR value sets, prefer ECL filters over enumerated concept lists for maintainability and automatic inclusion of new relevant concepts.
URI-encode ECL in URLs: When using implicit value set URLs, remember to properly URI-encode the ECL expression.
Use history supplements for retrospective queries: When querying patient data that may contain inactive concepts, use history supplements to capture historically associated concepts. Choose the profile (MIN, MOD, MAX) that matches the required precision/recall balance for your use case.
<< 64572001 |Disease| :
<< 363698007 |Finding site| = << 39057004 |Pulmonary valve structure|<< 71388002 |Procedure| :
<< 405813007 |Procedure site - Direct| = << 80891009 |Heart structure|,
<< 424226004 |Using device| = << 360062009 |Pacemaker|<< 373873005 |Pharmaceutical / biologic product| :
<< 127489000 |Has active ingredient| = << 387517004 |Paracetamol|<< 404684003 |Clinical finding| {{
effectiveTime = ("20230101".."20231231")
}}<< 404684003 |Clinical finding| :
<< 363698007 |Finding site| = (
<< 91723000 |Anatomical structure| :
<< 272741003 |Laterality| = << 24028007 |Right|
)| Pattern | ECL Syntax |
|---|---|
| Single concept | 73211009 |
| With display term | 73211009 |Diabetes mellitus| |
| Descendants | < 73211009 |
| Descendants or self | << 73211009 |
| Children only | <! 73211009 |
| Ancestors | > 73211009 |
| Ancestors or self | >> 73211009 |
| Parents only | >! 73211009 |
| Intersection | << 73211009 AND << 46635009 |
| Union | << 73211009 OR << 38341003 |
| Difference | << 73211009 MINUS << 46635009 |
| With attribute | << 404684003 : 116676008 = 79654002 |
| Multiple attributes | << 404684003 : attr1 = val1, attr2 = val2 |
| Grouped attributes | << 404684003 : { attr1 = val1, attr2 = val2 } |
| Nested constraint | << 404684003 : 363698007 = (<< 91723000 : 272741003 = 7771000) |
| With cardinality | << 373873005 : [1..3] 127489000 = 372687004 |
| Term filter | << 73211009 {{ term = "type 1" }} |
| Active filter | << 73211009 {{ active = true }} |
| Reference set members | ^ 32570481000036109 |
| History supplement | << 195967001 {{ + HISTORY-MIN }} |
© aehrc, 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 .agents/skills/snomed-ecl of aehrc/pathling.
Open the folder on GitHubat commit 56a3b4a
Snomed Ecl 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 |
|---|---|---|---|---|---|---|
| Snomed Ecl this skillaehrc/pathling | 137 | — | ~5k | Automated safety check: Pass | Apache-2.0 | |
| Clinical Trials Databasegoogle-deepmind/science-skills | 3.2k | 3 repos | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Model AssessmentAperivue/medsci-skills | 329 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Biomedical Analysis Dispatchxjtulyc/MedgeClaw | 617 | 1 repos | ~2k | Automated safety check: Pass | None | |
| Research Proposalluwill/research-skills | 858 | — | ~4.4k | Automated safety check: Notes | None |
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Aperivue/medsci-skills
A skill your agent uses when validating or evaluating a trained medical-imaging model.
xjtulyc/MedgeClaw
Routes bioinformatics, drug discovery, clinical and multi-omics tasks from a chat interface to Claude Code sessions running K-Dense scientific skills, with a live dashboard per task.
luwill/research-skills
A skill your agent uses when the user asks to write or draft a PhD / doctoral research proposal, research plan, 研究计划书, or 开题报告 — a forward-looking plan of background, gap, research questions…
LeonChaoX/qinyan-academic-skills
Write comprehensive literature reviews for medical imaging AI research.
aehrc/pathling
Expert guidance for implementing FHIR RESTful API servers and clients following the HL7 FHIR specification.
aehrc/pathling
Expert guidance for implementing FHIR Bulk Data Access (Flat FHIR) following the HL7 specification.
aehrc/pathling
Expert guidance for using the Databricks CLI to manage Databricks workspaces, clusters, jobs, pipelines, Unity Catalog, SQL warehouses, serving endpoints, secrets, bundles, and all other Databricks…
aehrc/pathling
FHIR RESTful search specification expert with access to the official HL7 search specification text and the formal SearchParameter registry.
aehrc/pathling
Design and generate comprehensive FHIRPath test suites using input domain partitioning and Pathling's DSL test framework.
aehrc/pathling
Expert guidance for implementing FHIR servers using HAPI FHIR Plain Server framework.
Categories
Write SNOMED CT Expression Constraint Language (ECL) queries to search and constrain concepts. Snomed Ecl is an agent skill from aehrc/pathling. Write SNOMED CT Expression Constraint Language (ECL) queries to search and constrain concepts.
Snomed Ecl fits situations like: writing ECL queries; constraining SNOMED concepts; filtering clinical terminology; creating FHIR value sets with ECL.
Run `npx skills add aehrc/pathling --skill snomed-ecl -a claude-code`. Or copy the skill folder (.agents/skills/snomed-ecl in aehrc/pathling) into .claude/skills/snomed-ecl in your project. Claude Code loads it when a task matches its description.
Run `npx skills add aehrc/pathling --skill snomed-ecl -a codex`. Or copy the skill folder (.agents/skills/snomed-ecl in aehrc/pathling) into .agents/skills/snomed-ecl 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 aehrc/pathling --skill snomed-ecl -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/snomed-ecl, .gemini/skills/snomed-ecl, .github/skills/snomed-ecl and .opencode/skills/snomed-ecl in your project.
SKILL.md names no scripts, command-line tools or credentials: Snomed Ecl is instructions for the agent only.
SKILL.md names 5 domains. In commands or code: snomed.info and hl7.org; the agent is likely to contact these when it follows the instructions. As links in the text: docs.snomed.org, ontoserver.csiro.au and terminology.hl7.org. 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.
Snomed Ecl is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5k tokens (SKILL.md is roughly 20k 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 Snomed Ecl: Clinical Trials Database (google-deepmind/science-skills, 3.2k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Model Assessment (Aperivue/medsci-skills, 329 stars) and Biomedical Analysis Dispatch (xjtulyc/MedgeClaw, 617 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
aehrc (a GitHub organization) maintains it in aehrc/pathling, which has 137 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 8, 2026.
Source: aehrc/pathling on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.