syn-tool-profiles

Generate replayable synthesis profiles for yosys, dc_shell, and genus.

43|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/babyworm/rtl-agent-team --skill syn-tool-profiles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: syn-tool-profiles
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/syn-tool-profiles
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill syn-tool-profiles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the lack of standardized benchmarks and artifact formats when comparing synthesis flows across tools (yosys, dc_shell, genus) by providing reusable profiles and a common output structure.

Core Features & Use Cases

  • Provides common contract and a consistent output directory structure for replayable runs.
  • Supports open-source and commercial tools (yosys, dc_shell, genus) with baseline and specialized profiles.
  • Generates standardized summaries and artifacts stored under syn/db/, syn/vnet/, syn/svf/, syn/scr/, syn/rpt/, syn/log/, syn/temp/, syn/work/ to enable easy comparison.

Quick Start

Run the wrapper script to generate reproducible synthesis profiles for your project using yosys, dc_shell, or genus.

Frequently Asked Questions about syn-tool-profiles

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

FAQPage Schema
How do I standardize synthesis benchmarking across yosys, dc_shell, and genus?

Standardize synthesis benchmarking by generating replayable profiles for yosys, dc_shell, and genus that produce consistent artifacts like .ddc or .genus_db in a defined directory structure. This enables direct performance comparisons across open-source and commercial toolchains.

What is the best way to organize synthesis outputs for consistent toolchain comparisons?

Organize synthesis outputs by running the provided wrapper script syn/scripts/run_syn.sh, which automatically structures generated artifacts into subfolders under syn/ like db/, vnet/, svf/, scr/, rpt/, log/, temp/, and work/ for easy comparison.

Can I use the same synthesis profiles for both open-source and commercial design flows?

Yes, you can use the same synthesis profiles across both open-source and commercial design flows. The profiles support yosys, dc_shell, and genus, ensuring baseline and specialized runs produce comparable netlists and summaries.

How do I generate replayable synthesis runs for multiple tools?

Generate replayable synthesis runs by executing the wrapper script syn/scripts/run_syn.sh. This applies reusable profiles to your project, outputting standardized summaries and artifacts into the organized syn/ directory structure for yosys, dc_shell, or genus.

What artifacts are generated when comparing synthesis flows across different tools?

Generated synthesis artifacts include .ddc, .genus_db, and netlists, alongside standardized summaries. These are consistently organized into subfolders like syn/db/, syn/vnet/, syn/svf/, syn/scr/, syn/rpt/, syn/log/, syn/temp/, and syn/work/.