chipyard

Detect local Chipyard installations and Docker availability to route hardware workflows.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xsw632/ChipAgent --skill chipyard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chipyard
Source: https://github.com/xsw632/ChipAgent/tree/main/skills/chipyard
Command: npx skills add https://github.com/xsw632/ChipAgent --skill chipyard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users working with Chipyard hardware design workflows must manually configure their backend execution environment (local or Docker), leading to setup errors, inconsistent results, and wasted time switching between development setups.

Core Features & Use Cases

  • Automatic Backend Detection: Scans the system for local Chipyard, ORFS, Java, sbt installations and Docker availability to determine the optimal execution environment without user input.
  • Unified Workflow Routing: Automatically directs to the correct pre-defined Chipyard workflow skill (local or Docker) based on the detected backend mode, eliminating manual skill selection and configuration steps.
  • Use Case: A hardware engineer can run Chipyard flows on both their local development machine and a shared Docker environment without adjusting commands or reconfiguring tools for each setup.

Quick Start

Use the chipyard skill to automatically detect your system's Chipyard backend configuration and run the appropriate hardware workflow without manual setup.

Frequently Asked Questions about chipyard

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

FAQPage Schema
How do I configure the Chipyard backend for local hardware design workflows?

Chipyard backend configuration is automated by detecting local installations and Docker availability. The system scans for Chipyard, ORFS, Java, and sbt installations to route execution to the optimal environment, eliminating manual backend setup for hardware design workflows.

Does Chipyard work with Docker for Verilog and Chisel development?

Yes, Chipyard works with Docker for Verilog and Chisel development by detecting Docker availability during backend routing. It automatically directs execution to a pre-defined Docker container workflow if local tool installations are not optimal for the hardware engineering setup.

How do I switch between local and Docker environments in Chipyard?

Switching between local and Docker environments in Chipyard requires no manual commands. The unified workflow routing automatically detects your system configuration and directs execution to the appropriate pre-defined workflow skill for either local or Docker backend mode.

Do I need to manually install sbt and Java before running Chipyard?

Manual sbt and Java installation is not required to initiate routing. The backend detection mechanism scans for local Chipyard, ORFS, Java, and sbt installations to determine the optimal execution environment, automatically falling back to Docker if local dependencies are missing.

Why does my Chipyard setup fail when switching development machines?

Chipyard setup fails from manual backend configuration errors when switching machines. Automatic backend detection resolves this by scanning each system for local tools and Docker availability, routing execution to the correct pre-defined workflow without environment-specific friction.