formal-verification SKILL.md skillA
formal-verification from hdl-tools/digital-chip-design-agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hdl-tools/digital-chip-design-agents/formal-verification@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hdl-tools/digital-chip-design-agents
- Path
plugins/formal/skills/formal-verification/SKILL.md- Versions recorded
- 7
- Latest version
- v1.0.0, committed Oct 2, 2026
- First version recorded
- Apr 17, 2026
- Size
- 13,616 bytes
- Repository stars
- 220
- License
- MIT
Formal property verification (FPV) and logical equivalence checking (LEC). Use when proving design properties exhaustively, checking RTL vs gate-level netlist equivalence, verifying CDC crossings formally, or closing verification coverage gaps that simulation cannot efficiently reach.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Skill: Formal Verification (FPV + LEC) ## Invocation When this skill is loaded and a user presents a formal verification task, **do not execute stages directly**. Immediately spawn the `digital-chip-design-agents:formal-orchestrator` agent and pass the full user request and any available context to it. The orchestrator enforces the stage sequence, loop-back rules, and sign-off criteria defined below. Use the domain rules in this file only when the orchestrator reads this skill mid-flow for stage-specific guidance, or when the user asks a targeted reference question rather than requesting a full flow execution. ## Pre-run Context Before executing or advising on **any** stage, read the following files if they exist: 1. `memory/formal/knowledge.md` — known failure patterns, successful tool flags, PDK/tool quirks. Incorporate its guidance into every stage decision. If absent, proceed without it. 2. `memory/formal/run_state.md` — current run identity (`run_id`, `design_name`, `tool`, `last_stage`). Use this to resume correctly after interruption. If absent, a new run is starting; the orchestrator will create this file before the first stage. …
Read the whole file at its exact version.
How to install
mdr add hdl-tools/digital-chip-design-agents/formal-verification@sha256:0b32d3d52c2eb4a3The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vedzmwg6yry5aikh)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Apr 17, 2026 and Oct 2, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-02 | e243902 | 13,616 B | A | view · diff |
| v1.0.0 | 2026-10-01 | a4478ea | 13,558 B | A | view · diff |
| v1.0.0 | 2026-05-31 | 9bdd652 | 10,269 B | A | view · diff |
| v1.0.0 | 2026-04-25 | b61e057 | 9,548 B | A | view · diff |
| v1.0.0 | 2026-04-25 | 40d51f7 | 9,406 B | A | view · diff |
| v1.0.0 | 2026-04-18 | 741e3d0 | 7,845 B | A | view · diff |
| v1.0.0 | 2026-04-17 | ac5c224 | 7,672 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13616 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hdl-tools/digital-chip-design-agents · 220 stars · license MIT · pushed 2026-10-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_vedzmwg6yry5aikh GET https://markdownregistry.com/api/v1/resolve?ref=hdl-tools/digital-chip-design-agents/formal-verification GET https://markdownregistry.com/api/v1/blob/0b32d3d52c2eb4a3009180a5354de1e37c1f65b93d0b6a557ac3fd90f286e9da
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hdl-tools/digital-chip-design-agents
Every file in hdl-tools/digital-chip-design-agents