What problem does it solve? Deriving a CDISC-conformant ADSL dataset requires deep knowledge of admiral function selection, ADaMIG conventions, and protocol-specific decisions. This Skill encodes that expertise so an AI agent can generate audit-traceable, QC-ready R code from SDTM inputs and an ADaM specification. ## Core Features & Use Cases - Step-by-step ADSL workflow: Covers treatment dates, planned/actual treatment, disposition, baseline demographics, and population flags (SAFFL, ITTFL, PPROTFL) using idiomatic admiral functions like derive_vars_merged() and derive_vars_dt(). - CDISC convention enforcement: Applies flag conventions ("Y"/NA never "N"), date imputation rules, study day calculation, and one-record-per-subject assertions. - Human review annotations: Inserts # REVIEW: comments at every protocol-specific decision point so statisticians can verify population flag definitions and cut-points. - Use Case: A clinical programmer needs ADSL for a two-arm study. Provide DM, EX, DS from pharmaversesdtm plus the ADaM spec, and the agent generates sectioned R code with assertions, imputation flags, and xportr-based attribute application. ## Quick Start Ask the agent to derive an ADSL dataset from the DM, EX, and DS SDTM domains using admiral, following the study's ADaM specification for population flags and age groupings.