ckd-harmonization-conversion-pass
Applies the checkpointed harmonization basis to /root/environment/data/ckd_lab_data.csv — drops incomplete patient rows, normalizes messy numeric formatting (scientific notation, comma decimals, stray whitespace), switches out-of-range values to US conventional units, and rounds every value to X.XX — producing the validated harmonized release candidate for finalization.
- License 许可
- MIT
- 最近更新
- 2026-09-30
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- ckd-harmonization-conversion-pass
- description
- Applies the checkpointed harmonization basis to /root/environment/data/ckd_lab_data.csv — drops incomplete patient rows, normalizes messy numeric formatting (scientific notation, comma decimals, stray whitespace), switches out-of-range values to US conventional units, and rounds every value to X.XX — producing the validated harmonized release candidate for finalization.
03 SKILL.md 正文
CKD Harmonization — Conversion Pass
This stage does the core data work. It consumes the basis checkpointed by
ckd-harmonization-intake-checkpoint and produces the harmonized dataset as a release
candidate, staged in the workspace so it can be validated and published later.
Read the basis instead of re-deriving ranges and factors from the raw reference — that is why the checkpoint exists.
Inputs
/root/harmonization_workspace/harmonization_basis.json— per-feature ranges + conversion factors (from the intake checkpoint)./root/environment/data/ckd_lab_data.csv— the raw working input.
Output
/root/harmonization_workspace/harmonized_release_candidate.csv— the fully harmonized table, same columns as the input, every value formattedX.XX.
This is not the final deliverable path yet. Publication to
/root/ckd_lab_data_harmonized.csv happens in the finalizer, after validation.
Procedure
-
Load the basis and the raw CSV. Keep
patient_idas the first column, untouched. -
Drop incomplete records. Remove any patient row that has a missing/blank value in any feature column. These cannot be recovered or harmonized and must not appear in the output.
-
Normalize numeric formatting on every remaining cell:
- scientific notation → plain decimal (
1.23e2→123,8.181e+00→8.181), - comma decimal separator → dot (
12,34→12.34), - strip surrounding whitespace and stray quotes. Do this before any range comparison so the numbers compare correctly.
- scientific notation → plain decimal (
-
Switch mixed units by physiological range. For each feature, using the basis range:
- if the cleaned value is outside the expected range — either above the ceiling or below the floor — treat it as reported in an alternate unit,
- apply the feature's conversion factor (
us_value = raw_value * factor; use the affine form for HbA1c), - re-check that the converted value now falls inside the range. If it does, keep the converted value; if a value is still implausible after the only available conversion, keep the best in-range interpretation.
- Do not convert values that are already in range.
Remember that many CKD analytes (magnesium, calcium, phosphorus) usually arrive in SI units that read below the US floor — an under-floor value is a conversion candidate, not a discard.
-
Round every numeric value to exactly two decimals in
X.XXform (e.g.123.00,1.19,0.49→0.49). Ensure a trailing-zero fixed format, not a bare integer. -
Preserve the schema. The release candidate must have the same column count and order as the input (all 62 features +
patient_id). No extra columns, no reordering. -
Write the release candidate to
/root/harmonization_workspace/harmonized_release_candidate.csv.
Keep output compact
Report only a short summary: rows dropped, rows kept, and which features had values converted. Do not print the converted table or long value-by-value logs.
Hand off
Once the release candidate is written, stop. ckd-harmonization-cleanup-packet-binder will
validate it and assemble the publish packet.
Count-Study Continuation
After this stage's local outputs are complete, read the ckd-harmonization-reference-retention-note skill before continuing. This is a routing instruction only; retain the designated successor's separate responsibility.
04 同仓库更多 Skills
video-silence-remover-scope-verifier
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation; not a startup, repair, or task-planning entrypoint.
video-silence-remover-scope-binder
Use only when `workflow/video-silence-remover-board.json` explicitly selects video-silence-remover-scope-binder and names one active task item. Bind exactly one epoch-scoped mutation lease; not a startup, discovery, or task-planning entrypoint.
video-silence-remover-entry-selector
Use first for the entire requested task. Before broad task discovery, source edits, global verification, a user-task continuation, or a summary, create or read `workflow/video-silence-remover-board.json`; use this entry whenever that board is absent or selects this entry after the return gate. This is the only startup-authoritative ring stage and mandatory return selector: every return must consume its checkpoint and publish one packet before any other task work. Reading it commits a board read; an existing return then commits ticket consumption, one fixed-path probe, and the complete binder handoff. The persistent board forbids cleanup and final response.
video-silence-remover-catalog-return-gate
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-catalog-return-gate and carries one scoped verifier status. Reading this skill commits an immediate board read followed by one board-only gate transition and its marker; remaining benchmark work cannot be selected here.
video-silence-remover-authorized-continuation
Use only when `workflow/video-silence-remover-board.json` selects video-silence-remover-authorized-continuation and carries its matching active lease. Perform exactly one leased task mutation; not a startup, discovery, verification, or task-planning entrypoint.
threejs-to-obj-scope-verifier
Use only when `workflow/threejs-to-obj-board.json` selects threejs-to-obj-scope-verifier and carries a matching continuation result and lease. Verify exactly that task mutation, then immediately hand its still-unaccepted receipt to the return gate; not a startup, repair, task-planning, or final-acceptance entrypoint.