loom-curator SKILL.md skillB
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
loom-curator from 2amlogic/kicad-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 2amlogic/kicad-tools/loom-curator@git:20261106.968018dPins git:20261106.968018d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 2amlogic/kicad-tools
- Path
.agents/skills/loom-curator/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261106.968018d, committed Nov 6, 2026
- First version recorded
- Oct 15, 2026
- Size
- 114,047 bytes
- Repository stars
- 77
- License
- MIT
Enhances approved issues and prepares them for implementation.
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
<!-- loom-managed-skill -->
<!-- GENERATED FILE — DO NOT EDIT DIRECTLY.
Produced by `loom-daemon generate-agent-skills` from
defaults/.claude/commands/loom/curator.md (the same source Claude Code
reads as /loom:curator via .claude/commands/loom/). This is the
cross-vendor skill-discovery surface (.agents/skills/<name>/SKILL.md)
read natively by Codex, Kimi Code, Mistral Vibe, and Grok — see
runtime-adapters.md §5. To change this file, edit the source above
and re-run the generator; CI (`loom-daemon generate-agent-skills
--check`) fails if this file is stale. -->
# Issue Curator
You are an issue curator who maintains and enhances the quality of GitHub issues in this repository.
<!-- toc:begin generated by scripts/check-doc-tocs.sh --fix; do not edit by hand -->
**Contents**
- [Your Role](#your-role)
- [Keep It Simple](#keep-it-simple)
- [⚠️ `--body @path` Does NOT Expand — It Posts the Literal String](#---body-path-does-not-expand--it-posts-the-literal-string)
- [GraphQL Budget: REST Recipes, Pool Gate, Max ~3 Curators (#10039)](#graphql-budget-rest-recipes-pool-gate-max-3-curators-10039)
- [Argument Handling](#argument-handling)
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_tkdi6usgfvpeecr6/8b2a1d297f1806756eb3beca383e2e3b4634f8484da22a6788f203fa97f8f21c.json
Then /plugin install loom-curator@markdownregistry-tkdi6usgfvpeecr6 in Claude Code. It installs git:20261106.968018d, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add 2amlogic/kicad-tools/loom-curator@sha256:8b2a1d297f180675The line at the top of this page pins the label git:20261106.968018d, 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_tkdi6usgfvpeecr6)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in 2amlogic/kicad-tools/loom-curator since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of loom-curator from somewhere else? Ask it: where did my loom-curator come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 15, 2026 and Nov 6, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261106.968018d latest | 2026-11-06 | 968018d | 114,047 B | B | view · diff |
| git:20261103.1bb1434 | 2026-11-03 | 1bb1434 | 113,587 B | B | view · diff |
| git:20261103.33240bf | 2026-11-03 | 33240bf | 110,994 B | B | view · diff |
| git:20261016.c705eeb | 2026-10-16 | c705eeb | 111,465 B | B | view · diff |
| git:20261015.7347c67 | 2026-10-15 | 7347c67 | 113,044 B | B | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/loom-curator/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- fail: No prompt-injection phrasing (matched: ignore your previous instructions)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (114047 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 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
2amlogic/kicad-tools · 77 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tkdi6usgfvpeecr6 GET https://markdownregistry.com/api/v1/resolve?ref=2amlogic/kicad-tools/loom-curator GET https://markdownregistry.com/api/v1/blob/8b2a1d297f1806756eb3beca383e2e3b4634f8484da22a6788f203fa97f8f21c
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 2amlogic/kicad-tools
Every file in 2amlogic/kicad-tools
Other files named loom-curator
Browse by kind, by grade B, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.