Skip to content
Back to skills

Decompose Evaluation Metric

ASecurity

Decompose an evaluation metric into rewarded signals, aggregation choices, polarity, ceiling effects, and Goodhart vulnerabilities.

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

Works with

  • cli

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill decompose-evaluation-metric --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Decompose Evaluation Metric?

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

Security grade badge for Decompose Evaluation Metric
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-decompose-evaluation-metric/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-decompose-evaluation-metric)

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: decompose-evaluation-metric
description: "Decompose an evaluation metric into rewarded signals, aggregation choices, polarity, ceiling effects, and Goodhart vulnerabilities."
---

# decompose-evaluation-metric

## Purpose

Decompose an evaluation metric into rewarded signals, aggregation choices, polarity, ceiling effects, and Goodhart vulnerabilities.

## Input contract

```yaml
required: [metric_definition, scored_outputs]
optional: [reference_standard, aggregation_rule, known_failure_cases]
constraints: [each component must have a declared direction and interpretation]
```

## Procedure

1. Split the metric into primitive signals and aggregation operations.
2. Record polarity, scale, weighting, normalization, and ceiling/floor behavior.
3. Map rewarded shortcuts and construct-irrelevant incentives.
4. State interpretation limits and diagnostic needs.

If metric components are explicit but their link to the intended construct remains uncertain, consider `assess-construct-validity` as the next tactic.

## Output contract

```yaml
produces: [metric_components, aggregation_map, polarity_and_scale, ceiling_analysis, goodhart_risks]
delta_fields: [findings, evidence_updates, uncertainties, open_questions]
```

## Quality gates

- Component contributions and aggregation are reconstructible.
- A high score is not treated as capability evidence without construct support.

## Failure and counterexamples

Do not infer metric meaning from its name or ignore nonlinear aggregation and clipping.

## Provenance map

- `resolved: metric-decomposition`

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…