stock_analyzer 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.
stock_analyzer 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/stock_analyzer@git:20261121.a27923dPins git:20261121.a27923d 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
SKILL.md- Versions recorded
- 4
- Latest version
- git:20261121.a27923d, committed Nov 21, 2026
- First version recorded
- Mar 3, 2026
- Size
- 9,127 bytes
- Repository stars
- 73,646
- 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
# 股票分析器 本技能驱动**已部署并配置好的** [daily_stock_analysis (DSA)](https://github.com/ZhuLinsen/daily_stock_analysis) 检出或正在运行的 DSA 服务;它本身**不包含** `src/` 运行时。市场安装的插件缓存通常只有 `./plugin`,在普通项目目录直接 `import src...` 会得到 `ModuleNotFoundError`。 ## 运行前提(调用前必做) 1. **确认存在可用的 DSA 环境**(完整仓库检出且已按指南配置 `.env`,或用户已有可调用的 DSA API 服务)。 2. **定位检出路径**(任选其一): - 询问用户本机 DSA 仓库路径; - 读取环境变量 `DSA_REPO_ROOT`(指向仓库根目录,含 `src/` 与 `.env`); - 若当前工作目录已是 DSA 根目录,可直接使用。 3. **再执行示例代码**:必须先 `os.chdir(repo_root)`(或等价地在该根目录启动进程),再将该根目录加入 `sys.path` / `PYTHONPATH`。仅改 `sys.path` 不够:默认相对 `DATABASE_PATH` 与大盘复盘锁按**进程工作目录**解析,不 `chdir` 会导致插件与 Web 锁住不同文件、写入不同 SQLite。 4. **对话内大盘复盘(不推送)**:需要检出已支持 `perform_market_review(..., send_notification=...)`(本仓库较新提交;例如 v3.35.0 尚不支持)。若不支持,先更新检出,**不要**回退为无该参数的调用(旧签名默认会推送)。 5. **若无法定位或未部署**:停止分析,向用户说明本技能只驱动现有 DSA 安装,并指向部署指南: - 中文:[完整配置与部署指南](https://github.com/ZhuLinsen/daily_stock_analysis/blob/main/docs/full-guide.md) - English: [Full Guide](https://github.com/ZhuLinsen/daily_stock_analysis/blob/main/docs/full-guide_EN.md) …
Read the whole file at its exact version.
How to install
mdr add zhulinsen/daily_stock_analysis/stock_analyzer@sha256:b2bb85f663a96c74The line at the top of this page pins the label git:20261121.a27923d, 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_v5rouftswff3himi)
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 zhulinsen/daily_stock_analysis/stock_analyzer 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 stock_analyzer from somewhere else? Ask it: where did my stock_analyzer 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 4 versions of this file, between Mar 3, 2026 and Nov 21, 2026, about one every 88 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261121.a27923d latest | 2026-11-21 | a27923d | 9,127 B | A | view · diff |
| git:20260819.5d14873 | 2026-08-19 | 5d14873 | 4,411 B | A | view · diff |
| git:20260510.595908c | 2026-05-10 | 595908c | 3,781 B | A | view · diff |
| git:20260303.c87c8ff | 2026-03-03 | c87c8ff | 3,696 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/stock_analyzer/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 (9127 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_v5rouftswff3himi GET https://markdownregistry.com/api/v1/resolve?ref=zhulinsen/daily_stock_analysis/stock_analyzer GET https://markdownregistry.com/api/v1/blob/b2bb85f663a96c7451503e6c24ea84ef60df243f93861dd40fd7b7b08e6ea3ee
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