BF eda-spec2gds
Drive an open-source EDA workflow from spec to GDS using OpenClaw skills, workspace files, and CLI tools. Use when the user wants to turn a hardware spec into RTL, testbenches, synthesis results, OpenLane backend runs, GDS output, or report summaries; also use when creating, iterating, or auditing an AgentSkill for AI-driven chip design workflows.
As a process F 52/100 · Will not run — References files that are not bundled: assets/project-template/
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
✓ No critical or high findings
Medium and low: 6
-
low Dangerous commands
cmd-background-processreferences/SECURITY.md:53Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable --now docker
security skill -
low Risky intent
intent-offensive-securityreferences/SECURITY.md:55Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Adds user to Docker group (privilege escalation potential)
-
low Risky intent
intent-offensive-securityreferences/SECURITY.md:93Offensive-security / dual-use content (legitimate for authorised testing; review intended use)1. **Docker Privilege Escalation**
-
low Dangerous commands
cmd-background-processreferences/ubuntu-24-setup.md:47Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable --now docker
security skill -
low Dangerous commands
cmd-background-processscripts/bootstrap_eda_demo.sh:72Starts a background / autostarted processrun_privileged systemctl enable --now docker
-
low Dangerous commands
cmd-background-processscripts/install_ubuntu_24_mvp.sh:23Starts a background / autostarted processsudo systemctl enable --now docker
Files scanned: 52. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/project-template/
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: assets/project-template/
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 84 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1931 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -314 of 25 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 349: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 84 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (9 of 10)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.