← All skill packs

AI Agent Workflow Collection

Skill pack
8 skills0 selected
jacobjamesonSkills in this pack

Use after estimating an observational target trial emulation to stress-test whether randomization was plausibly emulated — negative control outcomes/treatments/populations, covariate balance, positivity / weight diagnostics, and benchmarking against a randomized trial. Falsification, not verification.

English

Use when the outcome can be precluded by another event — e.g. death before the outcome of interest, or any "competing event" / "truncation event" — and you must choose and justify a causal estimand before analysis. Also use when loss to follow-up is present and you need to frame it as a joint intervention on treatment and censoring. Forces an explicit estimand and flags the common controlled-direct-effect trap.

English

Use when deciding how to adjust for confounding in a target trial emulation — eliciting the set of baseline confounders, choosing an adjustment method (matching, standardization/g-formula, or IP weighting), and judging whether emulating randomization is even reasonable (vs. unmeasured / intractable confounding that may call for instrumental-variable approaches).

English

Use when the treatment is sustained over time rather than a one-time decision at baseline — e.g. "initiate and continue therapy unless contraindicated", treatment with a duration, dose strategies, or strategies defined by WHEN/HOW LONG to treat. Decides static vs dynamic, whether time-varying confounding / treatment-confounder feedback requires g-methods, and whether the strategies are distinguishable at time zero (→ cloning) and need a grace period.

English

Use when a user wants to specify, sharpen, or critique a causal question as a target trial for target trial emulation (TTE) with observational (or trial) data — e.g. "I want to estimate the effect of X on Y", "is this a good causal question?", "set up a target trial for ...", "specify the protocol", or before running any TTE analysis. Interactively elicits the eight protocol elements and pushes back on common, avoidable design errors before any estimation.

English

Use when defining or auditing "time zero" (start of follow-up) in a target trial emulation — when an analysis needs to align eligibility, treatment assignment, and start of follow-up, when there is risk of immortal-time or prevalent-user selection bias, when individuals are eligible at multiple times, or to decide between a single emulated trial and sequential (nested) trials.

English

Use to generate and run the R analysis for a (specified) target trial emulation — estimating the causal effect after the protocol, time zero, and confounders are set. Dispatches by OUTCOME TYPE (time-to-event, continuous, binary) and ADJUSTMENT METHOD (none/RCT, matching, standardization, IP weighting) and writes a readable, course-faithful R script that calls the TTECC helpers.

English

Use to draft the write-up of a target trial emulation — the protocol table, a CONSORT-style participant-flow diagram, methods, and results — with disciplined causal language (causal terms in Title/Intro/Methods/Discussion, never in Results). Produces a manuscript/methods skeleton.

English

Includes Check Emulation, Competing Events, Emulate Randomization, and other workflows.

Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI

Supported by the Atlas install prompt. Skill-specific requirements vary.

Pack stats

Skills8CategorygeneralStars0

What’s included

Check Emulation

Use after estimating an observational target trial emulation to stress-test whether randomization was plausibly emulated — negative control outcomes/treatments/populations, covariate balance, positivity / weight diagnostics, and benchmarking against a randomized trial. Falsification, not verification.

Competing Events

Use when the outcome can be precluded by another event — e.g. death before the outcome of interest, or any "competing event" / "truncation event" — and you must choose and justify a causal estimand before analysis. Also use when loss to follow-up is present and you need to frame it as a joint intervention on treatment and censoring. Forces an explicit estimand and flags the common controlled-direct-effect trap.

Emulate Randomization

Use when deciding how to adjust for confounding in a target trial emulation — eliciting the set of baseline confounders, choosing an adjustment method (matching, standardization/g-formula, or IP weighting), and judging whether emulating randomization is even reasonable (vs. unmeasured / intractable confounding that may call for instrumental-variable approaches).

Sustained Strategies

Use when the treatment is sustained over time rather than a one-time decision at baseline — e.g. "initiate and continue therapy unless contraindicated", treatment with a duration, dose strategies, or strategies defined by WHEN/HOW LONG to treat. Decides static vs dynamic, whether time-varying confounding / treatment-confounder feedback requires g-methods, and whether the strategies are distinguishable at time zero (→ cloning) and need a grace period.

Target Trial

Use when a user wants to specify, sharpen, or critique a causal question as a target trial for target trial emulation (TTE) with observational (or trial) data — e.g. "I want to estimate the effect of X on Y", "is this a good causal question?", "set up a target trial for ...", "specify the protocol", or before running any TTE analysis. Interactively elicits the eight protocol elements and pushes back on common, avoidable design errors before any estimation.

Time Zero

Use when defining or auditing "time zero" (start of follow-up) in a target trial emulation — when an analysis needs to align eligibility, treatment assignment, and start of follow-up, when there is risk of immortal-time or prevalent-user selection bias, when individuals are eligible at multiple times, or to decide between a single emulated trial and sequential (nested) trials.

Tte Estimate

Use to generate and run the R analysis for a (specified) target trial emulation — estimating the causal effect after the protocol, time zero, and confounders are set. Dispatches by OUTCOME TYPE (time-to-event, continuous, binary) and ADJUSTMENT METHOD (none/RCT, matching, standardization, IP weighting) and writes a readable, course-faithful R script that calls the TTECC helpers.

Tte Report

Use to draft the write-up of a target trial emulation — the protocol table, a CONSORT-style participant-flow diagram, methods, and results — with disciplined causal language (causal terms in Title/Intro/Methods/Discussion, never in Results). Produces a manuscript/methods skeleton.

Quick start

  1. Choose your skills. Select individual skills above, or choose the entire pack.
  2. Copy the install prompt. Use Copy install prompt above the list.
  3. Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.

Try it with your agent

After installation, start with a request like:

Example request
Use the Check Emulation skill to help with my task.
Ask me for the context you need before getting started.

Requirements & license

  • A coding agent that can access your project files and install skills.
  • Your agent checks each skill’s instructions, dependencies, and permissions during setup.
  • Reported license for the skills shown: MIT. The author’s terms apply.
AI Agent Workflow Collection | Agent Skills Atlas