name-and-control-bias

Maps named research biases to concrete controls across study lifecycle stages.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill name-and-control-bias-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: name-and-control-bias
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/name-and-control-bias
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill name-and-control-bias-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research findings often fail because biases like self-selection, leading questions, and confirmation bias distort results, and vague advice like "stay objective" does nothing to prevent them. This Skill provides a canonical reference that pairs every named bias with a concrete control, so studies can be audited before fielding and findings can be trusted before they gate decisions. ## Core Features & Use Cases - Bias-to-control mapping: Every named bias across five lifecycle stages (sampling, instrument design, moderation, analysis, study-level confounds) is paired with a concrete design change that removes or bounds it. - Two audit modes: A fast triage path covering the top 5 study-killers for low-stakes work, and a full audit path for findings that gate decisions or external claims. - Internal vs external validity separation: Forces explicit statements about whether a claim is valid within the study, generalizable beyond it, or both. - Use Case: Before shipping a redesign based on "5 of 6 beta users said the new flow is easier," run the bias audit to catch self-selection, social desirability, survivorship, and overgeneralization, then attach concrete fixes like recruiting lapsed users and reporting prevalence as X of Y. ## Quick Start Audit my planned usability study for biases and tell me which threats actually endanger my conclusion and what concrete controls to add.

Frequently Asked Questions about name-and-control-bias

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my user research study for bias?

Run a bias audit by naming only the biases that actually threaten your specific claim, then attach a concrete control to each. For quick checks, test against the top 5 study-killers: self-selection, leading questions, analyst confirmation bias, social desirability, and small-n overgeneralization.

What is the difference between internal and external validity in UX research?

Internal validity asks whether a finding is real within the study, threatened by instrument, moderation, and analysis biases. External validity asks whether it generalizes beyond the sample, threatened by sampling and coverage biases. Small-n qualitative studies typically earn internal but not external validity.

How do I control for confirmation bias in research analysis?

Control confirmation bias with concrete changes: fix research questions before collecting data, run a mandatory disconfirming-case hunt, and use a second coder or fresh-eyes pass on analysis. Simply being aware of the bias is not a control.

Does a larger sample size fix sampling bias?

No. A large self-selected or non-representative sample is precisely wrong at scale. Sample size fixes precision, not bias; composition problems require controls like diverse recruit channels, screening against motivation, and deliberately recruiting absent cases such as churned users.

When should I run a full bias audit versus a quick triage?

Use the fast triage of the top 5 study-killers for low-stakes or time-boxed studies, taking about 10 minutes. Run the full lifecycle audit when a finding will gate a decision, support an external-facing claim, or appear in a client deliverable.