evaluation-anchor-checker

Audit and rewrite numeric claims with task, metric, and constraint context.

497|38|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill evaluation-anchor-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evaluation-anchor-checker
Source: https://github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.codex/skills/evaluation-anchor-checker
Command: npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill evaluation-anchor-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the common issue in technical surveys where strong numeric or performance claims are made without sufficient context, making them difficult for reviewers to verify and potentially leading to rejection.

Core Features & Use Cases

  • Numeric Claim Auditing: Reviews sentences containing numbers to ensure they are accompanied by minimal, interpretable evaluation context (task, metric, constraint).
  • Contextual Downgrading: Weakens or removes numeric claims if the necessary context is missing, preventing guesswork and maintaining evidence-boundedness.
  • Ambiguous Naming Check: Flags and corrects underspecified model names that appear hallucinated.
  • Use Case: Before submitting a research paper, use this Skill to automatically scan all claims like "Model X achieved 90% accuracy" and ensure they are rewritten to include the specific task and metric, e.g., "On the ImageNet classification task, Model X achieved ~90% top-1 accuracy".

Quick Start

Use the evaluation anchor checker skill to audit and rewrite numeric claims in the provided workspace.

Frequently Asked Questions about evaluation-anchor-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure numeric claims in my technical document are reviewer-safe?

To make numeric claims reviewer-safe, audit performance statements to include minimal protocol context like the specific task, metric, and constraints. Rewriting underspecified claims prevents reviewer confusion and potential paper rejection.

What happens to numeric claims that lack sufficient evaluation context?

Numeric claims lacking sufficient evaluation context undergo contextual downgrading, which weakens or removes the unsupported performance metrics. This process maintains evidence-boundedness and prevents guesswork by reviewers verifying the document.

How do I fix underspecified model names in technical writing before submission?

Fixing underspecified model names involves flagging ambiguous identifiers that appear hallucinated and correcting them within the text. This ensures technical surveys maintain clear attribution and citation integrity for performance benchmarks.

Can I automatically scan technical surveys for missing metric and task constraints?

Yes, you can automatically scan technical surveys to find numeric claims missing metric and task constraints. The auditing process reviews sentences containing numbers to ensure they feature interpretable evaluation context.

Why does my research paper get flagged for lacking protocol context?

Research papers get flagged for lacking protocol context when strong numeric claims are made without specifying the task, metric, or constraints. This missing context makes performance claims difficult for reviewers to verify accurately.