rigc SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
rigc from rig-c/core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rig-c/core/rigc@git:20261014.844d2a1Pins git:20261014.844d2a1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rig-c/core
- Path
skills/rigc/SKILL.md- Versions recorded
- 9
- Latest version
- git:20261014.844d2a1, committed Oct 14, 2026
- First version recorded
- Oct 5, 2026
- Size
- 10,447 bytes
- Repository stars
- 15
- License
- a license file GitHub does not identify
Author, build and validate Spine 4.3 skeleton data (skeleton.json plus its .atlas) from loose part PNGs with rigc, the rig compiler that verifies its own output with named assertions before writing it. Use for any request to make a Spine rig or Spine animation from PNG parts, or where the source is a Live2D, Unity or video model whose pictures you can render, to run or read rigc build, validate, render, preview, check or vote, or to write or fix a *.rig.json or *.motion.json spec; it says…
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
# rigc — a rig compiler for agents rigc compiles a rig spec and a motion spec into Spine 4.3 skeleton data and an atlas, runs its named assertions — rigc's own validator in the published package, held to a `@esotericsoftware/spine-core` round trip's verdicts in its CI, all but the parse itself — and writes **only if every one is green**. You cannot see the rig you are authoring. The validator's messages and the shipped guides are the whole interface, and this skill only says which of them to open. 📖 **A failure line ends with the command that prints its row of the guide** — ` (see rigc guide <RULE>)`. Run that command first, before reading anything else: it prints that rule's row of the shipped guide and nothing else. `rigc guide §<n>` (and `§<n>.<m>`, `§<n>.<m>.<k>`) prints the section's heading, own prose and subsection index from `docs/AUTHORING.md`; add `--all` to include subsection bodies. A leaf prints its full text either way. Sizes describe full ledger spans; `--all` with a rule name is refused, exit 2. A compile error points at its stable `CE_` code row. `rigc guide §5.1.<k>` prints a numbered compile-error group of …
Read the whole file at its exact version.
How to install
mdr add rig-c/core/rigc@sha256:2618be81ee035e74The line at the top of this page pins the label git:20261014.844d2a1, 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_ubz4h3yqodlm74pw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 9 versions of this file, between Oct 5, 2026 and Oct 14, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.844d2a1 latest | 2026-10-14 | 844d2a1 | 10,447 B | A | view · diff |
| git:20261014.91a1342 | 2026-10-14 | 91a1342 | 10,168 B | A | view · diff |
| git:20261014.cef502f | 2026-10-14 | cef502f | 10,005 B | A | view · diff |
| git:20261013.907e820 | 2026-10-13 | 907e820 | 9,738 B | A | view · diff |
| git:20261011.9b18801 | 2026-10-11 | 9b18801 | 9,368 B | A | view · diff |
| git:20261011.f2bd939 | 2026-10-11 | f2bd939 | 9,006 B | A | view · diff |
| git:20261008.c5f9972 | 2026-10-08 | c5f9972 | 9,030 B | A | view · diff |
| git:20261005.223f285 | 2026-10-05 | 223f285 | 9,065 B | A | view · diff |
| git:20261005.554bb90 | 2026-10-05 | 554bb90 | 8,820 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 (10447 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
rig-c/core · 15 stars · license a license file GitHub does not identify · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ubz4h3yqodlm74pw GET https://markdownregistry.com/api/v1/resolve?ref=rig-c/core/rigc GET https://markdownregistry.com/api/v1/blob/2618be81ee035e74e1a18f35e65fb34951d850265cb7bf6ca040b73adc559e38
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.