scaffold-traced-eval-project

Scaffold a new GAD eval project with standard artifacts from source docs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/B2Gdevs/custom_portfolio --skill scaffold-traced-eval-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold-traced-eval-project
Source: https://github.com/B2Gdevs/custom_portfolio/tree/main/oneoff/v2/intent/skill/scaffold-traced-eval-project
Command: npx skills add https://github.com/B2Gdevs/custom_portfolio --skill scaffold-traced-eval-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the bootstrap of a new GAD eval project from loose source documents into a complete evals/<name>/ directory, ensuring all required artifacts are created.

Core Features & Use Cases

  • Automatically generates critical artifacts: REQUIREMENTS.xml, SCORING.md, gad.json, and a starter template directory.
  • Registers a TRACE.json fragment in lib/trace-schema.cjs to ensure proper schema validation for the new eval domain.
  • Validates and enforces a consistent folder structure so new domains can be evaluated with minimal setup.
  • Triggers when a brand-new eval domain appears that lacks a template, or when a design/requirements doc must be turned into an eval.

Quick Start

Create a new eval project by running gad eval setup --project <name> and follow the prompts.

Frequently Asked Questions about scaffold-traced-eval-project

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

FAQPage Schema
How do I bootstrap a new GAD eval project from loose design documents?

To bootstrap a GAD eval project, run the setup command to automatically generate a standard evals directory containing REQUIREMENTS.xml, SCORING.md, gad.json, and a starter template directory from your source docs.

What artifacts are required when scaffolding an eval domain?

Scaffolding an eval domain requires generating REQUIREMENTS.xml, SCORING.md, gad.json, a starter template directory, and registering a TRACE.json fragment in lib/trace-schema.cjs to ensure proper schema validation.

How do I turn a requirements document into a functional eval benchmark?

You can turn a requirements document into an eval benchmark by triggering the scaffolding workflow, which parses loose source docs and outputs a structured eval directory with standardized scoring and trace artifacts.

Does scaffolding a GAD eval project automatically register the trace schema?

Yes, scaffolding a GAD eval project automatically registers a TRACE.json fragment within the lib/trace-schema.cjs file to ensure proper schema validation for the newly created eval domain.

When do I need to create a new eval project template directory?

You need to create a new eval project template directory when a brand-new eval domain appears that lacks an existing template, or when you must convert design and requirements documents into a structured eval.

What limitations exist when setting up an eval project from source docs?

The setup process focuses strictly on bootstrapping new eval domains from source docs into a standard folder structure; it enforces consistent artifact generation and does not support modifying existing eval project configurations.