blinding
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 98 / 100 · audit passed
- Author / version / license
- @majiayu000 · v1.0.0 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: blinding
description: Implement blinding procedures to reduce bias in experimental studies. Use when: (1) Designing RC…
category: data
runtime: no special runtime
---
# blinding output preview
## PART A: Task fit
- Use case: Implement blinding procedures to reduce bias in experimental studies. Use when: (1) Designing RCTs, (2) Ensuring objectivity, (3) Meeting CONSORT standards, (4) Minimizing performance and detection bias..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / Types of Blinding / Who to Blind” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Implement blinding procedures to reduce bias in experimental studies. Use when: (1) Designing RCTs, (2) Ensuring objectivity, (3) Meeting CONSORT standards, (4) Minimizing performance and detection bias.”.
- **02** When the source has headings, the agent prioritizes “Purpose / Types of Blinding / Who to Blind” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Purpose / Types of Blinding / Who to Blind”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: blinding
description: Implement blinding procedures to reduce bias in experimental studies. Use when: (1) Designing RC…
category: data
source: majiayu000/claude-skill-registry
---
# blinding
## When to use
- Implement blinding procedures to reduce bias in experimental studies. Use when: (1) Designing RCTs, (2) Ensuring objec…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / Types of Blinding / Who to Blind” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "blinding" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / Types of Blinding / Who to Blind
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Blinding Procedures Skill
Purpose
Implement appropriate blinding to reduce bias in research studies.
Types of Blinding
Single-Blind: Participants unaware of allocation Double-Blind: Participants and researchers unaware Triple-Blind: Participants, researchers, and analysts unaware
Who to Blind
Participants: Reduce expectancy effects, placebo Interventionists: Reduce performance bias Assessors: Reduce detection bias Analysts: Reduce reporting bias
Blinding Strategies
Medications:
- Identical placebo (same appearance, taste)
- Over-encapsulation
- Matching packaging
Behavioral Interventions:
- Attention-matched control
- Active control condition
- Blind outcome assessors
Assessments:
- Automated/computerized measures
- Independent blinded raters
- Objective outcomes (less bias-prone)
When Blinding Impossible
- Surgical interventions
- Exercise interventions
- Educational programs
Mitigation:
- Blind outcome assessors
- Use objective outcomes
- Report lack of blinding as limitation
Version: 1.0.0
Decide Fit First
Design Intent
How To Use It
Boundaries And Review