qor-report

Generate an FPGA design-health scorecard from Vivado timing, utilization, power, and congestion metrics.

11|7|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/LNC0831/oh-my-fpga --skill qor-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qor-report
Source: https://github.com/LNC0831/oh-my-fpga/tree/main/skills/qor-report
Command: npx skills add https://github.com/LNC0831/oh-my-fpga --skill qor-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, fragmented process of gathering FPGA design metrics by providing a consolidated, one-page health report that grades timing, area, power, and congestion.

Core Features & Use Cases

  • Automated Scorecarding: Aggregates data across six critical axes including timing, utilization, and DRC/methodology.
  • Objective Grading: Uses a standardized rubric to classify design health as PASS, MARGINAL, or FAIL based on current tool evidence.
  • Use Case: Before a design review or sign-off, use this skill to generate an objective snapshot of your implementation status to identify if the design is ready for tapeout.

Quick Start

Invoke the qor-report skill to generate a comprehensive design health scorecard for the currently open Vivado project.

Frequently Asked Questions about qor-report

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

FAQPage Schema
How do I generate an FPGA design health scorecard in Vivado?

To generate an FPGA design health scorecard, use a skill that analyzes timing, utilization, power, congestion, and rule-cleanliness metrics from synthesized or implemented Vivado designs. This provides an objective assessment of design readiness for signoff.

What metrics are evaluated during FPGA timing and utilization analysis for signoff?

FPGA timing and utilization analysis for signoff evaluates six critical axes: timing, utilization, power, congestion, and DRC/methodology rule-cleanliness. These metrics are aggregated to classify design health as PASS, MARGINAL, or FAIL based on current tool evidence.

Do I need an active SynthPilot MCP connection to evaluate Vivado implementation status?

Yes, an active SynthPilot MCP connection is required to evaluate Vivado implementation status. The connection executes read-only tool queries to gather metrics and synthesize a consolidated report.

Can I use automated scorecarding to identify FPGA design readiness before tapeout?

Yes, automated scorecarding can identify FPGA design readiness before tapeout by generating an objective snapshot of implementation status. It uses a standardized rubric to classify design health as PASS, MARGINAL, or FAIL.

What's the best way to consolidate fragmented FPGA design metrics into a single report?

The best way to consolidate fragmented FPGA design metrics is to use an automated scorecarding skill that aggregates data across timing, area, power, and congestion into a one-page health report.