judging-changes SKILL.md skillA
judging-changes from heptameta/heptabase-explainer-studio is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add heptameta/heptabase-explainer-studio/judging-changes@git:20261014.bb251f8Pins git:20261014.bb251f8 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- heptameta/heptabase-explainer-studio
- Path
.claude/skills/judging-changes/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261014.bb251f8, committed Oct 14, 2026
- Size
- 8,253 bytes
- Repository stars
- 3
- License
- Apache-2.0
How to decide whether and where to change Explainer Studio's teaching behaviour, how much evidence a change needs, and what its pull request must say. Use before changing anything under explainer_studio/guide/references/ or explainer_studio/question_types.py, when turning viewer feedback into a change, and when reviewing such a change.
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
# Judging a change A change to how videos are made is judged on three things at once, and the pull request says how it trades them: 1. **Quality:** what gets better, how it was checked (which sources, how many episodes, what the viewers said), and what is still not solved. 2. **Cost and time:** tokens and waiting are part of the user's experience. Say how much more or less it costs per series (knowing the viewer, deep reading, planning: these grow with the sources) and per episode (these grow with the video's length), in tokens, rough dollars and minutes. 3. **Rule complexity:** every rule can overfit one source and can hold back the next, stronger model. Say which rules were added or removed and of which kind (below), and whether any rule exists for a single source. None of the three may be bought without limit at the expense of the other two. ## Where a problem belongs Find the cause first, then the layer. Each layer has its own place to change and its own reach: | Layer | Example symptom | Change | Reaches | |---|---|---|---| …
Read the whole file at its exact version.
How to install
mdr add heptameta/heptabase-explainer-studio/judging-changes@sha256:01f9faf5a5eede1dThe line at the top of this page pins the label git:20261014.bb251f8, 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_ikfonyneao3uvvsy)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 14, 2026.
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 (8253 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
heptameta/heptabase-explainer-studio · 3 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ikfonyneao3uvvsy GET https://markdownregistry.com/api/v1/resolve?ref=heptameta/heptabase-explainer-studio/judging-changes GET https://markdownregistry.com/api/v1/blob/01f9faf5a5eede1d28fa0ea4f74df222311e4054c54c45c0adae6955bec8c43b
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.