mathrsi-assemble SKILL.md skillA
mathrsi-assemble from lisresearchgroup/math-rsi is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lisresearchgroup/math-rsi/mathrsi-assemble@git:20261114.82b79a0Pins git:20261114.82b79a0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lisresearchgroup/math-rsi
- Path
base/skills/mathrsi-assemble/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261114.82b79a0, committed Nov 14, 2026
- First version recorded
- Nov 1, 2026
- Size
- 17,514 bytes
- Repository stars
- 46
- License
- MIT
将原题、已证明引理、准确文献进口与计算证据装配成完整数学证明,调用 ARIS proof-writer,检查实际输入与条件引理的连接。用于已有足够结果后形成现用正文;正式审计的新稿可直接写 PROOF.tex,完成或发现缺口后返回原调用方。.
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
# MathRSI 证明装配 本技能把已经取得的数学结果写成从原题输入走到结论的完整证明。它是“装配验证”工作流中的装配步骤,也可由用户单独调用。输入可以是一组分散引理、带证书的有限归约,或已有较完整的稿件;输出是一份可供严格验证的完整正文,以及准确指出尚未接通之处的返回信息。 装配中允许展开已成立论证、省去重复符号、补写直接推论和真实调用,但不能为得到漂亮成稿改变原命题、偷偷把候选当进口、删去困难分支。发现需要新数学时,将那个具体义务交回 [mathrsi-prove](../mathrsi-prove/SKILL.md)。装配可以交回一份清楚的部分稿,不能用正文完整的外观代替证明完整。 **组合调用只返回原caller。** 由verify、prove、handoff或主流程调用时,完成指定scope后交回正文、状态和下一阶段建议,不自行再启动verify/prove/handoff;下一阶段由原调用方或唯一主dispatcher选择。本文“交回prove”等措辞表示需要的后继,不授予第二个调度者。内部proof-writer与必要推导照常实际执行。独立调用只完成本次授权的装配;用户明确要求持续研究时,由本agent接主调度一次再选后继,避免父子各启动同一任务。 ## 一次装配的实际接棒 本次工作从“哪些结果已经可用”开始,落在“它们怎样共同推出这条原命题”。先读取源并还原调用链,再实际交给writer组织正文,最后读取成稿核前提供给与完整分流;返回的是这份正文及其连接状态。下面的入口决定第一动作,无须每次从空白起草。 | 当前输入 | 本次实际动作 | 交给调用方的结果 | |---|---|---| | 仅要求形式目标,或完整Lean出口已在手 | 读原目标和导出入口,确认不需另组织自然语言正文;返回caller建议verify直接Lean分支 | 原声明、实际模块/导出与已知连接或缺口;不为经过assemble先造TeX或调用writer | | 分散的已证引理、文献进口与证书 | 读取实际证明和证据,把它们按原输入到结论排序,再调用proof-writer写现用正文 | 完整候选正文,或准确指出哪一步仍无上游供给的部分稿 | | 已有完整现稿 | 读主命题和实际引用,确认关键连接;只修真正遗漏的说明 | 沿用的正文入口、改动和是否可交验证;不声称重复执行writer | | 局部定理及caller | 仅组织该局部命题、必要定义、依赖和实际应用 | 可被原prove/verify消费的局部正文与条件,不升级成原题完成 | | handoff要求重排已核章节 | 给writer现稿、允许的编辑范围和已有verification | 可读修订与实质差异;新数学断言明确交回caller建议验证 | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rnhxfiyzs3vygl6w/561521b30e4a26eee5ddbbc8d6e050b1024cb390b86b8c5bf2af5513e5a49f7f.json
Then /plugin install mathrsi-assemble@markdownregistry-rnhxfiyzs3vygl6w in Claude Code. It installs git:20261114.82b79a0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add lisresearchgroup/math-rsi/mathrsi-assemble@sha256:561521b30e4a26eeThe line at the top of this page pins the label git:20261114.82b79a0, 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_rnhxfiyzs3vygl6w)
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 lisresearchgroup/math-rsi/mathrsi-assemble 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 mathrsi-assemble from somewhere else? Ask it: where did my mathrsi-assemble 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 1, 2026 and Nov 14, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.82b79a0 latest | 2026-11-14 | 82b79a0 | 17,514 B | A | view · diff |
| git:20261108.cc10760 | 2026-11-08 | cc10760 | 16,992 B | A | view · diff |
| git:20261104.774d09d | 2026-11-04 | 774d09d | 15,758 B | A | view · diff |
| git:20261102.086d0c6 | 2026-11-02 | 086d0c6 | 15,327 B | A | view · diff |
| git:20261101.a0c4ad3 | 2026-11-01 | a0c4ad3 | 14,395 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/mathrsi-assemble/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 (17514 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
lisresearchgroup/math-rsi · 46 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rnhxfiyzs3vygl6w GET https://markdownregistry.com/api/v1/resolve?ref=lisresearchgroup/math-rsi/mathrsi-assemble GET https://markdownregistry.com/api/v1/blob/561521b30e4a26eee5ddbbc8d6e050b1024cb390b86b8c5bf2af5513e5a49f7f
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.