analyze-issue SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
analyze-issue from zhulinsen/daily_stock_analysis is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zhulinsen/daily_stock_analysis/analyze-issue@git:20261121.7cfcf94Pins git:20261121.7cfcf94 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zhulinsen/daily_stock_analysis
- Path
.claude/skills/analyze-issue/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261121.7cfcf94, committed Nov 21, 2026
- First version recorded
- Mar 17, 2026
- Size
- 2,748 bytes
- Repository stars
- 73,646
- License
- MIT
分析 daily_stock_analysis 仓库的 GitHub Issue,核实版本基线、真实性、根因定位、影响面与仓库责任边界,给出优先级和处置建议。用户给出 Issue 号或链接并要求分析时使用。.
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
# Analyze Issue 规则真源:仓库根目录 [`AGENTS.md`](../../../AGENTS.md)(基线同步规则见 §7)。 - 输出语言:简洁中文。 - 产物策略:**默认直接在对话中输出**;仅当用户明确要求存档时,写入 `.reviews/issues/issue-<number>.md`。 ## Step 1: 同步基线并拉取 Issue 按 `AGENTS.md` §7 同步远端基线并记录本地 HEAD 与远端基线,然后执行: ```bash gh issue view <number> --repo ZhuLinsen/daily_stock_analysis gh issue view <number> --repo ZhuLinsen/daily_stock_analysis --comments ``` 如为 bug,核对是否提供了版本/commit hash、运行环境、复现步骤与报错日志。 ## Step 2: 代码证据核查 - 阅读相关源码、配置、测试、工作流与文档,不凭 issue 描述直接下结论。 - 回答 4 个核心问题:版本是否明确、问题是否真实可验证、是否属于仓库责任边界、是否值得立即处理。 - 区分:真实代码 bug / 配置或环境问题 / 使用方式问题 / 外部数据源或三方依赖问题 / 已在主干修复。 - 明确排查受影响模块与运行路径(本地 CLI / Docker / GitHub Actions / API / Web / Desktop)。 ## Step 3: 输出格式 ```markdown # Issue #<number> Analysis ## 1. 结论摘要 - 版本基线:最新 / 非最新 / 未提供 - 结论:成立 / 部分成立 / 不成立 - 分类:bug / feature / docs / question / external - 优先级:P0 / P1 / P2 / P3 | 难度:easy / medium / hard - 建议动作:立即修复 / 排期修复 / 文档澄清 / 关闭 ## 2. 证据与根因 - 代码同步基线: - 关键 Issue 信息: - 源码 / 配置 / 工作流证据(`path:line`): - 根因或主要判断依据: ## 3. 影响面 - 受影响模块与既有运行时文件: - 受影响运行路径(本地 / Docker / GitHub Actions / API / Web / Desktop): - 是否涉及配置/环境变量、UI/Web、报告结构、通知或持久化变更: ## 4. 处置建议 - 修复方案 / 澄清要点 / 关闭理由: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3yvqvlwefj5dk4ee/bee4172915f1b9c56f5f296352fc78bdd72d17278771a08a864b6ff297a47a38.json
Then /plugin install analyze-issue@markdownregistry-3yvqvlwefj5dk4ee in Claude Code. It installs git:20261121.7cfcf94, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add zhulinsen/daily_stock_analysis/analyze-issue@sha256:bee4172915f1b9c5The line at the top of this page pins the label git:20261121.7cfcf94, 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_3yvqvlwefj5dk4ee)
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 zhulinsen/daily_stock_analysis/analyze-issue 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 analyze-issue from somewhere else? Ask it: where did my analyze-issue 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 Mar 17, 2026 and Nov 21, 2026, about one every 62 days. Its first recorded version is graded C and its latest A.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261121.7cfcf94 latest | 2026-11-21 | 7cfcf94 | 2,748 B | A | view · diff |
| git:20261119.92f0209 | 2026-11-19 | 92f0209 | 1,110 B | A | view · diff |
| git:20260621.f61c536 | 2026-06-21 | f61c536 | 4,110 B | C | view · diff |
| git:20260515.f553fe1 | 2026-05-15 | f553fe1 | 3,176 B | C | view · diff |
| git:20260317.b06c098 | 2026-03-17 | b06c098 | 2,887 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/analyze-issue/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 (2748 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
zhulinsen/daily_stock_analysis · 73,646 stars · license MIT · pushed 2026-11-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3yvqvlwefj5dk4ee GET https://markdownregistry.com/api/v1/resolve?ref=zhulinsen/daily_stock_analysis/analyze-issue GET https://markdownregistry.com/api/v1/blob/bee4172915f1b9c56f5f296352fc78bdd72d17278771a08a864b6ff297a47a38
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.
More from zhulinsen/daily_stock_analysis
Every file in zhulinsen/daily_stock_analysis