rat-setup

Audit and configure EDA toolchains for RTL design and verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the local machine has the complete EDA toolchain and plugin configuration required for the RTL Agent Team pipeline so design and verification agents do not fail with tool-not-found or misconfiguration errors. It audits required, recommended, and optional tools, checks test infrastructure and commercial tool availability, and prevents wasted time troubleshooting environment issues.

Core Features & Use Cases

  • Parallel environment audit: Runs Bash-based checks to detect Tier 1 (required), Tier 2 (recommended), and Tier 3 (optional) EDA tools including python3, g++, make, verilator, cocotb, SystemC, verible/slang, svlens, yosys, and docker.
  • Interactive remediation: Prompts the user to choose local installs, global (sudo) command suggestions, or a Docker fallback, plus handles commercial tool env_source entries and verifies them.
  • Persistence and deployment: Writes machine-wide env-config.json, a setup completion marker, and can non-destructively deploy global CLAUDE rules (e.g., ~/.claude/rules/ and diagram policy) for consistent RTL conventions.
  • Use case: When onboarding a new workstation or CI runner, run this skill to validate tooling, install missing open-source tools locally, register commercial tool sourcing commands, and produce a verified environment for the 6-phase RTL pipeline.

Quick Start

Run the rat-setup skill to audit this machine, install missing EDA tools locally by default, and record the machine-wide environment configuration.

Frequently Asked Questions about rat-setup

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

FAQPage Schema
How do I verify and install the EDA toolchain for RTL design and verification?

You can verify and install the EDA toolchain by running a parallel Bash-based audit that detects required, recommended, and optional tools like Verilator, cocotb, and SystemC, interactively remediating missing tools via local, global, or Docker fallback options.

How do I set up SystemC, cocotb, and Verilator for an automated RTL pipeline?

To set up SystemC, cocotb, and Verilator, the skill audits your machine in parallel, categorizes these tools into required and recommended tiers, and interactively remediates missing components through local installs, global sudo commands, or a Docker fallback.

Do I need Docker to install Verilator and cocotb if they are missing from my workstation?

Docker is not strictly required to install Verilator and cocotb, as the setup process offers local installs and global sudo command suggestions first, using Docker only as an optional fallback for Tier 3 tooling if local installation is not feasible.

What is the best way to configure commercial EDA tool environments for CI runners?

The best way to configure commercial EDA tool environments is to register their env_source entries during the interactive remediation phase, which verifies the sourcing commands and persists the configuration machine-wide in an env-config.json file.

How does the EDA toolchain setup persist environment configurations across multiple projects?

The EDA toolchain setup persists environment configurations by writing a machine-wide env-config.json file and a setup completion marker, ensuring consistent RTL conventions and preventing tool-not-found errors across automated design and verification pipelines.