pipeline-orchestration SKILL.md skillA
pipeline-orchestration 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/pipeline-orchestration@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/meta/skills/pipeline-orchestration/SKILL.md- Versions recorded
- 8
- Latest version
- v1.0.0, committed Oct 3, 2026
- First version recorded
- Jun 8, 2026
- Size
- 29,113 bytes
- Repository stars
- 220
- License
- MIT
Cross-domain loop orchestration for the chip design pipeline. Provides the fix_request protocol, iteration-cap logic, escalation templates, and dispatch patterns for routing verification/formal failures to the RTL orchestrator and back. Use when driving the closed-loop verification↔RTL feedback cycle.
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: Pipeline Orchestration ## Invocation - **If invoked by a user** presenting a pipeline loop task: immediately spawn the `digital-chip-design-agents:pipeline-orchestrator` agent and pass the full user request and any available context. Do not execute stages directly. - **If invoked inside another orchestrator**: read `design_state.json`, summarise open `fix_requests[]`, and return — do not spawn subagents (anti-recursion rule). ## Purpose This skill provides the closed-loop verification↔RTL feedback protocol. When a DUT bug is found during simulation or formal verification, it must be communicated to the RTL orchestrator in a machine-actionable way and the pipeline must iterate until the bug is fixed or the iteration limit is reached. The protocol has three participants: | Participant | Role | |---|---| | **verification-orchestrator** / **formal-orchestrator** | Detects the bug; writes a `fix_request` entry to `design_state.fix_requests[]` with `status=open`; terminates with `decision=escalate`. | | **rtl-design-orchestrator** | Reads the open `fix_request`; sets `status=claimed`; fixes the RTL; sets `status=fixed` with `rtl_response`; terminates. | …
Read the whole file at its exact version.
How to install
mdr add hdl-tools/digital-chip-design-agents/pipeline-orchestration@sha256:e3e806be311a42c3The 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_aksuusvuvcq7tkww)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Jun 8, 2026 and Oct 3, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-03 | 436ef2e | 29,113 B | A | view · diff |
| v1.0.0 | 2026-10-01 | ecd6fdc | 28,736 B | A | view · diff |
| v1.0.0 | 2026-10-01 | a4478ea | 27,406 B | A | view · diff |
| v1.0.0 | 2026-09-30 | f845a80 | 26,857 B | A | view · diff |
| v1.0.0 | 2026-09-27 | e136d11 | 26,436 B | A | view · diff |
| v1.0.0 | 2026-07-28 | 8e23256 | 25,906 B | A | view · diff |
| v1.0.0 | 2026-07-28 | 1921926 | 25,872 B | A | view · diff |
| v1.0.0 | 2026-06-08 | ed0c7c0 | 25,705 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 (29113 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_aksuusvuvcq7tkww GET https://markdownregistry.com/api/v1/resolve?ref=hdl-tools/digital-chip-design-agents/pipeline-orchestration GET https://markdownregistry.com/api/v1/blob/e3e806be311a42c39aaa19582ab69e8d95fc72d7da1c31aacd73882f047ae1f8
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.