scoring-checks

Implement deterministic scoring checks in src/scoring/checks/ and wire them into the orchestrator.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Buckeyes22/weather-app --skill scoring-checks-buckeyes22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scoring-checks
Source: https://github.com/Buckeyes22/weather-app/tree/main/docs/corpora/caliber/skills/scoring-checks
Command: npx skills add https://github.com/Buckeyes22/weather-app --skill scoring-checks-buckeyes22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided pattern for adding deterministic scoring checks to the scoring system, ensuring consistency and integration with existing constants and orchestration.

Core Features & Use Cases

  • Standardizes the process for creating checks in src/scoring/checks/ and wiring them into the index.ts orchestrator.
  • Leverages ScoringContext fingerprint data and git history to keep checks deterministic and auditable.
  • Uses existing constants and types to ensure compatibility across the scoring pipeline.

Quick Start

Create a new check named {check-name} that follows the exported default function signature and returns a Check[], wire it into the orchestrator in src/scoring/index.ts, then run TypeScript compilation and tests.

Frequently Asked Questions about scoring-checks

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

FAQPage Schema
How do I add deterministic scoring checks to a TypeScript scoring system?

To add deterministic scoring checks, create a new check in src/scoring/checks/ that follows the default function signature, wire it into the orchestrator in src/scoring/index.ts, and validate the integration using TypeScript compilation and existing tests.

What are deterministic scoring checks and when do I need them?

Deterministic scoring checks are standardized validation functions that ensure consistent and auditable scoring results by leveraging ScoringContext fingerprint data and git history. You need them when adding reliable, repeatable scoring logic to your pipeline.

How do I wire a new scoring check into the orchestrator?

You wire a new scoring check into the orchestrator by importing your Check[] returning function into src/scoring/index.ts. Reference shared values from src/scoring/constants.ts to maintain compatibility across the scoring pipeline.

Do I need existing tests to validate new scoring checks?

Yes, you need existing tests to validate new scoring checks. Running TypeScript compilation and the existing test suite confirms that your newly wired check integrates correctly with the orchestrator and maintains system consistency.

What's the best way to keep scoring checks auditable?

The best way to keep scoring checks auditable is to leverage ScoringContext fingerprint data and git history within your check implementations. This approach ensures that every scoring result is traceable and deterministic.

Can I use custom constants instead of src/scoring/constants.ts for scoring checks?

You should use existing constants from src/scoring/constants.ts rather than custom values. Using the established constants ensures compatibility across the scoring pipeline and maintains consistency with other wired checks.