bb-invoke-klayout

Automate KLayout GDSII export, DRC checks, and signoff verification.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill bb-invoke-klayout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bb-invoke-klayout
Source: https://github.com/amoslee2026/Babel/tree/main/.claude/skills/bb-invoke-klayout
Command: npx skills add https://github.com/amoslee2026/Babel --skill bb-invoke-klayout

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill centralizes and automates the KLayout-based GDSII export, GDS level DRC checks, and final signoff verification for PD workstreams.

Core Features & Use Cases

  • GDSII export via KLayout in batch mode
  • GDS layer DRC checks with ASAP7 tech reference
  • Post-export verification and signoff readiness

Quick Start

Trigger KLayout-based GDSII export, DRC checks, and post-export verification for PD signoff.

Frequently Asked Questions about bb-invoke-klayout

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

FAQPage Schema
How do I automate GDSII export and DRC checks for KLayout signoff?

Automate KLayout signoff by triggering batch GDSII export, GDS layer DRC checks, and post-export verification to generate artifacts, logs, and a JSON result with violation counts per run.

What is KLayout batch mode used for in physical design signoff?

KLayout batch mode is used for end-to-end GDSII export, GDS level DRC checks, and final signoff readiness verification for routed physical design workstreams.

Does KLayout DRC validation work with ASAP7 technology?

Yes, this KLayout DRC validation supports ASAP7 technology references, applying tech files and runsets to execute GDS layer checks for routed physical design signoff.

How do I trace DRC violations and verify signoff readiness after GDS export?

Trace DRC violations and verify signoff readiness by reviewing the generated JSON result per run, which outputs violation counts, gds_size_bytes, verify_ok, valid, and error statuses.

What inputs do I need to run KLayout GDSII export and DRC checks?

Run KLayout GDSII export and DRC checks by providing input_def, tech_file, action, design_name, top_module, runset, and stamp parameters to configure the pipeline.

Why does my KLayout signoff pipeline fail to generate valid GDSII artifacts?

KLayout signoff pipelines may fail due to missing tech_file or runset parameters; check the error and valid fields in the output JSON result and review the generated log_path for details.