gos-eval

Run golden tests from tests/*.eval.json and generate a JSON pass/fail report.

41|27|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gos-eval
Source: https://github.com/kcleto-ai/growth-os-skills/tree/main/.claude/skills/gos-eval
Command: npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The gos-eval skill provides a deterministic mechanism to run golden tests against Growth OS tooling, capturing failures and producing structured reports to ensure tooling health.

Core Features & Use Cases

  • Runs tests defined in tests/.eval.json against the corresponding gos- tooling scripts.
  • Validates exit codes, stdout contents, and JSON status to produce a comprehensive report.
  • Generates an aggregated JSON outcome for CI/regression checks and audits of the tooling suite.

Quick Start

Execute the evaluator with the script .claude/skills/gos-eval/scripts/eval.py to run all fixtures.

Frequently Asked Questions about gos-eval

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

FAQPage Schema
How do I run deterministic golden tests for Python tooling scripts?

Deterministic golden tests validate tooling health by executing evaluation scripts against test fixtures, checking exit codes, stdout contents, and JSON status to generate a structured pass/fail report for CI and regression checks.

How do I validate exit codes and stdout output for CI regression checks?

Validating exit codes and stdout output for CI regression checks involves running evaluation scripts that enforce strict JSON output, capturing pass/fail status per component to generate an aggregated JSON health report.

What format should test fixtures be in for automated validation?

Test fixtures for automated validation must be strict JSON files placed in the tests/*.eval.json path, enabling the evaluator to execute corresponding Python scripts and verify exit codes, stdout contents, and JSON status reliably.

Does the golden test evaluator produce structured reports for automated auditing?

The golden test evaluator does produce structured JSON reports for automated auditing, aggregating pass/fail outcomes per component based on exit codes, stdout contents, and JSON status validation for reliable tooling health verification.

Why do I need strict JSON output for deterministic testing workflows?

Strict JSON output is needed for deterministic testing workflows to guarantee reliable tooling health verification, ensuring that exit codes, stdout content checks, and pass/fail status remain consistent and parseable across test runs.