core-build-return SKILL.md skillA
core-build-return from fractera/web4-node-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fractera/web4-node-starter-kit/core-build-return@git:20261111.c35fee6Pins git:20261111.c35fee6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fractera/web4-node-starter-kit
- Path
.claude/skills/core-build-return/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261111.c35fee6, committed Nov 11, 2026
- First version recorded
- Nov 8, 2026
- Size
- 6,516 bytes
- Repository stars
- 68
- License
- MIT
Work process. What happens to you and to the element agents when the core is built — a node update, the «Deploy core» button, npm run serve:rebuild: the build stops every agent, and after its end — good, failed or cut off — the ones that were running come back by themselves, in the same conversations. Load it before you start a core build or a node update, when you wake with the line «Node: the core build has finished», and when the person asks why an agent went off during a build or whether…
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
# The core build, and the agents that come back (node steps 675, 707) **Process: work.** Nothing here is built by you: it is how the node behaves; you plan around it and say it to the person. ## What happens Every agent's `claude` is a child of the core, so a core build with the closed lid stops all of them — you too. Before it stops the core, the build writes who was running and its own process (`data/node/agent-return.json`); after its end it brings each of them back in the same conversation (`claude --continue`) with a line from the node: the element agents first, then you, with the list of who came back, who did not (memory) and which work sessions were stopped. The end is any of three (step 707, the owner 2026-11-09: «с неудачным исходом автоматически поднимать себя так же как и удачным»): a GOOD build — the new build runs; a FAILED build — the previous build is up again and the line names the cause; a build CUT OFF (its process died, the lid stayed shut) — the core's next start sees the dead builder and returns everyone with «the build was cut off». An agent that was asleep stays asleep. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_c7dez2q5ye3lz32i/63f6172f14567a2dc3f420a61ef1ccffe4efd5e62380c33be55176bb2e452c5e.json
Then /plugin install core-build-return@markdownregistry-c7dez2q5ye3lz32i in Claude Code. It installs git:20261111.c35fee6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add fractera/web4-node-starter-kit/core-build-return@sha256:63f6172f14567a2dThe line at the top of this page pins the label git:20261111.c35fee6, 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_c7dez2q5ye3lz32i)
3 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 fractera/web4-node-starter-kit/core-build-return 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 core-build-return from somewhere else? Ask it: where did my core-build-return 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 Nov 8, 2026 and Nov 11, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261111.c35fee6 latest | 2026-11-11 | c35fee6 | 6,516 B | A | view · diff |
| git:20261111.5db642a | 2026-11-11 | 5db642a | 6,138 B | A | view · diff |
| git:20261109.c40d888 | 2026-11-09 | c40d888 | 6,136 B | A | view · diff |
| git:20261108.3e86537 | 2026-11-08 | 3e86537 | 5,111 B | A | view · diff |
| git:20261108.0263ebc | 2026-11-08 | 0263ebc | 4,599 B | A | 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/core-build-return/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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6516 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
fractera/web4-node-starter-kit · 68 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c7dez2q5ye3lz32i GET https://markdownregistry.com/api/v1/resolve?ref=fractera/web4-node-starter-kit/core-build-return GET https://markdownregistry.com/api/v1/blob/63f6172f14567a2dc3f420a61ef1ccffe4efd5e62380c33be55176bb2e452c5e
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.