method-clif skill
✓ VerifiedEnforces Common Longitudinal ICU data Format rules including mCIDE versions, Parquet usage, UTC datetimes, and PHI protection for ICU data analysis.
- GitHub stars
- 6
- Files
- 7
- Last commit
- Oct 31, 2026
- License
- MIT
- Allowed tools
- —
What does the method-clif skill do?
method-clif enforces Common Longitudinal ICU data Format rules including mCIDE versions, Parquet usage, UTC datetimes, and PHI protection for ICU data analysis.
Summary generated from the skill's SKILL.md.
About the method-clif skill
Researchers and developers working with intensive care unit data can use this skill to enforce the Common Longitudinal ICU data Format (CLIF) standards. It ensures that analysis workflows respect specific mCIDE versions, use Parquet files, and maintain UTC datetimes while protecting sensitive patient information. The skill is designed for projects that contain CLIF tables, mCIDE content, or specific configuration files like CLIF_CLAUDE.md.
When activated, the skill loads a specialized ruleset and emits a signal that instructs other analysis tools to follow CLIF-specific schemas and vocabularies. It acts as a guardrail for protected file paths, requiring authorization from a designated Point of Contact before any edits are made to critical directories. It does not perform de-identification itself but provides the necessary guidance and language-specific recipes for Python and R users to maintain data integrity and consortium compliance.
What an agent can do with it
- 1Enforce ICU data standardsEnsure all ICU data analysis follows specific mCIDE versions and Parquet usage rules.
- 2Protect sensitive data pathsPrevent unauthorized edits to critical mCIDE or project configuration files.
- 3Provide language-specific code recipesAccess verified Python or R code templates for handling CLIF datasets.
- 4Validate project versioningConfirm whether a project should use the 2.1 or 3.0 version family for mCIDE and CLIF.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the method-clif skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the method-clif skill in Plugin
/plugin marketplace add sajor2000/methodsmith /plugin install methodsmith@methodsmith
Install the method-clif skill in Claude Code
~/.claude/skills/method-clif/SKILL.md
$ npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif ~/.claude/skills/method-clifInstall the method-clif skill in Claude Code (project)
.claude/skills/method-clif/SKILL.md
$ npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif .claude/skills/method-clifInstall the method-clif skill in Codex
~/.agents/skills/method-clif/SKILL.md
$ npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif ~/.agents/skills/method-clifInstall the method-clif skill in Gemini CLI
~/.gemini/skills/method-clif/SKILL.md
$ npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif ~/.gemini/skills/method-clifInstall the method-clif skill in Claude.ai
npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif method-clif && zip -r method-clif.zip method-clif # claude.ai → Customize → Skills → + → Create skill → Upload a skill → method-clif.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablesajor2000/methodsmith/plugins/methodsmith/skills/method-clif is public and reachablegithub.com/sajor2000/methodsmith/tree/HEAD/plugins/methodsmi ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-10-31github.com/sajor2000/methodsmith/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/sajor2000/methodsmith/blob/HEAD/plugins/methodsmi ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/sajor2000/methodsmith/blob/HEAD/plugins/methodsmi ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 199 linesgithub.com/sajor2000/methodsmith/blob/HEAD/plugins/methodsmi ↗Pass
SKILL.md
View on GitHubCLIF-Safe Profile
Skill Value
- Problem it solves: CLIF projects have consortium-specific invariants that generic EHR analysis workflows can violate.
- Use when: The repo has CLIF_CLAUDE.md, CLIF tables, mCIDE content, CLIF remotes, or the user asks for CLIF-specific analysis.
- Output: A CLIF activation signal plus language-specific CLIF workflow and validation guidance.
- Ask only if: Only when CLIF signals are weak or ambiguous and activation could be wrong.
- Do not do: Do not treat generic OMOP, claims, or EHR projects as CLIF without evidence.
- Interaction: Check repo/config/chat evidence first. Ask one decision-changing question at a time; use the current harness's blocking question UI when available, otherwise present numbered choices and wait.
Loads the CLIF (Common Longitudinal ICU data Format) ruleset for CLIF consortium or CLIF-derived projects so the rest of the method-* lifecycle respects CLIF schema, vocabularies, project layout, and PHI rules instead of treating CLIF like a generic Parquet dataset.
Core source: Treat https://clif-icu.com/ as the authoritative public CLIF source for the data dictionary, mCIDE context, tools, and consortium status. Use GitHub repositories for implementation details only after anchoring the project to the CLIF site and declared data dictionary version.
When this skill activates
Auto-activate on one strong signal or two or more weak signals:
Strong signals:
- A file named
CLIF_CLAUDE.mdexists at the repo root or~/CLIF_CLAUDE.md - Git remote URL contains
clif-consortium,Common-Longitudinal-ICU-data-Format, orclif-icu - The user explicitly says "CLIF", "mCIDE", "clif-icu", or "common longitudinal icu data format"
- Manual:
method-clif(forces activation)
Weak signals (require 2+):
- A
mCIDE/directory exists WORKFLOW.mdexists at the repo root- Files named
clif_*.parquetexist (e.g.,clif_vitals.parquet,clif_respiratory_support.parquet) - Code references CLIF-specific table names:
respiratory_support,medication_admin_continuous,patient_assessments,intake_output config/config.jsoncontains atables_pathfield pointing to parquet files
NOT activation signals (too generic):
patient.parquetalone (OMOP hasperson, but custom EHR may usepatient)hospitalizationalone (generic term)vitalsorlabsalone (generic terms)renv.lockalone (any R project)WORKFLOW.mdalone (any project with a workflow doc)adtalone (ADT feeds exist outside CLIF)
When signals are ambiguous (only weak signals, or the user mentions a CLIF table name in a non-CLIF context), ask one question before activating:
"Detected possible CLIF signals but this may not be a CLIF project. Is this a CLIF consortium or CLIF-derived project?"
method-clif --off forces deactivation for the session.
Select the CLIF and mCIDE family
Read references/version-families.md before selecting a family. Inspect, in
order, an explicit --version, stack_profile.clif.data_dictionary_version and
stack_profile.clif.mcide_version in local config, a project data-dictionary declaration,
and a documented source manifest. Treat --version as a full direct call:
`method-clif --version 2.1.0` -> CLIF 2.1.0 + mCIDE 2.1.0
`method-clif --version 3.0.0` -> CLIF 3.0.0 + mCIDE 3.0.0
An accepted direct call emits selection=explicit and needs no extra version
question. If it conflicts with an explicitly declared local or project pair,
show the mismatch and ask which source is intended before category work. Never
infer 3.0.0 merely from an mCIDE/ directory, a table name, or missing
language evidence.
When no matching pair is declared, signals conflict, or only one version is known, ask this blocking question before generating category filters or validating vocabularies. Follow the interaction contract in Skill Value; if the blocking question UI is unavailable, present the same numbered choices in chat and wait. Never silently choose a family.
Which CLIF and mCIDE version family should this project use?
- CLIF 2.1 + mCIDE 2.1 — the 2.1 structured-dictionary release family (confirm the current release at https://clif-icu.com/).
- CLIF 3.0 + mCIDE 3.0 — multimodal family, still pre-release on clif-icu.com; use only when the project explicitly targets it.
Reject an undeclared mixed pair such as CLIF 3.0 with mCIDE 2.1. Record a project-specific exception only after the user supplies its source and states which vocabulary is authoritative.
When selected, print one acknowledgment line and emit the handoff signal:
[method-clif] CLIF profile active (data dictionary v<dd-version>, mCIDE v<mcide-version>); protected paths read-only without POC sign-off.
__CE_CLIF__ active=true version=<dd-version> mcide_version=<mcide-version> selection=<explicit|declared|selected> strict=<true|false> rules=references/clif-rules.md
When --off is passed, emit __CE_CLIF__ active=false so downstream skills resume default behavior.
Prerequisites
None; no stack profile is required. Resolve the repository root before reading optional config:
!git rev-parse --show-toplevel 2>/dev/null || true
Use the resolved absolute path or resolve it at runtime, then read <repo-root>/.methodsmith/config.local.yaml with the native file-read tool. In a linked worktree, fall back to the main checkout when the config is absent.
Core workflow
Step 1: Detect or confirm
If auto-detection signals are present, activate silently and print the acknowledgment line. If signals are ambiguous (e.g., user mentions CLIF but is in an unrelated repo), ask one question:
"Detected CLIF references but the working directory is
<dir>. Activate CLIF profile for this session?"
Step 2: Load the rule set and language envelope
Load references/clif-rules.md (always), references/mcide-vocab.md (when the session touches _category columns or vocabulary checks), and references/poc-table.md (when an edit or PR is proposed against a protected path).
Before reading patient-level data, code output, logs, or tracebacks, apply the
sensitive-data boundary in references/clif-rules.md. CLIF's federated rules (no
patient-level tables leave the site; every shared cell has more than 10 patients) apply
in every mode.
Then ensure __CE_LANG__ exists:
- If
__CE_LANG__is already present in chat context, consume it as-is. - Otherwise load the
method-language-detectskill and use its emitted envelope. - If detection returns
primary=unknown, route CLIF code guidance to both recipe files.
Step 3: Read the project's local override (optional)
If the resolved config contains a clif: block under stack_profile:, merge it over the defaults. Recognized keys:
stack_profile:
profile: clif
clif:
data_dictionary_version: "2.1.0" # selected family: 2.1.0 or 3.0.0
mcide_version: "2.1.0" # must match data_dictionary_version unless an authoritative exception is documented
parquet_only: true # refuse CSV/Feather for CLIF tables
protected_paths: # in addition to the built-in list
- mCIDE/**
- ddl/**
- WORKFLOW.md
poc_table_path: ./CLIF_POCs.md # optional override; defaults to references/poc-table.md
strict: true # block on any rule violation rather than warn
Step 4: Emit the signal
Emit the __CE_CLIF__ line (canonical envelope below) alongside __CE_LANG__; downstream method-* skills read both in their step-0 context scan. This skill never modifies the user's repo; it only loads rules and emits signals.
Step 5: On protected-path edits
When the session is about to edit any protected_paths entry, the skill's guardrail runs before the edit:
-
Resolve the responsible POC by matching the file path against
references/poc-table.md(e.g.,mCIDE/respiratory_support/**-> Nicholas Ingraham,@ingra107). -
Refuse the edit unless the prompt contains a phrase indicating POC authorization, e.g.,
POC: @ingra107 approvedor--poc-approved. -
If the user insists without authorization, write the proposed change to
analysis/clif-protected-edits/<timestamp>-<file>.diffand surface a single-line warning:[method-clif] BLOCKED: edit to mCIDE/respiratory_support/respiratory_support_mode_categories.csv requires POC sign-off (Nicholas Ingraham, @ingra107). Diff staged at analysis/clif-protected-edits/2026-04-29T18-00-00-respiratory_support_mode_categories.diff
What this skill does NOT do
- Does not edit files in the upstream CLIF repo on the user's behalf
- Does not contact POCs (it only cites the right person)
- Does not replace
method-data-qa,method-cohort, etc. — it just changes how those skills behave when CLIF mode is active - Does not de-identify data or run PHI scans (dispatch the
method-phi-leak-revieweragent)
Handoff signal (canonical envelope)
__CE_CLIF__ active=<true|false> version=<dd-version> mcide_version=<mcide-version> selection=<explicit|declared|selected> strict=<true|false> rules=<path-to-clif-rules.md>
Consumers (other method-* skills) parse active=true to switch to CLIF behavior; they parse version= and mcide_version= as one selected family before validating categories; they parse strict=true to escalate warnings into refusals. If mcide_version= is absent, stop category validation and route back to this skill rather than assuming the v2.1 cache applies.
Code recipes (drawn from the upstream CLIF org)
When the user is writing CLIF analysis code, surface canonical recipes from the upstream code-of-record packages:
- Python users (
__CE_LANG__ primary=python): loadreferences/clifpy-recipes.md— core recipes verified againstCommon-Longitudinal-ICU-data-Format/clifpy2.1.0 (uv projects useuv add clifpy; otherwisepython3 -m pip install --upgrade clifpy). CoversClifOrchestratorsetup, schema validation, wide datasets, outlier handling, stitching, medication unit conversion, SOFA, and the data-quality assessment (DQA) pattern. For any otherclifpycall, SOFA-2, ASE, timezone handling, 3.0 migration, or a review of existingclifpycode, load themethod-clifpyskill. - R users (
__CE_LANG__ primary=r): loadreferences/r-template-recipes.md— recipes drawn fromCommon-Longitudinal-ICU-data-Format/CLIF-Project-Template(R) and the canonicalcode/templates/R/layout. Coversrenvbootstrap,arrow::open_dataset()reads, cohort → QC → outlier handling → analysis, and the separate intermediate/final output paths. __CE_LANG__ primary=bothorunknown: surface both files so the agent can choose.
For a new consortium project or a structural check of a template-derived repository, route to the method-clif-template skill. For a full audit of a CLIF project repository (environment pins, config, clifpy usage, timezone, output disclosure, reproducibility), route to the method-clif-audit skill. This skill remains the CLIF version, vocabulary, and protected-path guardrail.
For formal site-to-lead effect pooling, model-output synthesis, or a literature
meta-analysis, use method-clif-meta-analysis. A shared CLIF schema does not establish
comparable estimands or independent site estimates.
References
Read each file at the step that names it (backtick paths, loaded on demand):
references/clif-rules.md— Core rules (Parquet, UTC datetimes, mCIDE vocab, project layout, sensitive-data boundary, template workflow). Read at Step 2, always.references/version-families.md— Selection and migration contract for CLIF/mCIDE 2.1 and 3.0. Read before selecting a version family or validating v3 categories.references/mcide-vocab.md— Cached 2.1 allow-lists plus pointers to authoritative mCIDE CSV sources; never use it for v3.references/poc-table.md— CLIF table / mCIDE subdirectory to responsible POC (name and GitHub handle), for the protected-path guardrail. Names and handles only; no contact addresses are cached.references/clifpy-recipes.md— Core Python recipes (ClifOrchestrator, wide dataset, outliers, stitching, units, SOFA, DQA). Load when generating Python CLIF code; usemethod-clifpyfor the full verified API.references/r-template-recipes.md— R recipes (arrow, cohort, QC, meta-analysis, propensity, federated). Load when generating R CLIF code.
Files in this skill
7method-clif skill questions
How do I install the method-clif skill in Claude Code?
Run npx degit sajor2000/methodsmith/plugins/methodsmith/skills/method-clif ~/.claude/skills/method-clif. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the method-clif skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should the CLIF skill be activated?
It should auto-activate on one strong signal (like a CLIF_CLAUDE.md file) or two or more weak signals (like a mCIDE/ directory and clif_*.parquet files).
Can I force the CLIF skill to turn off?
Yes, you can use the command method-clif --off to force deactivation for the session.
What happens if I try to edit a protected path in a CLIF project?
The skill will block the edit unless the prompt contains POC authorization, such as 'POC: @username approved'.