Skip to content
Back to skills

Analyze Heterogeneity

ASecurity

Identify clinical, methodological, and statistical heterogeneity sources and prioritize subgroup/meta-regression/outlier investigation.

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

Works with

  • cli

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill analyze-heterogeneity --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze Heterogeneity?

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

Security grade badge for Analyze Heterogeneity
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-analyze-heterogeneity/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-analyze-heterogeneity)

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: analyze-heterogeneity
description: "Identify clinical, methodological, and statistical heterogeneity sources and prioritize subgroup/meta-regression/outlier investigation."
---

# analyze-heterogeneity

## Purpose

Identify clinical, methodological, and statistical heterogeneity sources and prioritize subgroup, meta-regression, or outlier investigation.

## Input contract

```yaml
required: [evidence_records, outcome_schema, comparison_context]
optional: [covariate_schema, effect_estimates, subgroup_hypotheses]
constraints: [heterogeneity claims require record-level conditions and provenance]
```

## Procedure

1. Group records by declared design, population, intervention, outcome, and condition dimensions.
2. Compare effect or performance patterns within and across groups.
3. Identify plausible moderators, outliers, and confounding condition differences.
4. Prioritize subgroup or meta-regression investigations and record uncertainty.

If unexplained variation may reflect selective reporting rather than substantive moderators, consider `assess-publication-bias` as the next tactic.

## Output contract

```yaml
produces: [heterogeneity_sources, moderator_candidates, outlier_list, investigation_priorities]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]
```

## Quality gates

- Each heterogeneity source must point to affected records and a comparison dimension.
- Do not infer a moderator from a single discrepant record without an uncertainty marker.

## Failure and counterexamples

Do not label ordinary measurement noise as a causal subgroup effect, and do not pool records whose condition vectors are incomparable.

## Provenance map

- `resolved: heterogeneity-source-analysis`
- `resolved: heterogeneity-investigation`

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…