Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

vivado-reports

Sterne3

Forks0

Aktualisiert22. April 2026 um 23:03

Parse Vivado reports and produce a structured design health score. Use when analyzing run results, comparing multiple runs, generating a health score, or surfacing key findings from report files.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

devansh0703

devansh0703/vivaclaw-agent

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	vivado-reports
version	1.0.0
description	Parse Vivado reports and produce a structured design health score. Use when analyzing run results, comparing multiple runs, generating a health score, or surfacing key findings from report files.
metadata	{"openclaw":{"requires":{"bins":["vivado"]},"emoji":"📊"}}

Vivado Reports Runbook

1. Standard Report Suite

report_utilization -file /tmp/vivaclaw_rpt/utilization.rpt
report_timing_summary -file /tmp/vivaclaw_rpt/timing.rpt
report_cdc -file /tmp/vivaclaw_rpt/cdc.rpt
report_drc -file /tmp/vivaclaw_rpt/drc.rpt
report_power -file /tmp/vivaclaw_rpt/power.rpt
report_design_analysis -complexity -congestion -file /tmp/vivaclaw_rpt/analysis.rpt

2. Design Health Score (Max 100)

Timing (25 pts): WNS >= 0 (25), -5 per 0.5ns violation.
Constraints (20 pts): -5 per no_clock, -2 per unconstrained I/O.
CDC (20 pts): 0 unwaived (20), -10 per Type B violation.
DRC (15 pts): 0 CRITICAL (15), -5 per CRITICAL.
Utilization (10 pts): All < 80% (10), -5 if any > 90%.
Power (10 pts): SAIF annotated (5), power_opt used (5).

3. Headline Extraction (Shell)

grep "WNS=" timing.rpt | awk '{print $NF}'
grep "Slice LUTs" utilization.rpt | awk '{print $NF}'
grep -c "CRITICAL WARNING" drc.rpt

4. Anomaly Detection

Utilization jump > 5% without RTL change.
WNS improved but TNS worsened (systemic issue).
Logic levels increased post-phys_opt (unintended path creation).

Mehr aus diesem Repository

gleiches Repository

vivado-flow

devansh0703/vivaclaw-agent

Run a complete Vivado FPGA design flow from RTL sources to bitstream. Use when asked to synthesize, implement, build, or compile an FPGA design. Also handles project creation, checkpoint management, and run orchestration.

2026-04-223

vivado-cdc

devansh0703/vivaclaw-agent

Analyze and fix clock domain crossing violations. Use when CDC violations appear, when auditing multi-clock designs, or when reviewing set_false_path and set_max_delay exceptions for safety.

2026-04-223

vivado-constraints

devansh0703/vivaclaw-agent

Author and audit Vivado XDC constraint files. Use when creating constraints, finding unconstrained paths, debugging timing exceptions, checking clock definitions, or auditing I/O delays for completeness.

2026-04-223

vivado-debug

devansh0703/vivaclaw-agent

Insert ILA and VIO debug cores into a Vivado design. Use when asked to add hardware debug probes, set up ILA trigger conditions, insert VIO for stimulus injection, or generate .ltx probeinfo files.

2026-04-223

vivado-floorplan

devansh0703/vivaclaw-agent

Create Pblock floorplan constraints in Vivado. Use when dealing with placement congestion, SSI multi-die devices, reconfigurable partitions (DFX), or when critical paths need physical locality.

2026-04-223

vivado-flow

devansh0703/vivaclaw-agent

Run a complete Vivado design flow: project creation, synthesis, implementation, bitstream. Use when asked to build, synthesize, implement, or compile an FPGA design from RTL sources.

2026-04-223

name	vivado-reports
version	1.0.0
description	Parse Vivado reports and produce a structured design health score. Use when analyzing run results, comparing multiple runs, generating a health score, or surfacing key findings from report files.
metadata	{"openclaw":{"requires":{"bins":["vivado"]},"emoji":"📊"}}

Vivado Reports Runbook

1. Standard Report Suite

report_utilization -file /tmp/vivaclaw_rpt/utilization.rpt
report_timing_summary -file /tmp/vivaclaw_rpt/timing.rpt
report_cdc -file /tmp/vivaclaw_rpt/cdc.rpt
report_drc -file /tmp/vivaclaw_rpt/drc.rpt
report_power -file /tmp/vivaclaw_rpt/power.rpt
report_design_analysis -complexity -congestion -file /tmp/vivaclaw_rpt/analysis.rpt

2. Design Health Score (Max 100)

Timing (25 pts): WNS >= 0 (25), -5 per 0.5ns violation.
Constraints (20 pts): -5 per no_clock, -2 per unconstrained I/O.
CDC (20 pts): 0 unwaived (20), -10 per Type B violation.
DRC (15 pts): 0 CRITICAL (15), -5 per CRITICAL.
Utilization (10 pts): All < 80% (10), -5 if any > 90%.
Power (10 pts): SAIF annotated (5), power_opt used (5).

3. Headline Extraction (Shell)

grep "WNS=" timing.rpt | awk '{print $NF}'
grep "Slice LUTs" utilization.rpt | awk '{print $NF}'
grep -c "CRITICAL WARNING" drc.rpt

4. Anomaly Detection

Utilization jump > 5% without RTL change.
WNS improved but TNS worsened (systemic issue).
Logic levels increased post-phys_opt (unintended path creation).