sync SKILL.md skillB
sync from qwerfunch/cladding is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qwerfunch/cladding/sync@git:20260905.d56eea5Pins git:20260905.d56eea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qwerfunch/cladding
- Path
skills/sync/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260905.d56eea5, committed Sep 5, 2026
- First version recorded
- Jun 2, 2026
- Size
- 1,953 bytes
- Repository stars
- 16
- License
- MIT
Validate the active spec.yaml against the Ironclad schema and refresh the inventory. Rarely needed manually — clad_create_feature already auto-syncs the inventory and clad check / clad done self-validate the spec, so do NOT run it as a reflexive pre-flight before those. Use it only after you have directly hand-edited a shard file (spec/features/*.yaml or spec.yaml). Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in…
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
# Cladding sync Run `clad sync` from the project root. The command: - Loads `spec.yaml` (or its sharded form under `spec/features/*.yaml`). - Validates against `src/spec/schema.json` (JSONSchema). - Reports the feature count and any validation failures. - Exits non-zero when the spec is invalid so CI can gate on it. Spec must be valid before `clad check` or any stage runner produces meaningful output. If `sync` fails, fix the reported issues first. ``` clad sync ``` ## When you actually need it (don't reflex-sync) You rarely need to run this MANUALLY — and a reflexive "just-in-case" sync after every operation is wasted work (in an A/B measurement, 28 of 30 manual `clad sync` calls found nothing to fix). The inventory + validation are already maintained for you: - **`clad_create_feature` auto-syncs the inventory** after each feature it writes (and rejects a malformed AC at creation), so you don't need to sync after creating features. - **`clad check` / `clad done` validate the spec themselves** (drift stage), so you don't need to pre-sync before them — a real drift surfaces in that gate anyway. …
Read the whole file at its exact version.
How to install
mdr add qwerfunch/cladding/sync@sha256:33222aea324fda74The line at the top of this page pins the label git:20260905.d56eea5, 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_4hxrjwv3hbz5ik2u)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 2, 2026 and Sep 5, 2026, about one every 24 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.d56eea5 latest | 2026-09-05 | d56eea5 | 1,953 B | B | view · diff |
| git:20260714.abe37cd | 2026-07-14 | abe37cd | 1,966 B | B | view · diff |
| git:20260613.28fc6d8 | 2026-06-13 | 28fc6d8 | 1,815 B | B | view · diff |
| git:20260603.8448281 | 2026-06-03 | 8448281 | 1,817 B | B | view · diff |
| git:20260602.49d1c5d | 2026-06-02 | 49d1c5d | 1,700 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1953 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
qwerfunch/cladding · 16 stars · license MIT · pushed 2026-09-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4hxrjwv3hbz5ik2u GET https://markdownregistry.com/api/v1/resolve?ref=qwerfunch/cladding/sync GET https://markdownregistry.com/api/v1/blob/33222aea324fda74ae7e45421404efe08b8370b5920269bf001b03eed63669b5
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 qwerfunch/cladding
Every file in qwerfunch/cladding