Skip to content
Back to skills

Analyze Leaderboard Dynamics

ASecurity

Analyze leaderboard score distributions, compression/saturation, anomalies, selective reporting, and regime shifts.

  • 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 analyze-leaderboard-dynamics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze Leaderboard Dynamics?

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

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

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-leaderboard-dynamics
description: "Analyze leaderboard score distributions, compression/saturation, anomalies, selective reporting, and regime shifts."
---

# analyze-leaderboard-dynamics

## Purpose

Analyze leaderboard score distributions, compression or saturation, anomalies, selective reporting, and regime shifts.

## Input contract

```yaml
required: [leaderboard_records, metric_schema, time_or_version_field]
optional: [evaluation_protocols, source_quality, method_metadata]
constraints: [scores require task, metric, condition, source, and observation provenance]
```

## Procedure

1. Normalize scores and evaluation conditions into comparable groups.
2. Inspect distributions, rank movement, compression, and missingness.
3. Identify anomalies, selective reporting, and regime changes.
4. State whether additional evidence is continuing, near-saturated, or saturated.

## Output contract

```yaml
produces: [leaderboard_distribution, regime_segments, anomaly_report, saturation_assessment]
delta_fields: [findings, evidence_updates, uncertainties, decisions]
```

## Quality gates

- Every reported regime or anomaly must cite the records and comparison basis.
- Do not compare scores across incompatible protocols without an explicit limitation.

## Failure and counterexamples

Do not treat rank order as progress when metric definitions or evaluation conditions changed; preserve ties and missing observations.

## Provenance map

- `resolved: leaderboard-dynamics-analysis`

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…