Bspdn Pdn Sufficiency Evaluator
Evaluate whether the current BSPDN PDN contract is strong enough under `BPR reserved for PDN`, separating PDN sufficiency from signal-mixing questions.
Install
$ agentstack add skill-mr-fang-vlsi-edagent-bspdn-pdn-sufficiency-evaluator ✓ 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mr-fang-vlsi-edagent-bspdn-pdn-sufficiency-evaluator) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
BSPDN PDN Sufficiency Evaluator
Use this skill when the question is "is the current PDN contract strong enough?" rather than "did backside signal routing help?"
When to use
Use this skill when:
- the project needs to decide whether
BPR + current backside PDNis sufficient, - PDN weakness may be confounding backside-signal conclusions,
Strict-BPR,PDN-boost, orStress-checkcomparisons need a dedicated evaluator,- PDN stability must be judged without letting signal use
BPR.
Scope boundary
This skill owns:
- PDN sufficiency judgments under the current BSPDN contract,
- separating PDN strength questions from signal-routing benefit questions,
- deciding whether the issue is likely
PDN under-strengthvstopology invalidityvscase unsuitability.
It does not own:
- redefining the physical contract itself without
bspdn-physical-contract-auditor, - benefit attribution across
front-only / CTS-backside-only / partial-signal-backside, - general execution orchestration.
Core experiment family
Use this family by default:
Strict-BPRPDN-boostStress-check
Expected outputs
*.results.tsv*.conclusion.md- optional
*.experience_delta.md
Hard rules
- Never answer "PDN is weak" by letting signal use
BPR; that changes the question. - Keep
BPR-reserved-for-PDNintact unless the physical contract is separately overturned. - Distinguish:
- PDN connectivity/stability evidence
- timing side effects
- congestion side effects
- A better
PDN-boostresult implies "strengthen PDN", not "relax the signal contract".
Operational references
- Load
references/background-knowledge-links.mdfor the current summarized PDN-sufficiency knowledge contract. - Load
references/update-mechanism.mdwhen deciding whether the evaluator's assumptions or pass/fail criteria need refresh.
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.