compare-porting-feasibility

Orchestrate parallel porting feasibility assessments across evals into YAML, reports, and HTML dashboards.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/EquiStamp/evaluating-evaluations --skill compare-porting-feasibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compare-porting-feasibility
Source: https://github.com/EquiStamp/evaluating-evaluations/tree/main/.claude/skills/compare-porting-feasibility
Command: npx skills add https://github.com/EquiStamp/evaluating-evaluations --skill compare-porting-feasibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end porting feasibility workflow for AI safety evaluations, enabling parallel extraction, reporting, and pairwise comparison across multiple evals.

Core Features & Use Cases

  • Parallel orchestration of extraction (YAML) and reporting for all evals
  • Per-eval control via arguments: default run of all evals, --force, --report-only, --compare-only, and specific eval mapping
  • Generates assessment.yaml, report.md, and HTML dashboard
  • Spawns Task agents for parallel processing and coordinates pairwise comparisons

Quick Start

Run the porting feasibility workflow for all evals using the default configuration.

Frequently Asked Questions about compare-porting-feasibility

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

FAQPage Schema
How do I automate porting feasibility evaluations for multiple AI safety tests in parallel?

Automate porting feasibility evaluations by orchestrating extraction and reporting across multiple evals simultaneously. The workflow reads an eval list, spawns Task agents for parallel processing, and maps eval names to directory slugs to coordinate assessments.

Can I run pairwise comparisons and generate an HTML dashboard for porting feasibility assessments?

Pairwise comparisons generate an HTML dashboard after all individual assessments complete. The system coordinates these comparisons across evals and produces the dashboard to visualize the porting feasibility results.

What's the best way to run a porting feasibility pipeline with only reporting and no extraction?

Run the pipeline with the --report-only option to generate per-eval reports without repeating the extraction phase. This skips YAML assessment file generation and focuses solely on producing the reporting output.

How does YAML fit into the porting feasibility assessment workflow?

YAML assessment files are written during the extraction phase to capture porting feasibility data for each eval. These structured files serve as the foundation for generating per-eval reports and running pairwise comparisons.

Do I need to manually map evaluation names to directory slugs when running parallel feasibility assessments?

Manual mapping is unnecessary because the orchestration automatically maps eval names to directory slugs. This automated mapping ensures correct file paths when reading eval lists and writing assessment outputs.

Why would I use the --force option during a feasibility porting workflow?

Use --force to overwrite existing assessment files and reports during the porting workflow. This ensures all evals are re-processed and updated outputs are generated, even if previous assessment results already exist.