strategy SKILL.md skillA
strategy from chaingpt-org/chaingpt-claude-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chaingpt-org/chaingpt-claude-skill/strategy@git:20261101.75a24faPins git:20261101.75a24fa in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chaingpt-org/chaingpt-claude-skill
- Path
skills/strategy/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261101.75a24fa, committed Nov 1, 2026
- First version recorded
- May 19, 2026
- Size
- 4,070 bytes
- Repository stars
- 7
- License
- MIT
Build trading strategy plans via the ChainGPT plugin: DCA (dollar-cost-averaging), grid trading, Hyperliquid funding-rate arbitrage, copy-trading from a target wallet, and DCA backtesting against historical price data. The strategy tools COMPUTE THE PLAN; Claude executes the steps one by one via Tier 1-3 tools (research, risk, dex, defi, hl, pm) — every action still gated by the mainnet acknowledgement refusal. Triggers: DCA, dollar cost average, grid trade, funding arb, copy trade, copy…
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
# ChainGPT Strategy Skill You build trading strategy *plans* — not execute them autonomously. Every plan output by these tools lists the exact Tier 1-3 tools Claude should call to execute the steps, in order. Each executing step still goes through the existing mainnet-ack gates. This keeps the agent layer reviewable and refusal-safe. ## Tools | Tool | What | Output | |---|---|---| | `chaingpt_strategy_dca_plan` | DCA schedule for one token | List of buys (timestamp + USD size) + the exact MCP calls to execute each | | `chaingpt_strategy_grid_plan` | Grid-trading ladder | Buy + sell limit levels with sizes; HL / PM / DEX-flavored execution | | `chaingpt_strategy_funding_arb_plan` | HL funding-rate carry suggester | Side / leverage / hourly+daily carry estimate + execution sequence | | `chaingpt_strategy_copy_plan` | Mirror a target wallet's swaps | Step-by-step: fetch txs → decode → risk-check each outToken → scale + mirror | | `chaingpt_backtest_dca` | Replay DCA against CoinGecko history | DCA P&L vs buy-and-hold baseline | ## Execution discipline When the user asks "build me a DCA into ETH for $1000 over a week": …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ggfmyg27i5kkvoup/fa20f200cc87e5958e7e05bb3922157283f103403ea71b9ba66595a2916b4fb9.json
Then /plugin install strategy@markdownregistry-ggfmyg27i5kkvoup in Claude Code. It installs git:20261101.75a24fa, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add chaingpt-org/chaingpt-claude-skill/strategy@sha256:fa20f200cc87e595The line at the top of this page pins the label git:20261101.75a24fa, 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_ggfmyg27i5kkvoup)
1 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 chaingpt-org/chaingpt-claude-skill/strategy 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 strategy from somewhere else? Ask it: where did my strategy 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 19, 2026 and Nov 1, 2026, about one every 55 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261101.75a24fa latest | 2026-11-01 | 75a24fa | 4,070 B | A | view · diff |
| git:20261030.2fdba0c | 2026-10-30 | 2fdba0c | 4,030 B | A | view · diff |
| git:20260610.61657e2 | 2026-06-10 | 61657e2 | 4,132 B | A | view · diff |
| git:20260519.ca5b8d0 | 2026-05-19 | ca5b8d0 | 4,141 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/strategy/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 (4070 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
chaingpt-org/chaingpt-claude-skill · 7 stars · license MIT · pushed 2026-11-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ggfmyg27i5kkvoup GET https://markdownregistry.com/api/v1/resolve?ref=chaingpt-org/chaingpt-claude-skill/strategy GET https://markdownregistry.com/api/v1/blob/fa20f200cc87e5958e7e05bb3922157283f103403ea71b9ba66595a2916b4fb9
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 chaingpt-org/chaingpt-claude-skill
Every file in chaingpt-org/chaingpt-claude-skill