skills/bscost-net/SKILL.md
Plan and execute internet-assisted backside net cost modeling for signal and clock nets, then evaluate stability and correlation against HPWL baselines across multiple designs. Use when users ask to improve/validate backside cost models, choose benchmark designs, compare model vs HPWL, or prepare publishable model-evaluation evidence.
npx skillsauth add mr-fang-vlsi/edagent bscost-netInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to move model work from single-design intuition to reproducible, multi-design evidence.
This skill should stay linked to:
eda-context-accessor when current KB or tool context needs to be refreshed before benchmark or evaluation design.If the planned benchmark set or evaluation claim conflicts with current KB or paper-derived background knowledge, keep that conflict explicit and route KB feedback instead of silently proceeding.
contract.md/tsv and bucketed.md/tsvreferences/background-knowledge-links.md when deciding which KB notes, paper-derived artifacts, and benchmark assumptions are authoritative for the current study.references/benchmark_candidates.md when selecting the benchmark panel or deciding whether the current panel is too narrow.references/web_research_protocol.md when network-backed benchmark expansion or provenance checking is required.references/model_plan.md when designing signal-net and clock-net modeling tracks and aligned output fields.references/evaluation-protocol.md when setting Gate-0/Gate-1 evaluation structure, HPWL comparison, or stability-panel reporting.references/promotion-gate.md when deciding whether the model remains in shadow mode or is eligible for active optimization.development
Create immutable stage checkpoints for Innovus flows. Use when users ask for fixed golden files or restart-from-stage workflows (place/cts/route) with matched DEF+V+SDC and reproducible manifests.
tools
Capture and maintain reusable script-writing experience across wrappers, helpers, parsers, validators, and runtime shims so future script work can reuse proven patterns and avoid repeated anti-patterns.
testing
Summarize local paper PDFs into structured, citation-grounded evidence notes. Use when the user provides local PDF paths and asks for methods/assumptions/results/limitations extraction or wants evidence mapped to current EDA hypotheses.
development
Fetch primary-source paper metadata when evidence is missing or weak for EDA/model/flow claims. Use for requests like building reproducible paper candidate lists, generating user-download queues, and recording citation metadata for local validation.