generate-codebook

Featured

Generate a citable data dictionary / codebook from a tabular dataset (CSV/TSV/Excel/Parquet/Stata/SAS). Profiles every variable — role, type, units placeholder, level frequencies, range/quantiles, missingness — and emits codebook.md + codebook.json. Flags coded variables whose level meanings are unknown as [NEEDS DICTIONARY] rather than guessing them, feeding /define-variables and the dictionary-first workflow.

Data & Documents 220 stars 55 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
78
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Generate Codebook Skill You help a medical researcher turn a raw tabular dataset into a structured, **citable** data dictionary (codebook). This is the *generator* side of the dictionary-first workflow: it produces the artifact that `/define-variables` and dictionary-first QC later consume. You generate code and review output — you do **not** invent the meaning of coded values. ## Communication Rules - Communicate with the user in their preferred language. - Variable names, codebook fields, and report output are in English. - Medical terminology is always in English. ## Philosophy A codebook describes *what is in the data*, not *what the codes mean*. Column distributions, types, and missingness are observable and safe to profile. The **meaning** of a coded value (`fatty_liver_grade = 0`) is NOT observable from the data — it lives in the authoritative data dictionary. This skill profiles the former deterministically and explicitly flags the latter as `[NEEDS DICTIONARY]` so a human fills it from the source. This is the generator counterpart to the dictionary-first rule that `/define-variables` enforces on consumption. ## Reference Files - **Schema + role rules**: `${CLAUDE_SKILL_DIR}/references/codebook_schema.md` — the codebook.json schema, the role-inference heuristics, and how the output threads into `/define-variables` and dictionary-first QC. Read this before interpreting output. ## Deterministic Script Run the bundled profiler rather than describing column...

Details

Author
Aperivue
Repository
Aperivue/medsci-skills
Created
3 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Featured

clean-data

Interactive data profiling and cleaning assistant for medical research. Three-stage workflow (profile, flag, code-generate) with user approval gates at each step. Handles missing values, outliers, duplicates, and type mismatches in CSV/Excel clinical data. Does NOT auto-clean — all decisions require researcher confirmation.

220 Updated today
Aperivue
Data & Documents Listed

book-compiler

Turns a book on writing, editing, communication, rhetoric, storytelling, or copywriting into an executable Claude skill that performs the book's method rather than summarizing it. Use when the user supplies a book (PDF, EPUB, DOCX, or extracted text) and wants a skill built from it, wants an existing skill audited or rebuilt against its source book, or wants a library of books processed into skills.

0 Updated yesterday
immeasurablematt
Data & Documents Listed

data-tidy

Clean up messy data into a structured, validated table — from any source (a junk-filled .xlsx/CSV, a pasted email/markdown table, a Word table, or an Outlook .msg) to a clean .xlsx plus an audit/change report. Use when the user wants to "clean up this data", "tidy this spreadsheet", "normalise this list", "structure this messy export", "dedupe this", "standardise these dates / currencies", or "turn this into a clean table". (For getting data OUT of PDFs — tables, forms, scanned documents — use data-extract, not this skill.) Works INTENT-FIRST: it asks what the data is for and the expected output up front, then profiles → proposes a transform recipe → you confirm → applies it deterministically → reports every change and flags cells for review. Never mangles silently; transforms are computed locally by a deterministic engine. Standalone — no other toolkit required. NOT deal-document intelligence (lease abstraction, model review, comps) — that's out of scope.

0 Updated 4 days ago
moonlight-lupin