deploy SKILL.md skillA
deploy 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/deploy@git:20261101.61ec6b2Pins git:20261101.61ec6b2 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/deploy/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261101.61ec6b2, committed Nov 1, 2026
- First version recorded
- May 19, 2026
- Size
- 5,872 bytes
- Repository stars
- 7
- License
- MIT
Deploy Solidity contracts to MAINNET (or testnet) safely via the ChainGPT plugin. End-to-end: generate → audit → compile → estimate → build unsigned tx → user signs → verify on Etherscan. MAINNET is the default; the audit gate is mandatory for mainnet deploys. The plugin never holds private keys — the user signs externally via MetaMask / Rabby / hardware wallet / ERC-4337 smart account. Triggers: deploy contract, ship contract, deploy to mainnet, deploy to ethereum, deploy to base, deploy to…
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 Deploy Skill
You orchestrate Solidity-contract deployment to **real mainnet chains** through the ChainGPT plugin. This skill is mainnet-first by design — testnet is an opt-in via the `network` parameter, never the default behavior.
The plugin is **custody-free**: it builds an unsigned transaction object and returns it. The user signs and broadcasts via their own wallet (MetaMask, Rabby, hardware wallet, ERC-4337 smart account, WalletConnect). Never ask the user for a private key. Never accept one in a tool argument.
## The mandatory pipeline
```
chaingpt_generate_contract (optional — if generating from description)
│
▼
chaingpt_audit_contract ← MANDATORY for mainnet. Costs 1 credit. Never skip.
│
▼
chaingpt_deploy_compile ← solc 0.8.x, returns bytecode + ABI
│
▼
chaingpt_deploy_estimate ← gas + USD cost on the chosen mainnet
│
▼
chaingpt_deploy_build_tx ← MAINNET REFUSES unless acknowledgeMainnet: true AND the bytecode came from
chaingpt_deploy_compile of source audited by chaingpt_audit_contract this session
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_knjwh3dzyj3s5ikr/8d451e528bf7f2e7621e322bbe01c4f0851799fb115dde4fb13f2bc412e6aee0.json
Then /plugin install deploy@markdownregistry-knjwh3dzyj3s5ikr in Claude Code. It installs git:20261101.61ec6b2, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add chaingpt-org/chaingpt-claude-skill/deploy@sha256:8d451e528bf7f2e7The line at the top of this page pins the label git:20261101.61ec6b2, 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_knjwh3dzyj3s5ikr)
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 chaingpt-org/chaingpt-claude-skill/deploy 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 deploy from somewhere else? Ask it: where did my deploy 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.61ec6b2 latest | 2026-11-01 | 61ec6b2 | 5,872 B | A | view · diff |
| git:20261101.75b5b1c | 2026-11-01 | 75b5b1c | 5,759 B | A | view · diff |
| git:20260610.61657e2 | 2026-06-10 | 61657e2 | 5,503 B | A | view · diff |
| git:20260519.ca5b8d0 | 2026-05-19 | ca5b8d0 | 5,512 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/deploy/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 (5872 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_knjwh3dzyj3s5ikr GET https://markdownregistry.com/api/v1/resolve?ref=chaingpt-org/chaingpt-claude-skill/deploy GET https://markdownregistry.com/api/v1/blob/8d451e528bf7f2e7621e322bbe01c4f0851799fb115dde4fb13f2bc412e6aee0
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