Agent skill

Admiral Adrs

by RConsortium in RConsortium/pharma-skills

Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages.

MITAuto-check passedDevelopment

Install Admiral Adrs

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

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

GitHub CLI
$ gh skill install RConsortium/pharma-skills admiral-adrs --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-adrs .claude/skills/admiral-adrs && 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-adrs
GitHub stars
120
Token cost
~3.9k tokens
SKILL.md length
1,077 words
Files
5
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages.

  • Works in 12 steps: Setup and domain loading → DOMAIN removal → Merge ADSL backbone variables → …
  • A user needs to create ADRS from SDTM RS domain data
  • SKILL.md covers Inputs, Workflow, Flag convention exception for… and Common errors to avoid, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Admiral Adrs is an agent skill from RConsortium/pharma-skills. Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages. Use when a user needs to create ADRS from SDTM RS domain data, derive RECIST 1.1 response parameters (overall response, confirmed response, best overall response, clinical benefit), or generate QC-ready R code following CDISC ADaM and oncology conventions. Requires SDTM RS input data, ADSL with randomization and treatment dates, and an ADaM ADRS specification.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `DESIGN.md`, `README.md` and `benchmarks/README.md`). Compatibility notes: Requires R with admiral, admiralonco, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset with RANDDT and TRTSDT. Designed for…

It sits in Development, covering Architecture decision records. 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 ADRS from SDTM RS domain data
  • Derive RECIST 1.1 response parameters (overall response
  • Confirmed response
  • Best overall response

Example prompts

  • “Use the admiral-adrs skill to derive an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages”
  • “/admiral-adrs”

Requirements

  • Compatibility (from SKILL.md): Requires R with admiral, admiralonco, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset with RANDDT and TRTSDT. Designed for use in a GxP-compliant oncology trial environment with access to SDTM RS domain data and an ADaM ADRS specification.

Workflow steps

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

  1. Setup and domain loading
  2. DOMAIN removal
  3. Merge ADSL backbone variables
  4. Date derivation (ADT, ADTF, ADY)
  5. Analysis value (AVALC, AVAL)
  6. Overall response parameter (OVRLRESP)
  7. Unconfirmed response flag (RSP)
  8. Confirmed response (CONFIRMED)
  9. Best overall response (BESTRESP)
  10. Clinical benefit (CBRESPFL)
  11. Verification: confirmed vs unconfirmed ORR
  12. Final checks

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, admiralonco, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset with RANDDT and TRTSDT. Designed for use in a GxP-compliant oncology trial environment with access to SDTM RS domain data and an ADaM ADRS specification.

    From compatibility in the SKILL.md frontmatter.

Context cost

Admiral Adrs loads about 3.9k tokens when it runs. Until then it costs about 120 tokens; SKILL.md has 1,077 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~120
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

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). 1,077 words, ~3,931 tokens.

Download SKILL.mdSave it as .claude/skills/admiral-adrs/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
admiral-adrs
description
Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages. Use when a user needs to create ADRS from SDTM RS domain data, derive RECIST 1.1 response parameters (overall response, confirmed response, best overall response, clinical benefit), or generate QC-ready R code following CDISC ADaM and oncology conventions. Requires SDTM RS input data, ADSL with randomization and treatment dates, and an ADaM ADRS specification.
compatibility
Requires R with admiral, admiralonco, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset with RANDDT and TRTSDT. Designed for use in a GxP-compliant oncology trial environment with access to SDTM RS domain data and an ADaM ADRS specification.
license
MIT
metadata.author
Navitas Data Sciences
metadata.version
0.1
metadata.pharmaverse
true
metadata.parent
admiral

admiral-adrs

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 ADRS-specific.

Derives a CDISC-conformant ADRS tumor response dataset using {admiral} and {admiralonco}. Outputs executable, QC-ready R code covering RECIST 1.1 response parameters with full derivation traceability.

The primary design challenge in ADRS is the confirmation logic: CR and PR must be supported by a second qualifying assessment ≥28 days later. Best Overall Response (BOR) follows a strict hierarchy (CR > PR > SD > NON-CR/NON-PD > PD > NE) and handles NE propagation in ways that manual case_when() or slice_min() cannot replicate correctly. Always use admiralonco functions — never manual derivations.


Inputs

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

InputRequiredNotes
RSYesOne record per tumor assessment per subject; RSSTRESC contains the response category (CR/PR/SD/PD/NE)
ADSLYesProvides TRTSDT, RANDDT, treatment labels, population flags
ADaM ADRS specYesParameter list, PARAMCD/PARAM mapping, confirmation window, clinical benefit definition
Study contextYesRECIST version (1.0 vs 1.1), assessor (investigator vs BICR), confirmation window, clinical benefit anchor date

If RS or ADSL are absent, stop and request them.

Note on pharmaversesdtm test data: The pharmaversesdtm package no longer exports a plain rs object. Use pharmaversesdtm::rs_onco_recist for test or benchmark runs. When working with real study data, load RS from the study's SDTM package or file path.


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(admiralonco)
library(dplyr)
library(lubridate)
library(pharmaversesdtm)

# Load RS domain
# For pharmaversesdtm test data: use rs_onco_recist (plain `rs` no longer exported)
rs   <- pharmaversesdtm::rs_onco_recist
adsl <- adsl  # assumed derived upstream; replace with path/load as needed

# Confirm RS has at least one record
stopifnot(nrow(rs) > 0)
Step 2 — DOMAIN removal

Remove DOMAIN from RS before any derive_param_*() or derive_vars_merged() calls. admiral errors when DOMAIN exists in both the dataset and a source dataset passed to these functions.

r
rs <- rs |> select(-DOMAIN)
Step 3 — Merge ADSL backbone variables

Bring required ADSL variables into the RS dataset before parameter derivation. At minimum: RANDDT and TRTSDT (clinical benefit anchor and study day reference), treatment labels, and population flags.

r
# REVIEW: Confirm which ADSL variables are required by the ADaM ADRS spec.
#   RANDDT is the conventional clinical benefit anchor date; TRTSDT is required
#   for ADY derivation. Add or remove population flags per the spec.
adrs <- rs |>
  derive_vars_merged(
    dataset_add = adsl,
    by_vars     = exprs(STUDYID, USUBJID),
    new_vars    = exprs(RANDDT, TRTSDT, TRT01P, TRT01PN, TRT01A, TRT01AN,
                        ITTFL, SAFFL)
  )
Step 4 — Date derivation (ADT, ADTF, ADY)

Derive the analysis date from RSDTC. This must happen before any derive_param_*() call — admiralonco response functions use ADT internally for confirmation window comparisons.

r
adrs <- adrs |>
  derive_vars_dt(
    dtc             = RSDTC,
    new_vars_prefix = "A",
    date_imputation = "first",
    flag_imputation = "auto"
  ) |>
  derive_vars_dy(
    reference_date = TRTSDT,
    source_vars    = exprs(ADT)
  )
Step 5 — Analysis value (AVALC, AVAL)

Set AVALC from RSSTRESC and derive the numeric AVAL using the admiralonco helper aval_resp(). This function maps response categories to a monotone numeric scale: CR=1, PR=2, SD=3, NON-CR/NON-PD=4, PD=5, NE=6.

r
# REVIEW: Confirm that RSSTRESC values in this study's RS domain align with the
#   RECIST 1.1 CT expected by aval_resp(). Non-standard categories (e.g.
#   "NON-CR/NON-PD" in lymphoma, iRECIST response categories) require a custom
#   lookup if aval_resp() does not map them — do not suppress the resulting NA.
adrs <- adrs |>
  mutate(
    AVALC = RSSTRESC,
    AVAL  = aval_resp(AVALC)
  )
Step 6 — Overall response parameter (OVRLRESP)

Add OVRLRESP records — one per subject per assessment timepoint. This parameter carries the verbatim response at each visit; it is not confirmation-adjusted.

r
# REVIEW: PARAMCD and PARAM values must match the ADaM ADRS spec exactly.
#   Adjust filter_source if the study uses a different assessor
#   (BICR: RSEVAL == "INDEPENDENT ASSESSOR") or a different RECIST version.
adrs <- adrs |>
  derive_param_response(
    dataset_adsl  = adsl,
    filter_source = RSEVAL == "INVESTIGATOR" & RSEVALID == "RECIST 1.1",
    source_var    = RSSTRESC,
    set_values_to = exprs(
      PARAMCD = "OVRLRESP",
      PARAM   = "Overall Response by Investigator"
    )
  )
Step 7 — Unconfirmed response flag (RSP)

Add RSP records — one per subject, indicating whether any CR or PR was observed (unconfirmed). Retained alongside CONFIRMED to enable the ORR verification check in Step 11.

r
adrs <- adrs |>
  derive_param_response(
    dataset_adsl  = adsl,
    filter_source = RSEVAL == "INVESTIGATOR" & RSEVALID == "RECIST 1.1",
    source_var    = RSSTRESC,
    resp_val      = c("CR", "PR"),
    set_values_to = exprs(
      PARAMCD = "RSP",
      PARAM   = "Response (Unconfirmed)"
    )
  )
Step 8 — Confirmed response (CONFIRMED)

A CR or PR is confirmed when a second qualifying assessment ≥ ref_confirm days after the first also shows CR or PR. CONFIRMED = "Y" if the subject has at least one confirmed CR or PR; "N" otherwise.

Flag convention note: CONFIRMED uses "Y"/"N", not "Y"/NA — this is the documented admiralonco contract. See Flag convention exception below. Do not recode "N" to NA.

r
# REVIEW: ref_confirm = 28 is the RECIST 1.1 standard for CR/PR confirmation.
#   Confirm this value against the study protocol and SAP — some programs specify
#   21 days, and regulatory precedent exists for other windows. A wrong value
#   silently inflates or deflates confirmed ORR.
adrs <- adrs |>
  derive_param_confirmed_resp(
    dataset_adsl  = adsl,
    filter_source = RSEVAL == "INVESTIGATOR" & RSEVALID == "RECIST 1.1",
    source_var    = RSSTRESC,
    ref_confirm   = 28,       # PLACEHOLDER — confirm from SAP
    set_values_to = exprs(
      PARAMCD = "CONFIRMED",
      PARAM   = "Confirmed Response"
    )
  )
Step 9 — Best overall response (BESTRESP)

BOR applies the RECIST 1.1 hierarchy across all assessments for each subject. derive_param_confirmed_bor() handles confirmation requirements, the NE propagation rule, and the hierarchy correctly. Never substitute slice_min(AVAL) or manual case_when() — these cannot replicate the NE propagation logic.

r
# REVIEW: missing_as_ne controls how missing assessments are treated in BOR.
#   FALSE (default): missing assessments are ignored (excluded from BOR).
#   TRUE: missing assessments count as NE, which can worsen BOR for subjects
#   with gaps in the assessment schedule.
#   Confirm the per-protocol analysis population definition with the
#   statistical reviewer before committing to either value.
adrs <- adrs |>
  derive_param_confirmed_bor(
    dataset_adsl  = adsl,
    filter_source = RSEVAL == "INVESTIGATOR" & RSEVALID == "RECIST 1.1",
    source_var    = RSSTRESC,
    ref_confirm   = 28,       # must match Step 8
    missing_as_ne = FALSE,    # PLACEHOLDER — confirm from SAP
    set_values_to = exprs(
      PARAMCD = "BESTRESP",
      PARAM   = "Best Overall Response (Confirmed)"
    )
  )
Step 10 — Clinical benefit (CBRESPFL)

Clinical benefit is a durable non-progressive response: CR, PR, or SD sustained for ≥ ref_start_window days from reference_date. CBRESPFL = "Y" if criteria are met; "N" otherwise.

Flag convention note: CBRESPFL uses "Y"/"N", not "Y"/NA. Same admiralonco contract as CONFIRMED — do not recode.

r
# REVIEW: Two protocol-specific decisions are required here and must both be
#   confirmed from the protocol and SAP before use:
#
#   (1) reference_date — RANDDT is the conventional anchor. Some protocols
#       instead define the 42-day window from the date of the first qualifying
#       response (first SD, PR, or CR). If the protocol means "from first
#       qualifying assessment", compute per-subject first-assessment dates
#       and pass them as reference_date rather than a fixed ADSL variable.
#
#   (2) ref_start_window = 42 — RECIST standard for SD duration. Some studies
#       use 35 or 56 days. Confirm from the protocol.
adrs <- adrs |>
  derive_param_clinbenefit(
    dataset_adsl     = adsl,
    filter_source    = RSEVAL == "INVESTIGATOR" & RSEVALID == "RECIST 1.1",
    source_var       = RSSTRESC,
    reference_date   = RANDDT,    # PLACEHOLDER — confirm anchor from protocol
    ref_start_window = 42,        # PLACEHOLDER — confirm from protocol
    set_values_to    = exprs(
      PARAMCD = "CBRESPFL",
      PARAM   = "Clinical Benefit"
    )
  )
Step 11 — Verification: confirmed vs unconfirmed ORR

Print response counts side-by-side and assert that confirmed ORR cannot exceed unconfirmed ORR. A confirmed count greater than unconfirmed count signals a configuration error in the confirmation window.

r
# Print response parameter summary for QC — include in script output log
response_summary <- adrs |>
  filter(PARAMCD %in% c("RSP", "CONFIRMED", "CBRESPFL")) |>
  count(PARAMCD, AVALC)
print(response_summary)

# Confirmed ORR must not exceed unconfirmed ORR
n_confirmed   <- sum(adrs$PARAMCD == "CONFIRMED" & adrs$AVALC == "Y", na.rm = TRUE)
n_unconfirmed <- sum(adrs$PARAMCD == "RSP"       & adrs$AVALC == "Y", na.rm = TRUE)
stopifnot(n_confirmed <= n_unconfirmed)

# PD is never a confirmed response
stopifnot(!any(
  adrs$PARAMCD == "CONFIRMED" & adrs$AVALC == "Y" &
  adrs$AVAL == aval_resp("PD"),
  na.rm = TRUE
))
Step 12 — Final checks
r
# Required parameter coverage
required_params <- c("OVRLRESP", "RSP", "CONFIRMED", "BESTRESP", "CBRESPFL")
missing_params  <- setdiff(required_params, unique(adrs$PARAMCD))
if (length(missing_params) > 0) {
  stop("Missing required ADRS parameters: ", paste(missing_params, collapse = ", "))
}

# Uniqueness: one record per subject per subject-level parameter
dup_check <- adrs |>
  filter(PARAMCD %in% c("BESTRESP", "CONFIRMED", "RSP", "CBRESPFL")) |>
  count(STUDYID, USUBJID, PARAMCD) |>
  filter(n > 1)
if (nrow(dup_check) > 0) {
  stop("Duplicate subject-level parameter records found:\n",
       paste(paste(dup_check$USUBJID, dup_check$PARAMCD), collapse = "\n"))
}

# Required variable presence check
required_vars <- c(
  "STUDYID", "USUBJID", "PARAMCD", "PARAM",
  "ADT", "ADTF", "ADY", "AVAL", "AVALC", "TRTSDT"
)
missing_vars <- setdiff(required_vars, names(adrs))
if (length(missing_vars) > 0) {
  stop("Missing required ADRS variables: ", paste(missing_vars, collapse = ", "))
}

Show full SKILL.md (439 more words)Show less

Flag convention exception for CONFIRMED and CBRESPFL

The admiral family convention is "Y" or NA — never "N" — for flag variables. ADRS has two named exceptions:

VariableValuesReason
CONFIRMED"Y" / "N"admiralonco contract: "N" means assessed but unconfirmed, not missing
CBRESPFL"Y" / "N"admiralonco contract: same logic as CONFIRMED

Do not recode "N" to NA for these variables. The "N" records are required by downstream derive_param_confirmed_bor() logic to correctly identify subjects with no confirmed response. Recoding them breaks BOR derivation.

All other flags in ADRS (ANL01FL, ABLFL, population flags from ADSL) follow the standard "Y" or NA convention.


Common errors to avoid

  • Using rs instead of rs_onco_recist from pharmaversesdtm — the plain rs object is no longer exported; the script will fail at load
  • Using case_when() or slice_min(AVAL) for BOR — manual BOR derivation cannot replicate admiralonco's NE propagation rule and confirmation hierarchy; always use derive_param_confirmed_bor()
  • Not removing DOMAIN from RS before derive_param_*() calls — causes variable conflict errors; DOMAIN must be removed in Step 2, not in the final select() at the end of the script
  • Hardcoding ref_confirm = 28 without a # REVIEW: comment — the confirmation window is protocol-specific and must come from the SAP; a wrong value silently inflates or deflates confirmed ORR
  • Applying derive_vars_dt() after derive_param_response() — ADT must exist before the response parameter functions run; the functions use ADT for confirmation window comparisons
  • Using RANDDT as the clinical benefit anchor without verifying protocol intent — if the protocol defines the 42-day window from the "first qualifying response assessment" rather than randomization, a fixed RANDDT will misclassify subjects
  • Not printing the confirmed vs unconfirmed ORR comparison — the omission is a silent audit risk; confirmed ORR > unconfirmed ORR indicates a derivation error that will not surface without an explicit check
  • Recoding CONFIRMED or CBRESPFL "N" to NA — these values are meaningful per the admiralonco function contract; recoding breaks downstream BOR derivation

Output checklist

Before returning code, verify:

  • DOMAIN removed from RS in Step 2, before any derive_param_*() call
  • ADSL merged with at minimum RANDDT, TRTSDT, and population flags before parameter derivation
  • ADT derived with derive_vars_dt() from RSDTC, with flag_imputation = "auto"
  • AVALC and AVAL (via aval_resp()) populated before derive_param_response() calls
  • All five parameters present in output: OVRLRESP, RSP, CONFIRMED, BESTRESP, CBRESPFL
  • # REVIEW: at PARAMCD/PARAM mapping in Steps 6–10
  • # REVIEW: at ref_confirm in Steps 8 and 9
  • # REVIEW: at missing_as_ne in Step 9
  • # REVIEW: at reference_date and ref_start_window in Step 10
  • Confirmed vs unconfirmed ORR comparison printed to console (Step 11)
  • stopifnot(n_confirmed <= n_unconfirmed) present (Step 11)
  • PD-never-confirmed assertion present (Step 11)
  • Required PARAMCD coverage check present (Step 12)
  • Uniqueness assertion for subject-level parameters (Step 12)
  • CONFIRMED and CBRESPFL values are "Y"/"N" — not recoded to "Y"/NA

© 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 4 other files in admiral/admiral-adrs of RConsortium/pharma-skills.

  • SKILL.md
  • DESIGN.md
  • LICENSE
  • README.md
  • benchmarks/README.md

Open the folder on GitHubat commit ae5d83b

Compare with similar skills

Admiral Adrs 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 Adrs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Admiral Adrs this skillRConsortium/pharma-skills120—~3.9kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands91k—~2.4kAutomated safety check: PassMIT
Cto AdvisorIbrahim-3d/orchestrator-supaconductor3814 repos~2.4kAutomated safety check: PassMIT
Domain Modelingbrim-borium/spotify_sdk1667 repos~806Automated safety check: PassApache-2.0
Architecture DecisionDonchitos/Claude-Code-Game-Studios26k—~1.7kAutomated safety check: PassMIT
Improve Codebase Architectureywwynm/EverythingDone14415 repos~1.3kAutomated safety check: PassGPL-3.0

Similar skills

  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    91k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Domain Modeling

    brim-borium/spotify_sdk

    Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.

    166 GitHub starsUsed in 7 repos~806 tokens
    DevelopmentAuto-check passed
  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated 3 days ago
    DevelopmentAuto-check passed
  • Improve Codebase Architecture

    ywwynm/EverythingDone

    Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.

    144 GitHub starsUsed in 15 repos~1.3k tokens
    DevelopmentAuto-check passed
  • Design Doc Mermaid

    SpillwaveSolutions/design-doc-mermaid

    Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.

    176 GitHub starsUsed in 1 repo~5.6k tokens
    DevelopmentAuto-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 7 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 7 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 7 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 7 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 7 days ago
    Auto-check passed
  • Admiral Bds

    RConsortium/pharma-skills

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

    120 GitHub stars~3.6k tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Admiral Adrs

What does Admiral Adrs do?

Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages. Admiral Adrs is an agent skill from RConsortium/pharma-skills. Derives an ADaM Tumor Response Analysis Dataset (ADRS) using the {admiral} and {admiralonco} R packages.

When should I use Admiral Adrs?

Admiral Adrs fits situations like: A user needs to create ADRS from SDTM RS domain data; derive RECIST 1.1 response parameters (overall response; confirmed response; best overall response.

How do I install Admiral Adrs in Claude Code?

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

How do I install Admiral Adrs in Codex?

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

Can I use Admiral Adrs 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-adrs -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-adrs, .gemini/skills/admiral-adrs, .github/skills/admiral-adrs and .opencode/skills/admiral-adrs in your project.

What does Admiral Adrs need to run?

SKILL.md names no scripts, command-line tools or credentials: Admiral Adrs is instructions for the agent only. Compatibility (from SKILL.md): Requires R with admiral, admiralonco, dplyr, lubridate, and pharmaversesdtm installed. Requires a completed ADSL dataset with RANDDT and TRTSDT. Designed for use in a GxP-compliant oncology trial environment with access to SDTM RS domain data and an ADaM ADRS specification. .

Does Admiral Adrs 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 Adrs 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 Adrs use?

Admiral Adrs 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 Adrs use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Admiral Adrs?

Skills that share tags, products or a category with Admiral Adrs: PR Design Doc (OpenHands/OpenHands, 91k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars), Domain Modeling (brim-borium/spotify_sdk, 166 stars) and Architecture Decision (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Admiral Adrs?

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.