Install
$ agentstack add skill-mr-fang-vlsi-edagent-control-postrun-retro ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Control Postrun Retro
Overview
Use this skill immediately after an experiment batch finishes. It converts raw artifacts into a structured "what happened / why / what next" decision and gates whether a recursive next run is justified. It does not own the durable experiment-experience registry; consume that through eda-experiment-phenomenology-analyst.
Inputs
Minimum required:
- run summary markdown (
*.summary.md) - monitor/history (
*.monitor.md,*.monitor.history.tsv) or manifest (*.tsv) - key report sources (postCTS/postRoute summary, DRV/type/length distributions, gate outputs)
Optional but preferred:
- knowledge-base references used for this batch
- web/primary-source references for unstable assumptions
- structured evidence-lift artifacts from
eda-experiment-phenomenology-analyst:
*.results.tsv/json*.conclusion.md*.experience_delta.md
Workflow
- Consolidate observations
- prefer the structured
resultlayer when available; only re-open raw logs to resolve contradictions. - extract the smallest set of outcome metrics:
- timing (
WNS/TNS/ViolPaths) - PPA (
power/area/runtime) - geometry/routing (
backside usage,type/length distribution,long-net capture) - gate status (
H1/H2/H3or equivalent)
- Diagnose mechanism, not symptoms
- assign one primary mechanism and optional secondary mechanisms:
model_mismatchflow_policy_mismatchresource_capacity_conflicttool_stability_issueinsufficient_evidence
- Score improvement proposals
- for each candidate change, score:
confidence(low/medium/high)impact(low/medium/high)cost(low/medium/high)risk(low/medium/high)
- Decide recursion
- trigger recursive
workflow-scoped-executiononly when: - confidence >= medium
- expected impact >= medium
- risk is acceptable
- evidence gap is not blocking
- otherwise, request focused data collection first.
- Emit retrospective artifact
- write one markdown summary under
slurm_logs/04_delay_modeling/: .retro.md- include:
- hypothesis validation state
- chosen next step
- explicit stop condition for the next iteration
- which new or reinforced
experienceitems were relied on
References
Load as needed:
references/retro-checklist.mdreferences/recursive-loop-policy.md
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Mr-Fang-VLSI
- Source: Mr-Fang-VLSI/EDAgent
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.