loom-builder-complexity 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.

loom-builder-complexity from 2amlogic/kicad-tools is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add 2amlogic/kicad-tools/loom-builder-complexity@git:20261014.394e76a

Pins git:20261014.394e76a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
2amlogic/kicad-tools
Path
.agents/skills/loom-builder-complexity/SKILL.md
Versions recorded
5
Latest version
git:20261014.394e76a, committed Oct 14, 2026
First version recorded
Oct 4, 2026
Size
22,688 bytes
Repository stars
77
License
MIT

This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the core builder workflow, see `builder.md`.

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/builder-complexity.md (the same source Claude Code
     reads as /loom:builder-complexity 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. -->

# Builder: Complexity Assessment and Issue Decomposition

This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the core builder workflow, see `builder.md`.

<!-- toc:begin generated by scripts/check-doc-tocs.sh --fix; do not edit by hand -->
**Contents**

- [⚠️ `--body @path` Does NOT Expand — It Posts the Literal String](#---body-path-does-not-expand--it-posts-the-literal-string)
- [Never Abandon Work](#never-abandon-work)
- [Auditing Before Decomposition](#auditing-before-decomposition)
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mejzdtt5rjk5upgo/4c0b0da4e1da507ea5d54859927a043c1bbf8ce887753f507ea2b142424ae161.json

Then /plugin install loom-builder-complexity@markdownregistry-mejzdtt5rjk5upgo in Claude Code. It installs git:20261014.394e76a, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add 2amlogic/kicad-tools/loom-builder-complexity@sha256:4c0b0da4e1da507e

The line at the top of this page pins the label git:20261014.394e76a, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_mejzdtt5rjk5upgo.svg)](https://markdownregistry.com/a/art_mejzdtt5rjk5upgo)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in 2amlogic/kicad-tools/loom-builder-complexity 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-builder-complexity from somewhere else? Ask it: where did my loom-builder-complexity 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 4, 2026 and Oct 14, 2026, about one every 3 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261014.394e76a latest2026-10-14 394e76a 22,688 BA view · diff
git:20261012.4df1f032026-10-12 4df1f03 23,293 BA view · diff
git:20261011.dcb2b512026-10-11 dcb2b51 23,411 BA view · diff
git:20261006.f33ce3a2026-10-06 f33ce3a 23,439 BA view · diff
git:20261004.2c3dee02026-10-04 2c3dee0 23,197 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (22688 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

GitHub

2amlogic/kicad-tools · 77 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_mejzdtt5rjk5upgo
GET https://markdownregistry.com/api/v1/resolve?ref=2amlogic/kicad-tools/loom-builder-complexity
GET https://markdownregistry.com/api/v1/blob/4c0b0da4e1da507ea5d54859927a043c1bbf8ce887753f507ea2b142424ae161

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

loom-architect SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-architect/SKILL.md · Identifies improvement opportunities and creates proposals
git:20261014.c9e8426 · audit A · 77 stars
loom-auditor SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-auditor/SKILL.md · Verifies claims made by other agents against runtime reality by building and testing software
git:20261014.c9e8426 · audit A · 77 stars
loom-builder-pr SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-builder-pr/SKILL.md · This document covers PR creation, test output handling, and quality requirements for the Builder role. For the core…
git:20261026.79cebff · audit A · 77 stars
loom-builder-worktree SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-builder-worktree/SKILL.md · This document covers git worktree management for the Builder role. For the core builder workflow, see `builder.md`.
git:20261014.c9e8426 · audit A · 77 stars
loom-builder SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-builder/SKILL.md · Implements issues labeled loom:issue (human-approved work)
git:20261117.d2f58d4 · audit B · 77 stars
loom-cargo-target-isolation SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-cargo-target-isolation/SKILL.md · **Load when**: you are about to run (or just ran) a local `cargo build`/`cargo test`/`cargo run` whose result will…
git:20261012.bf4491e · audit A · 77 stars
loom-champion SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-champion/SKILL.md · Human avatar for final decisions - promotes quality issues to approved status AND auto-merges Judge-approved PRs that…
git:20261101.cb06282 · audit A · 77 stars
loom-ci-refusals-reference SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-ci-refusals-reference/SKILL.md · **Load when**: `loom-daemon forge wait-checks` printed `LOOM-CHECKS-ERROR` naming an HTTP `401`/`403`/`429`, it left a…
git:20261007.6b901b8 · audit A · 77 stars
loom-comment-body-literal-path SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-comment-body-literal-path/SKILL.md · Single canonical copy; role prompts' short pointers refer here.
git:20261010.688914e · audit A · 77 stars
loom-curator-estimate SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-curator-estimate/SKILL.md · For every issue you actually curate or re-curate, write exactly one concrete, standalone comment in the current issue…
git:20261016.bd59834 · audit A · 77 stars
loom-curator-rate-budget SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-curator-rate-budget/SKILL.md · Why `curator.md`'s per-issue recipes are REST, and what is still unmeasured.
git:20261005.f192e8f · audit A · 77 stars
loom-curator SKILL.md skill
2amlogic/kicad-tools · .agents/skills/loom-curator/SKILL.md · Enhances approved issues and prepares them for implementation
git:20261106.968018d · audit B · 77 stars

Every file in 2amlogic/kicad-tools

Other files named loom-builder-complexity

loom-builder-complexity SKILL.md skill
rjwalters/kicad-tools · .agents/skills/loom-builder-complexity/SKILL.md · This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the…
git:20261014.394e76a · audit A · 77 stars

Browse by kind, by grade A, or by owner.

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.