generate-porting-feasibility-report

Generate a Google Docs-friendly porting feasibility report from an eval YAML.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill automates turning an existing evaluation YAML into a Google Docs-friendly porting feasibility report, enabling rapid portability analysis.

Core Features & Use Cases

  • Generate a complete porting feasibility document from an eval YAML.
  • Produce a standardized structure ready for review in Google Docs.
  • Support for mapping eval questions to a fixed Inspect porting template.

Quick Start

Run the porting feasibility workflow on the target eval YAML to generate a Google Docs-friendly feasibility report.

Frequently Asked Questions about generate-porting-feasibility-report

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

FAQPage Schema
How do I generate a porting feasibility report from an evaluation YAML?▼

To generate a porting feasibility report, the Skill parses your evaluation YAML and maps the questions to a fixed Inspect porting template, outputting a Google Docs-friendly markdown file instantly. It writes the final report directly to the assessment directory.

Can I create a Google Docs-friendly feasibility report from my eval assessments?▼

Yes, you can create a Google Docs-friendly feasibility report by running this workflow on your eval assessment YAML. It produces a standardized markdown structure ready for immediate review and import into Google Docs.

What is the process for converting eval YAML files into markdown reporting templates?▼

The process involves locating your source assessment YAML, mapping its contents to a predefined porting template, and writing the generated markdown report to your local assessments directory. This provides a rapid portability analysis document.

Do I need to specify a file path to generate a porting feasibility markdown file?▼

You do not need to specify a path if your evaluation YAML is located in the default ./assessments/*/assessment.yaml directory. The Skill can also accept a user-provided path to locate the source evaluation YAML.

Where does the generated porting feasibility markdown report get saved?▼

The generated porting feasibility markdown report is saved locally to ./assessments/<eval-name-slugified>/report.md. The workflow provides a brief confirmation message containing the exact output path after successful generation.