bottom-volume SKILL.md skillA
bottom-volume from weaxs/stock-analysis-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add weaxs/stock-analysis-plugin/bottom-volume@git:20260916.70e8228Pins git:20260916.70e8228 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- weaxs/stock-analysis-plugin
- Path
skills/bottom-volume/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260916.70e8228, committed Sep 16, 2026
- First version recorded
- May 14, 2026
- Size
- 1,832 bytes
- Repository stars
- 98
- License
- MIT
底部放量分析:判断长期下跌后的异常放量是否构成反转信号。用于低位放量;普通阻力突破用 volume-breakout。.
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
# 底部放量分析 ## 核心理念 长期下跌后的底部区域出现异常放量,可能意味着主力资金开始建仓。底部放量是趋势反转的先兆信号,但需要结合其他指标确认。 ## 执行流程 ### 1. 采集数据 运行数据采集脚本获取 120 根日K线及技术指标: ```bash python3 scripts/gather.py <symbol> ``` ### 2. 底部区域确认 **底部特征**: - 价格距离近 60 日高点下跌 >20% - 股价运行在 MA60 下方较长时间 - RSI 处于低位区间(<40) - 布林带开口收窄,股价在下轨附近 - KDJ 在超卖区域 ### 3. 底部放量类型 | 类型 | 量价特征 | 信号强度 | |------|----------|----------| | 底部温和放量 | 量比 1.5-2.5,小阳线 | 中等,可能是试探性建仓 | | 底部巨量阳线 | 量比 >3,大阳线 | 强,主力大举建仓 | | 底部放量十字星 | 量比 >2,十字星 | 变盘信号,需观察后续 | | 底部放量长下影 | 量比 >2,长下影线 | 强支撑,有资金承接 | ### 4. 确认信号 单日放量不够,还需要: - 后续几日成交量维持在均量之上 - 价格站上 MA5 并上攻 MA10 - MACD 在底部金叉 - 不出现放量大阴线(那是出货不是建仓) ### 5. 注意事项 - 底部放量后可能还有二次探底 - 区分"放量见底"和"放量破位"(放量跌破重要支撑是加速下跌) - 建议分批建仓而非一次满仓 ## 输出要求 1. 是否处于底部区域(下跌幅度、持续时间) 2. 是否出现底部放量信号 3. 放量类型及信号强度 4. 后续确认情况 5. 建仓建议(分批价位、止损位)
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yzvqdxaqf3cpv5bm/83ebd3c9f561c3c4848d0ec0036b2ff6efe8b93e455b78722e6b928de9aa2d7f.json
Then /plugin install bottom-volume@markdownregistry-yzvqdxaqf3cpv5bm in Claude Code. It installs git:20260916.70e8228, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add weaxs/stock-analysis-plugin/bottom-volume@sha256:83ebd3c9f561c3c4The line at the top of this page pins the label git:20260916.70e8228, 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_yzvqdxaqf3cpv5bm)
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 weaxs/stock-analysis-plugin/bottom-volume 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 bottom-volume from somewhere else? Ask it: where did my bottom-volume 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 May 14, 2026 and Sep 16, 2026, about one every 42 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.70e8228 latest | 2026-09-16 | 70e8228 | 1,832 B | A | view · diff |
| git:20260916.a1ca926 | 2026-09-16 | a1ca926 | 2,011 B | A | view · diff |
| git:20260521.076544a | 2026-05-21 | 076544a | 1,883 B | A | view · diff |
| git:20260514.9bdbe4d | 2026-05-14 | 9bdbe4d | 1,764 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/bottom-volume/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 (1832 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
weaxs/stock-analysis-plugin · 98 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yzvqdxaqf3cpv5bm GET https://markdownregistry.com/api/v1/resolve?ref=weaxs/stock-analysis-plugin/bottom-volume GET https://markdownregistry.com/api/v1/blob/83ebd3c9f561c3c4848d0ec0036b2ff6efe8b93e455b78722e6b928de9aa2d7f
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.