CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

confounder-and-bias-control-planner

Plans confounder control, variable adjustment logic, and bias mitigation strategies at the protocol stage for clinical, epidemiologic, translational, observational, and biomarker studies. Always use this skill when a user needs to identify major confounders, decide which variables should or should not be adjusted for, compare matching/stratification/weighting approaches, anticipate selection or measurement bias, or pressure-test a study design before execution. Focus on bias sensing, causal structure awareness, variable-role classification, and critical design review rather than generic statistical advice.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction skill with excellent progressive disclosure (all nine references real and mapped to output sections) and a clearly sequenced decision workflow with a time-order gate. The main weaknesses are redundancy — negative guidance repeated across three sections and a trigger list duplicating the description — plus a minor step-count mismatch with the workflow reference template and no worked output example.

Suggestions

Consolidate the three overlapping negative-guidance blocks (Core Function's 'should not' list, Hard Rules, and 'What This Skill Should Not Do') into the single Hard Rules section, which is the most forceful and best-placed home for them.

Delete or trim the 'Sample Triggers' section — its examples duplicate the trigger phrases already in the description and in 'Input Validation' examples.

Add one short worked example (e.g., a filled Section F table row showing variable → proposed role → recommended handling → rationale) and sync the 8-step Decision Logic with the 9-step references/workflow-step-template.md to remove the step-count mismatch.

DimensionReasoningScore

Conciseness

The body is prescriptive rather than explanatory, but there is clear trimmable redundancy: negative guidance appears in three overlapping places (Core Function's "should not" list, Hard Rules, and the separate "What This Skill Should Not Do" section), and the "Sample Triggers" section largely duplicates the description's trigger phrases. Not 2 because there is no padded conceptual explanation — nearly every statement carries operational weight; not 4 because the duplicated sections and trigger list are unnecessary tokens.

3 / 5

Actionability

For an instruction-only skill the guidance is mostly executable: an 8-step decision logic with named reference modules per step, a mandatory output structure (Sections A–K) with specified table columns and handling categories ("must adjust / control", "do not adjust", "role uncertain"), and an exact out-of-scope redirect template. Minor gaps keep it below fully executable: no worked example of a filled output section, and some directives remain abstract ("identify the true confounding problem rather than list generic covariates").

4 / 5

Workflow Clarity

The 8-step sequence is clear and each step maps to a reference module, with a gating checkpoint ("Do not proceed with adjustment logic until time order is at least partially clarified"), input validation with an explicit redirect, and a role-uncertain escape hatch. It falls short of 5 because there is no explicit error-recovery loop, and the body's 8 steps are out of sync with the 9 steps in references/workflow-step-template.md, which the body directs the model to follow for step alignment.

4 / 5

Progressive Disclosure

SKILL.md functions as an overview that explicitly routes each of the nine real, substantive, one-level-deep reference files to specific output sections (e.g., "references/adjustment-selection-rules.md → use when deciding which variables should be adjusted for... in Sections E and F"), and states the consequence of skipping them. All referenced paths exist and navigation is unambiguous.

5 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete third-person capability list, an explicit 'Always use this skill when...' trigger clause with five natural conditions, and a clear niche reinforced by an explicit scope contrast. The only gap is a few missing synonyms (e.g., 'covariates', 'propensity score') in trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "identify major confounders", "decide which variables should or should not be adjusted for", "compare matching/stratification/weighting approaches", "anticipate selection or measurement bias", "pressure-test a study design" — comprehensively covering the skill's domain. It exceeds the minor-gaps level because identification, adjustment decisions, strategy comparison, bias anticipation, and critical review are all explicitly named, and it uses third-person voice throughout.

5 / 5

Completeness

It clearly answers both questions: the first sentence states what the skill does ("Plans confounder control, variable adjustment logic, and bias mitigation strategies at the protocol stage...") and "Always use this skill when a user needs to..." explicitly states when to use it with five concrete trigger conditions. Not 4 because the 'when' clause is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say: "confounders", "adjust for", "matching", "stratification", "weighting", "selection bias", "measurement bias", "pressure-test". It falls short of comprehensive because common synonyms like "covariates", "control for", or "propensity score" are absent, matching the 'a few natural terms missing' anchor rather than full synonym coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (protocol-stage confounder/bias planning for biomedical studies) and actively reduces conflict risk with the contrast clause "rather than generic statistical advice", distinguishing it from general statistics or data-analysis skills. Minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

awesome-med-research-skills/Protocol Design/confounder-and-bias-control-planner/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.