evidence-recap SKILL.md skillA
evidence-recap from hisn00w/asu-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hisn00w/asu-skills/evidence-recap@git:20260906.32dfaf7Pins git:20260906.32dfaf7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hisn00w/asu-skills
- Path
skills/evidence-recap/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260906.32dfaf7, committed Sep 6, 2026
- First version recorded
- Sep 3, 2026
- Size
- 4,786 bytes
- Repository stars
- 6,511
- License
- MIT
把 AI 编程对话和项目交付材料复盘为可核验的九段证据链,区分问题、决策、个人动作、交付阶段、效果证据与责任边界。当用户运行 /evidence-recap、$evidence-recap,或明确要求复盘 AI 编程过程、交付记录、落地状态和证据缺口时使用;仅需简历改写、源码导学或模拟面试时不使用。.
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
# /evidence-recap:证据复盘 把人工智能编程对话和项目交付材料还原成可核验的项目证据链,帮助用户 看清问题、决策、个人动作、交付阶段和真实影响,再决定是否需要求职表达 或升维练习。 ## 适用范围 仅处理以下材料: - 人工智能编程对话; - 项目设计、实现、联调、验收或交付记录; - 用于说明项目是否落地、效果如何和个人负责边界的材料。 普通求职经历提升、岗位定位和招聘开场白交给 `/great-resume`;本入口不修改简历, 也不启动其他学习状态。 ## 工作流程 1. 把整段对话中的用户决定、可核验结果和关键助手推理作为材料,不把推测 当成事实。 2. 输出前做隐私检查:项目代号、令牌、密钥、邮箱、客户标识、内部路径和 未公开架构默认泛化或替换。 3. 先判断交付阶段,再整理证据性质。只能在材料明确时使用“生产落地”、 “内部试点”、“原型/技术验证”或“计划/估算”。 4. 按九段证据链输出,保持顺序,不用漂亮措辞掩盖证据缺口。 5. 如果用户之后提交自己的重写尝试,只反馈事实保留、升维动作和越界风险, 不重新代写完整复盘。 ## 九段证据链 按以下顺序输出: 1. **问题背景**:真实场景、原有问题、限制和希望达成的结果。 2. **方案决策**:采用了什么方案、为什么采用、放弃了什么,以及关键取舍。 3. **个人动作**:用户实际完成的设计、实现、联调、验证或推进动作;团队、 平台和人工智能完成的部分单独标注。 4. **交付状态**:明确标注生产落地、内部试点、原型/技术验证或计划/估算。 5. **落地范围**:环境、用户或团队范围、持续时间、覆盖流程和技术范围。 6. **效果证据**:逐项标注实测结果、阶段结果、技术验证或估算收益,并保持 指标的原始范围。 7. **个人边界**:说明用户负责、参与、接入、验证和未负责的部分,不把团队 或平台成果升级为个人主导。 8. **待补证据**:列出缺少的用户、范围、时间、指标、验收或使用记录,不用 推断补成事实。 9. **面试追问**:围绕方案取舍、失败路径、落地范围、效果证据和责任边界, 生成可以由现有材料回答的追问。 ## 表达边界 - 已落地、试点、原型和计划必须显式区分。 - 实测结果、阶段结果、技术验证和估算收益必须显式区分。 - 没有可靠数字时使用可核验的定性表达,不编造比例、用户量、成本或排名。 - 不输出原始密钥、令牌、邮箱、客户标识、内部代号和未公开实现细节。 - 不把演示原型写成业务上线,不把估算收益写成已经实现的结果。 - 机制命名必须能回到当前材料中的真实行为、控制流或边界。 ## 输出附录 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_7pwqgfh3m5d2euxm/0644b5f6db9e92a549568ffeae6fc02787c4992d9c3d0a707bb6bbb8785308d5.json
Then /plugin install evidence-recap@markdownregistry-7pwqgfh3m5d2euxm in Claude Code. It installs git:20260906.32dfaf7, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add hisn00w/asu-skills/evidence-recap@sha256:0644b5f6db9e92a5The line at the top of this page pins the label git:20260906.32dfaf7, 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_7pwqgfh3m5d2euxm)
2 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 hisn00w/asu-skills/evidence-recap 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 evidence-recap from somewhere else? Ask it: where did my evidence-recap 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 2 versions of this file, between Sep 3, 2026 and Sep 6, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260906.32dfaf7 latest | 2026-09-06 | 32dfaf7 | 4,786 B | A | view · diff |
| git:20260903.a706e27 | 2026-09-03 | a706e27 | 4,562 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/evidence-recap/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 (4786 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
hisn00w/asu-skills · 6,511 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7pwqgfh3m5d2euxm GET https://markdownregistry.com/api/v1/resolve?ref=hisn00w/asu-skills/evidence-recap GET https://markdownregistry.com/api/v1/blob/0644b5f6db9e92a549568ffeae6fc02787c4992d9c3d0a707bb6bbb8785308d5
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.