Skip to content
Back to skills

Estimate Sample Size

ASecurity

Estimate sample/repetition requirements from detectable effect, uncertainty, power/precision target, and design structure.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
research

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill estimate-sample-size --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Estimate Sample Size?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Estimate Sample Size
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-estimate-sample-size/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-estimate-sample-size)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: estimate-sample-size
description: "Estimate sample/repetition requirements from detectable effect, uncertainty, power/precision target, and design structure."
---

# estimate-sample-size

## Purpose

Estimate sample/repetition requirements from detectable effect, uncertainty, power/precision target, and design structure.

## Input contract

```yaml
required: [effect_target, uncertainty_model, power_target, design_structure]
optional: [evidence, assumptions, prior_results]
constraints: [use named scientific objects; retain provenance and missingness; $\alpha$ = 0.05 and power = 0.8 where applicable]
```

## Procedure

1. Validate the typed inputs and state the decision this operation must support.
2. Apply the declared operation to the named object; record intermediate values that affect interpretation.
3. Check boundary conditions and counterexamples, then emit the result with uncertainty and source links.

If the precision or power requirement is fixed, consider `select-statistical-method` as the next tactic.

## Output contract

```yaml
produces: [estimate_sample_size_result, evidence_trace, uncertainties]
delta_fields: [evidence_updates, uncertainties]
```

## Quality gates

- Inputs are named scientific objects with compatible schemas.
- Every material result has a derivation or source reference.
- Fixed statistical criteria remain exact where applicable: $\alpha$ 0.05 and power 0.8.

## Failure and counterexamples

Return a failed operation with the violated precondition when inputs are incomplete, assumptions are unsupported, or a counterexample defeats the result.

## Provenance map

- intermediate: experiment-execution/sample-size-estimation

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…