sta SKILL.md skillA
sta 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/sta@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/sta/skills/sta/SKILL.md- Versions recorded
- 6
- Latest version
- v1.0.0, committed Oct 2, 2026
- First version recorded
- Apr 14, 2026
- Size
- 12,456 bytes
- Repository stars
- 220
- License
- MIT
Static timing analysis — multi-corner constraint validation, setup and hold analysis, timing exception review, and ECO guidance for closure. Use when running timing analysis on a design, reviewing timing violations, guiding ECO fixes, or performing timing sign-off for tape-out.
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: Static Timing Analysis (STA) ## Invocation When this skill is loaded and a user presents a timing analysis task, **do not execute stages directly**. Immediately spawn the `digital-chip-design-agents:sta-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/sta/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/sta/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/sta@sha256:8b05f0feeb1396f9The 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_vjj7smfq3nblmbol)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Apr 14, 2026 and Oct 2, 2026, about one every 34 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-02 | e243902 | 12,456 B | A | view · diff |
| v1.0.0 | 2026-05-31 | bdc988c | 12,417 B | A | view · diff |
| v1.0.0 | 2026-05-31 | 9bdd652 | 12,412 B | A | view · diff |
| v1.0.0 | 2026-04-25 | 40d51f7 | 10,589 B | A | view · diff |
| v1.0.0 | 2026-04-17 | ac5c224 | 9,043 B | A | view · diff |
| v1.0.0 | 2026-04-14 | fd9fb28 | 8,546 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 (12456 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_vjj7smfq3nblmbol GET https://markdownregistry.com/api/v1/resolve?ref=hdl-tools/digital-chip-design-agents/sta GET https://markdownregistry.com/api/v1/blob/8b05f0feeb1396f9e112057ba897679c18a51ad69be4a7df0b7a9d87e156edb2
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.