Agent skill

Admiral Bds

by RConsortium in RConsortium/pharma-skills

Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package.

MITAuto-check passed

Install Admiral Bds

skills CLI
$ npx skills add RConsortium/pharma-skills --skill admiral-bds -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install RConsortium/pharma-skills admiral-bds --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/RConsortium/pharma-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/admiral/admiral-bds .claude/skills/admiral-bds && rm -rf skills-src

Use ~/.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/

Facts

Skill name
admiral-bds
GitHub stars
120
Token cost
~3.6k tokens
SKILL.md length
998 words
Files
6 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package.

  • Works in 12 steps: Setup and domain loading → Merge ADSL backbone variables → Parameter assignment → …
  • A user needs to create a BDS findings dataset from SDTM domains
  • SKILL.md covers Inputs, Workflow, Common BDS errors to avoid and Output checklist
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Admiral Bds is an agent skill from RConsortium/pharma-skills. Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package. Initial scope covers ADVS (vital signs) and ADLB (laboratory values). Use when a user needs to create a BDS findings dataset from SDTM domains, derive parameter assignments, baseline values, change from baseline, visit windowing, or analysis flags, following CDISC ADaM conventions. Requires SDTM input data, an ADaM BDS specification, and a completed ADSL.

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `DESIGN.md`, `README.md` and `benchmarks/README.md`). Compatibility notes: Requires R with admiral, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset. Designed for use in a GxP-compliant environment…

The repository describes itself as: A collection of agent skills for BioPharma use cases GSDBench Intake https://rconsortium.github.io/pharma-skills/gsdbench-intake/. The licence is MIT.

When your agent uses it

  • A user needs to create a BDS findings dataset from SDTM domains
  • Derive parameter assignments
  • Baseline values
  • Change from baseline

Example prompts

  • “Use the admiral-bds skill to derive ADaM Basic Data Structure (BDS) datasets using the {admiral} R package”
  • “/admiral-bds”

Requirements

  • Compatibility (from SKILL.md): Requires R with admiral, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset. Designed for use in a GxP-compliant environment with access to SDTM datasets and an ADaM BDS specification.

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Setup and domain loading
  2. Merge ADSL backbone variables
  3. Parameter assignment
  4. Analysis value (AVAL, AVALC)
  5. Date derivation (ADT, ADTF, ADY)
  6. Visit assignment (AVISIT, AVISITN)
  7. Baseline flagging (ABLFL)
  8. Baseline values (BASE, BASEC)
  9. Change from baseline (CHG, PCHG)
  10. Analysis flags (ANL01FL)
  11. Dataset-specific: ADVS
  12. Dataset-specific: ADLB

What it can do on your machine

Read from SKILL.md and the folder at commit ae5d83b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are r).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires R with admiral, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset. Designed for use in a GxP-compliant environment with access to SDTM datasets and an ADaM BDS specification.

    From compatibility in the SKILL.md frontmatter.

Context cost

Admiral Bds loads about 3.6k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 998 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~112
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.8k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from RConsortium/pharma-skills at commit ae5d83b, republished under its MIT licence (© RConsortium). 998 words, ~3,639 tokens.

Download SKILL.mdSave it as .claude/skills/admiral-bds/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
admiral-bds
description
Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package. Initial scope covers ADVS (vital signs) and ADLB (laboratory values). Use when a user needs to create a BDS findings dataset from SDTM domains, derive parameter assignments, baseline values, change from baseline, visit windowing, or analysis flags, following CDISC ADaM conventions. Requires SDTM input data, an ADaM BDS specification, and a completed ADSL.
compatibility
Requires R with admiral, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset. Designed for use in a GxP-compliant environment with access to SDTM datasets and an ADaM BDS specification.
license
MIT
metadata.author
Navitas Data Sciences
metadata.version
0.1
metadata.pharmaverse
true
metadata.parent
admiral

admiral-bds

Shared conventions (library setup, pipe style, date rules, flag convention, # REVIEW: annotations, stopifnot() patterns) are defined in the parent ../SKILL.md. The workflow below is BDS-specific.

Derives CDISC-conformant BDS findings datasets using {admiral}. Outputs executable, QC-ready R code for ADVS and ADLB with full derivation traceability.

See bds-conventions reference for BDS variable conventions and record structure. See ../admiral-adsl/references/admiral-functions.md for function selection guidance shared across the admiral family.


Inputs

Before generating code, confirm the following are available or explicitly noted as absent:

InputRequiredNotes
VS or LBYesSource SDTM domain for ADVS or ADLB respectively
ADSLYesProvides TRTSDT, TRTEDT, treatment variables, and population flags
ADaM BDS specYesParameter list, derivation rules, visit windows, baseline definition
Study contextYesBaseline window, analysis flag definitions, visit map

If ADSL is absent, stop and request it. ADSL variables are required before baseline flagging and analysis flags can be derived.


Workflow

Follow these steps in order. Generate code section by section, not as a single block.

Step 1 — Setup and domain loading
r
library(admiral)
library(dplyr)
library(lubridate)
library(pharmaversesdtm)

# Load source domain — replace with vs/lb per dataset being derived
vs  <- pharmaversesdtm::vs
adsl <- <loaded ADSL dataset>

# Remove DOMAIN to avoid conflicts in derive_vars_merged() calls
vs <- select(vs, -DOMAIN)
Step 2 — Merge ADSL backbone variables

Bring required ADSL variables into the source dataset before any derivations. At minimum: TRTSDT, TRTEDT, population flags used as analysis set criteria.

r
# REVIEW: Confirm which population flags and ADSL variables are required by
#   the ADaM spec for this dataset. Add or remove from new_vars accordingly.
advs <- vs |>
  derive_vars_merged(
    dataset_add = adsl,
    by_vars     = exprs(STUDYID, USUBJID),
    new_vars    = exprs(TRTSDT, TRTEDT, TRT01P, TRT01PN, TRT01A, TRT01AN,
                        SAFFL, ITTFL)
  )
Step 3 — Parameter assignment

Map SDTM test codes to ADaM parameters. Use derive_vars_merged_lookup() with a lookup table driven by the ADaM spec. Do not use derive_vars_merged() here — it is not a lookup function and will not correctly handle unmatched records. Do not use case_when() or hardcoded if_else() chains.

r
# REVIEW: PARAMCD mapping must match the ADaM spec parameter list exactly.
#   Confirm VSTESTCD values in VS and align with ADaM PARAMCD conventions.
#   Remove parameters not in scope for this study.
param_lookup <- tibble::tribble(
  ~VSTESTCD, ~PARAMCD, ~PARAM,                    ~PARAMN,
  "SYSBP",   "SYSBP",  "Systolic Blood Pressure",  1L,
  "DIABP",   "DIABP",  "Diastolic Blood Pressure",  2L,
  "PULSE",   "PULSE",  "Pulse Rate",                3L,
  "WEIGHT",  "WEIGHT", "Weight",                    4L,
  "HEIGHT",  "HEIGHT", "Height",                    5L,
  "TEMP",    "TEMP",   "Temperature",               6L
)

advs <- advs |>
  derive_vars_merged_lookup(
    dataset_add = param_lookup,
    by_vars     = exprs(VSTESTCD),
    new_vars    = exprs(PARAMCD, PARAM, PARAMN)
  ) |>
  filter(!is.na(PARAMCD))   # drop records for out-of-scope tests

For ADLB, map from LBTESTCD. Include units in PARAM text per ADaM spec.

Step 4 — Analysis value (AVAL, AVALC)

AVAL is the numeric analysis value. AVALC is the character analysis value. Derive from the SDTM result variables, applying unit conversions if required.

r
advs <- advs |>
  mutate(
    AVAL  = VSSTRESN,    # numeric result in standard units
    AVALC = VSSTRESC,    # character result (for non-numeric or verbatim)
    AVALU = VSSTRESU     # analysis value units
  )

For ADLB, use LBSTRESN and LBSTRESC. If unit standardisation is required (e.g. converting mg/dL to mmol/L), apply before AVAL assignment and add a # REVIEW: comment referencing the protocol-specified units.

Step 5 — Date derivation (ADT, ADTF, ADY)
r
advs <- advs |>
  # ADT: analysis date from VSDTC
  derive_vars_dt(
    dtc             = VSDTC,
    new_vars_prefix = "A",
    date_imputation = "first",
    flag_imputation = "auto"
  ) |>
  # ADY: study day relative to TRTSDT
  derive_vars_dy(
    reference_date = TRTSDT,
    source_vars    = exprs(ADT)
  )

For ADLB, replace VSDTC with LBDTC.

Step 6 — Visit assignment (AVISIT, AVISITN)

Map SDTM VISIT/VISITNUM to ADaM AVISIT/AVISITN. Use the visit map from the ADaM spec — do not pass VISIT through directly to AVISIT.

r
# REVIEW: Visit map must come from the ADaM spec. The example below is
#   illustrative. Confirm VISIT names and AVISITN codes against the study CRF
#   and ADaM spec before use.
visit_map <- tibble::tribble(
  ~VISIT,        ~AVISIT,       ~AVISITN,
  "SCREENING 1", "Screening",   -1L,
  "BASELINE",    "Baseline",     0L,
  "WEEK 2",      "Week 2",       2L,
  "WEEK 4",      "Week 4",       4L,
  "WEEK 8",      "Week 8",       8L,
  "WEEK 16",     "Week 16",     16L,
  "WEEK 26",     "Week 26",     26L
)

advs <- advs |>
  derive_vars_merged_lookup(
    dataset_add = visit_map,
    by_vars     = exprs(VISIT),
    new_vars    = exprs(AVISIT, AVISITN)
  )

For studies with date-driven visit windowing (ADT-based assignment), use derive_vars_joined() with a window table that maps ADY ranges to analysis visits instead of the direct VISIT lookup above.

Step 7 — Baseline flagging (ABLFL)

The baseline record is the last non-missing, non-excluded record on or before TRTSDT for each subject-parameter combination. Use restrict_derivation() + derive_var_extreme_flag() — do not flag baseline with mutate() or filter().

r
# REVIEW: Baseline window definition is protocol-specific. Confirm whether
#   the baseline is the last pre-dose record (ADT <= TRTSDT), last on-or-before
#   treatment start, or a specific visit (e.g. DAY 1 only). Adjust filter below.
advs <- advs |>
  restrict_derivation(
    derivation = derive_var_extreme_flag,
    args = params(
      by_vars  = exprs(STUDYID, USUBJID, PARAMCD, BASETYPE),
      order    = exprs(ADT, AVISITN),
      new_var  = ABLFL,
      mode     = "last"
    ),
    filter = ADT <= TRTSDT & !is.na(AVAL)
  )

If multiple baseline definitions apply (e.g. last pre-dose and last pre-treatment), add a BASETYPE variable to distinguish them before flagging.

Step 8 — Baseline values (BASE, BASEC)

Derive BASE and BASEC from the flagged baseline records.

r
advs <- advs |>
  derive_var_base(
    by_vars  = exprs(STUDYID, USUBJID, PARAMCD, BASETYPE),
    source_var = AVAL,
    new_var    = BASE
  ) |>
  derive_var_base(
    by_vars    = exprs(STUDYID, USUBJID, PARAMCD, BASETYPE),
    source_var = AVALC,
    new_var    = BASEC
  )
Step 9 — Change from baseline (CHG, PCHG)

Derive after BASE is present. CHG and PCHG are NA for the baseline record itself and for any post-baseline record where BASE is NA.

r
advs <- advs |>
  derive_var_chg() |>    # CHG = AVAL - BASE
  derive_var_pchg()      # PCHG = CHG / BASE * 100; NA if BASE = 0 or NA

If CHG is not in scope per the ADaM spec (e.g. for categorical parameters), omit these calls and add a note in the code.

Step 10 — Analysis flags (ANL01FL)

ANL01FL flags the records used in primary analysis. The definition is protocol- and study-specific. Derive with restrict_derivation().

r
# REVIEW: ANL01FL definition is protocol-specific. The condition below
#   (on-treatment, non-baseline) is a common starting point. Confirm against
#   the SAP before use.
advs <- advs |>
  restrict_derivation(
    derivation = derive_var_extreme_flag,
    args = params(
      by_vars  = exprs(STUDYID, USUBJID, PARAMCD),
      order    = exprs(ADT, AVISITN),
      new_var  = ANL01FL,
      mode     = "last"
    ),
    filter = ADT >= TRTSDT & !is.na(AVAL) & is.na(DTYPE)
  )
Step 11 — Dataset-specific: ADVS

Additional derivations specific to vital signs:

VSTEST mapping for PARAM units: Include units in PARAM text per spec (e.g. "Systolic Blood Pressure (mmHg)"). Confirm unit conventions from VSSTRESU.

Position variable (VSPOS): If VSPOS is in scope, carry through from VS and include in uniqueness assertions — ADVS uniqueness is typically per USUBJID + PARAMCD + AVISIT + VSPOS.

r
# Uniqueness assertion — adjust key variables per spec
stopifnot(
  advs |>
    filter(is.na(DTYPE)) |>
    count(STUDYID, USUBJID, PARAMCD, AVISITN, VSPOS) |>
    filter(n > 1) |>
    nrow() == 0
)

Duplicate records: If multiple VS records exist for the same subject-parameter-visit (e.g. triplicate BP measurements), decide with the statistician whether to: (a) average them and add DTYPE = "AVERAGE", (b) flag only one using ANL01FL, or (c) retain all. Add a # REVIEW: comment with the chosen approach.

Show full SKILL.md (362 more words)Show less
Step 12 — Dataset-specific: ADLB

Additional derivations specific to laboratory values:

Normal ranges: Carry LBSTNRLO and LBSTNRHI from LB as ANRLO and ANRHI.

r
adlb <- adlb |>
  derive_vars_merged(
    dataset_add = lb |> select(-DOMAIN),
    by_vars     = exprs(STUDYID, USUBJID, LBTESTCD, VISIT),
    new_vars    = exprs(ANRLO = LBSTNRLO, ANRHI = LBSTNRHI)
  )

Reference range indicator (ANRIND): Map to controlled terminology values ("LOW", "NORMAL", "HIGH", "LOW LOW", "HIGH HIGH").

r
# REVIEW: ANRIND derivation rules may be protocol-specific if the study
#   uses non-standard normal range definitions.
adlb <- adlb |>
  mutate(
    ANRIND = case_when(
      AVAL < ANRLO  ~ "LOW",
      AVAL > ANRHI  ~ "HIGH",
      !is.na(AVAL)  ~ "NORMAL"
    )
  )

Baseline reference range indicator (BNRIND): Carry ANRIND where ABLFL == "Y".

r
adlb <- adlb |>
  derive_var_base(
    by_vars    = exprs(STUDYID, USUBJID, PARAMCD, BASETYPE),
    source_var = ANRIND,
    new_var    = BNRIND
  )

Toxicity grades: If CTCAE grading is in scope, derive ATOXGR from LB.LBTOXGR using derive_vars_merged() and carry BTOXGR from baseline.

Step 13 — Dataset attributes and final checks
r
# Key uniqueness check — adjust by_vars per dataset and spec
key_vars <- c("STUDYID", "USUBJID", "PARAMCD", "AVISITN")
dup_check <- advs |>
  filter(is.na(DTYPE)) |>
  count(across(all_of(key_vars))) |>
  filter(n > 1)
if (nrow(dup_check) > 0) {
  stop("Duplicate records found: ", paste(key_vars, collapse = ", "))
}

# Check required BDS variables are present
required_vars <- c(
  "STUDYID", "USUBJID", "PARAM", "PARAMCD", "PARAMN",
  "ADT", "ADY", "AVISIT", "AVISITN",
  "AVAL", "BASE", "CHG", "ABLFL", "ANL01FL"
)
missing_vars <- setdiff(required_vars, names(advs))
if (length(missing_vars) > 0) {
  stop("Missing required BDS variables: ", paste(missing_vars, collapse = ", "))
}

# Apply variable labels and export via xportr — see adsl-conventions.md for pattern

Common BDS errors to avoid

  • Using filter() + mutate() to flag baselines instead of restrict_derivation() + derive_var_extreme_flag() — the admiral functions are required for reproducibility and traceability
  • Not adding BASETYPE before restrict_derivation() when multiple baseline definitions exist — results in incorrect BASE values for subjects with more than one baseline window
  • Deriving CHG before BASE is populated — derive_var_chg() depends on BASE being present; sequence matters
  • Passing VISIT directly to AVISIT — AVISIT is an ADaM-defined grouping, not an SDTM passthrough; always map via spec-driven visit table
  • Not scoping CHG/PCHG to on-treatment records before summary — ANL01FL or an equivalent filter must be applied in analysis programs
  • Asserting uniqueness without accounting for DTYPE rows — exclude DTYPE != NA records from uniqueness checks (synthetic rows are intentional duplicates by USUBJID + PARAMCD + AVISITN)
  • Using derive_vars_merged() instead of derive_vars_merged_lookup() for PARAMCD/PARAM/PARAMN assignment — derive_vars_merged() is primarily used for ADSL backbone merges; parameter code mappings must use derive_vars_merged_lookup() so that unmatched records are retained and filterable via filter(!is.na(PARAMCD))
  • Using "N" for ABLFL or ANL01FL — flag convention is "Y" or NA only
  • Deriving ANRIND from AVAL without a # REVIEW: comment — normal range logic is almost always protocol-specific

Output checklist

Before returning code, verify:

  • ADSL variables (TRTSDT, population flags) merged before baseline derivation
  • DOMAIN removed from source domain before derive_vars_merged() calls
  • PARAMCD/PARAM/PARAMN assigned with derive_vars_merged_lookup() — not derive_vars_merged(), not case_when()
  • ADT derived with derive_vars_dt(), not as.Date() on VSDTC/LBDTC
  • ADY derived with derive_vars_dy()
  • AVISIT assigned from spec-driven visit map
  • ABLFL flagged with restrict_derivation() + derive_var_extreme_flag()
  • BASE derived with derive_var_base()
  • CHG/PCHG derived with derive_var_chg() / derive_var_pchg()
  • ANL01FL annotated with # REVIEW: referencing SAP definition
  • Uniqueness assertion excludes DTYPE rows
  • All # REVIEW: comments placed at protocol-specific decision points
  • flag_imputation = "auto" used for date derivations
  • ABLFL and ANL01FL are "Y" or NA, never "N"
  • Dataset and variable labels applied before export

© RConsortium, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references) in admiral/admiral-bds of RConsortium/pharma-skills.

  • SKILL.md
  • DESIGN.md
  • LICENSE
  • README.md
  • benchmarks/README.md
  • references/bds-conventions.md

Open the folder on GitHubat commit ae5d83b

Compare with similar skills

Admiral Bds 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.

Admiral Bds compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Admiral Bds this skillRConsortium/pharma-skills120—~3.6kAutomated safety check: PassMIT
DatasetsArize-ai/phoenix12k—~1.6kAutomated safety check: PassCustom licence
Longbridge Derivativessickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassMIT
Dataset Curationwshobson/agents40k—~2kAutomated safety check: PassMIT
Arize Datasetgithub/awesome-copilot40k1 repos~3.9kAutomated safety check: NotesMIT
Bigquery Basicsdavila7/claude-code-templates33k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Datasets

    Arize-ai/phoenix

    Understand what a Phoenix dataset is and reason well about its examples, outputs, splits, and how it feeds evaluators and experiments.

    12k GitHub stars~1.6k tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Longbridge Derivatives

    sickn33/agentic-awesome-skills

    Curated upstream guidance for Longbridge Derivatives; use when the workflow matches the user goal.

    47k GitHub starsUsed in 1 repo~1.1k tokens
    Business, Finance & HRAuto-check passed
  • Dataset Curation

    wshobson/agents

    Prepare, format, and validate datasets for supervised fine-tuning and preference training.

    40k GitHub stars~2k tokensUpdated 5 days ago
    AI & LLM EngineeringAuto-check passed
  • Arize Dataset

    github/awesome-copilot

    Official

    Creates, manages, and queries Arize datasets and examples. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check: notes
  • Bigquery Basics

    davila7/claude-code-templates

    Manages datasets, tables, and jobs in BigQuery, and integrates with BigQuery ML and Gemini for advanced data analytics and AI-driven insights.

    33k GitHub stars~1.1k tokensUpdated today
    DatabasesAuto-check passed
  • Basic

    bergside/awesome-design-skills

    Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

    3.1k GitHub starsUsed in 1 repo~969 tokens
    Frontend & DesignAuto-check passed

More from RConsortium/pharma-skills

All 13 skills in this repo
  • Rounding

    RConsortium/pharma-skills

    Audit R code that prepares CSR/TLF statistics for SAS-compatible rounding compliance (ties away from zero, round-once-at-display, fixed trailing-zero precision).

    120 GitHub stars~3.8k tokensUpdated 6 days ago
    Auto-check passed
  • Issue To Eval

    RConsortium/pharma-skills

    Converts one or more GitHub Issues into standardized benchmark data using automated scripts.

    120 GitHub stars~463 tokensUpdated 6 days ago
    Auto-check passed
  • Weekly Summary

    RConsortium/pharma-skills

    Generate a concise weekly progress summary for the pharmaskills repository.

    120 GitHub stars~546 tokensUpdated 6 days ago
    Auto-check passed
  • Admiral Adae

    RConsortium/pharma-skills

    Derives an ADaM Adverse Events Analysis Dataset (ADAE) using the {admiral} R package and pharmaverse ecosystem.

    120 GitHub stars~3.9k tokensUpdated 6 days ago
    Auto-check passed
  • Admiral Adsl

    RConsortium/pharma-skills

    Derives an ADaM Subject-Level Analysis Dataset (ADSL) using the {admiral} R package and pharmaverse ecosystem.

    120 GitHub stars~4.4k tokensUpdated 6 days ago
    Auto-check passed
  • Sdtm Oak

    RConsortium/pharma-skills

    Derives CDISC SDTM domains from raw clinical (EDC/eCRF) data using the {sdtm.oak} R package.

    120 GitHub stars~3.9k tokensUpdated 6 days ago
    Auto-check passed

Questions about Admiral Bds

What does Admiral Bds do?

Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package. Admiral Bds is an agent skill from RConsortium/pharma-skills. Derives ADaM Basic Data Structure (BDS) datasets using the {admiral} R package.

When should I use Admiral Bds?

Admiral Bds fits situations like: A user needs to create a BDS findings dataset from SDTM domains; derive parameter assignments; baseline values; change from baseline.

How do I install Admiral Bds in Claude Code?

Run `npx skills add RConsortium/pharma-skills --skill admiral-bds -a claude-code`. Or copy the skill folder (admiral/admiral-bds in RConsortium/pharma-skills) into .claude/skills/admiral-bds in your project. Claude Code loads it when a task matches its description.

How do I install Admiral Bds in Codex?

Run `npx skills add RConsortium/pharma-skills --skill admiral-bds -a codex`. Or copy the skill folder (admiral/admiral-bds in RConsortium/pharma-skills) into .agents/skills/admiral-bds in your project. Codex loads it when a task matches its description.

Can I use Admiral Bds in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RConsortium/pharma-skills --skill admiral-bds -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/admiral-bds, .gemini/skills/admiral-bds, .github/skills/admiral-bds and .opencode/skills/admiral-bds in your project.

What does Admiral Bds need to run?

SKILL.md names no scripts, command-line tools or credentials: Admiral Bds is instructions for the agent only. Compatibility (from SKILL.md): Requires R with admiral, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset. Designed for use in a GxP-compliant environment with access to SDTM datasets and an ADaM BDS specification. .

Does Admiral Bds access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Admiral Bds safe to install?

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.

What licence does Admiral Bds use?

Admiral Bds is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Admiral Bds use?

About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Admiral Bds?

Skills that share tags, products or a category with Admiral Bds: Datasets (Arize-ai/phoenix, 12k stars), Longbridge Derivatives (sickn33/agentic-awesome-skills, 47k stars), Dataset Curation (wshobson/agents, 40k stars) and Arize Dataset (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Admiral Bds?

RConsortium (a GitHub organization) maintains it in RConsortium/pharma-skills, which has 120 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 4, 2026.

Source: RConsortium/pharma-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.