zh-CN SKILL.md skillC
zh-CN from kimyx0207/kim_service is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kimyx0207/kim_service/zh-CN@git:20261114.fa2ad6cPins git:20261114.fa2ad6c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 14 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kimyx0207/kim_service
- Path
skills/kim-decision/docs/zh-CN/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261114.fa2ad6c, committed Nov 14, 2026
- First version recorded
- Jul 15, 2026
- Size
- 9,342 bytes
- Repository stars
- 193
- License
- MIT
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
# 老金 Skill 中文参考 这个文件给人看。 这是中文精简参考版。完整运行入口是 `.agents/skills/Kim/SKILL.md`(Codex)和 `.claude/skills/Kim/SKILL.md`(Claude Code)。 ## 核心规则 设定层保持抽象。 答复层允许具体。 回答用户时,可以使用真实姓名、公司、产品、案例、来源、日期、数据、命令、文件路径。前提是能增强可信度,并且不能编。 不要把具体人物写成内部角色模型。 不要写“像某某一样思考”。 把有价值的思维方式转成抽象模型。 ## 核心框架 ```text 意图 -> 主体 -> 路径 -> 约束 -> 证据 -> 最小验证 -> 模型 -> 硬门 -> 输出 ``` ## 核心问题门 展开框架前,先在后台钉住一句话:用户真正要解决的是哪个决策、缺陷、路径、offer 或交付物。 如果某个模型、标题、解释或流程不能提升这个核心问题的判断质量、证据质量、执行清晰度或复盘质量,就压缩或删除。KIM 可以借鉴 Meta_Kim 的治理纪律,但可见输出必须仍然是锋利的判断、验证动作、交付物或下一步。 ## 路径分级 - 快路径:单点问题、本地证据、低风险。输出结论、杠杆点、下一步和通过标准。 - 标准路径:产品、商业、内容、策略类决策,有真实不确定性。输出问题、取证、判断、24 小时动作和复盘尺。 - 监管路径:高风险、当前外部事实、法律/金融/安全、多步执行或公开长期决策。输出证据等级、研究尝试、假设、通过/停止门和硬缺口。 流程级别随风险升级,不因 skill 被触发就默认走重流程。 ## 澄清与联网边界 只问最小阻塞问题。缺信息但能合理假设时,带着假设继续;本地能查时,先查再问;多个解释会导向不同输出时,列出 2-3 个解释并推荐默认项。 外部事实会变时必须验证:版本、API、文档、规则、价格、时间表、安全公告、市场状态、第三方工具行为、需要引用或支撑公开判断的来源。优先官方或一手来源。用户明确要求“最新、搜索、验证、引用来源”时,先查再判断。 ## 参考加载 一次只加载当前任务需要的文件。 - `references/execution.md`:当用户要方案、计划、落地、执行、推进、MVP、交付、增长、变现或验证时加载;用于把判断变成有执行者、输入、产出、测试假设、通过标准、停止标准和硬缺口的动作链。 - `references/distillation.md`:当用户要求提炼高手方法、学习某套方法或“像某人一样判断”时加载;用于把样本蒸馏成抽象判断结构,禁止把具体人物当成内部角色。 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gzganauam5sedfxh/0a39fb4ba128dd9c16d5c1c82566fcd883198758d94337918ef8fb05c99df868.json
Then /plugin install zh-cn@markdownregistry-gzganauam5sedfxh in Claude Code. It installs git:20261114.fa2ad6c, the one graded C here, pinned to the commit it was graded at, and leaves it there.
mdr add kimyx0207/kim_service/zh-CN@sha256:0a39fb4ba128dd9cThe line at the top of this page pins the label git:20261114.fa2ad6c, 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_gzganauam5sedfxh)
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 kimyx0207/kim_service/zh-CN 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 zh-CN from somewhere else? Ask it: where did my zh-CN 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 Jul 15, 2026 and Nov 14, 2026, about one every 122 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261114.fa2ad6c latest | 2026-11-14 | fa2ad6c | 9,342 B | C | view · diff |
| git:20260715.cad3517 | 2026-07-15 | cad3517 | 8,105 B | C | 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/zh-CN/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
- fail: Frontmatter block present
- fail: Frontmatter declares a name
- fail: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9342 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
kimyx0207/kim_service · 193 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gzganauam5sedfxh GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/kim_service/zh-CN GET https://markdownregistry.com/api/v1/blob/0a39fb4ba128dd9c16d5c1c82566fcd883198758d94337918ef8fb05c99df868
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.