Agent skill

Deploy To Mainnet

by sendaifun in sendaifun/solana-new

Guide a Solana project from devnet to mainnet production deployment.

MITAuto-check passedDevOps & Cloud

Install Deploy To Mainnet

skills CLI
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .claude/skills/deploy-to-mainnet && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deploy-to-mainnet
GitHub stars
179
Token cost
~1.8k tokens
SKILL.md length
499 words
Files
5 (incl. references)
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Guide a Solana project from devnet to mainnet production deployment.

  • Works in 6 steps: Check for .superstack/build-context.md.… → Run through… → Help configure production RPC using… → …
  • A user says deploy to mainnet
  • SKILL.md covers Preamble (run first), Overview, Workflow and Prior Context (Optional —…, plus 6 more sections
  • Calls curl; reaches mainnet.helius-rpc.com

What it does

Deploy To Mainnet is an agent skill from sendaifun/solana-new. Guide a Solana project from devnet to mainnet production deployment. Use when a user says "deploy to mainnet", "go to production", "deployment checklist", "prepare for launch", "mainnet deployment", or "ship it". Reads build-context.md from a prior build phase if available.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/deployment-checklist.md` and `references/program-upgrade-guide.md`).

It sits in DevOps & Cloud, covering Deployment. It works with Solana. The repository describes itself as: think. build. ship. tasteful & useful crypto apps. using a curated skills + knowledge base for AI agents on solana contracts & integrations. The licence is MIT.

When your agent uses it

  • A user says deploy to mainnet
  • Go to production
  • Deployment checklist
  • Prepare for launch

Example prompts

  • “deploy to mainnet”
  • “go to production”
  • “deployment checklist”
  • “/deploy-to-mainnet”

Requirements

  • A credential in YOUR_KEY

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Check for .superstack/build-context.md. If found, verify the build status (tests passing, devnet deployed). If not, ask the user about…
  2. Run through references/deployment-checklist.md item by item.
  3. Help configure production RPC using references/rpc-provider-guide.md.
  4. If deploying a program, follow references/program-upgrade-guide.md.
  5. Write a deployment report HTML artifact.
  6. Update .superstack/build-context.md with deployment status.

What it can do on your machine

Read from SKILL.md and the folder at commit 38a494a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • mainnet.helius-rpc.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deploy To Mainnet loads about 1.8k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 499 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sendaifun/solana-new at commit 38a494a, republished under its MIT licence (© sendaifun). 499 words, ~1,769 tokens.

Download SKILL.mdSave it as .claude/skills/deploy-to-mainnet/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
deploy-to-mainnet
description
Guide a Solana project from devnet to mainnet production deployment. Use when a user says "deploy to mainnet", "go to production", "deployment checklist", "prepare for launch", "mainnet deployment", or "ship it". Reads build-context.md from a prior build phase if available.

Preamble (run first)

bash
_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier": *"[^"]*"' | head -1 | sed 's/.*"telemetryTier": *"//;s/"$//'  || echo "anonymous")
_TEL_TIER="${_TEL_TIER:-anonymous}"
_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" || echo "no")
_TEL_START=$(date +%s)
_SESSION_ID="$$-$(date +%s)"
mkdir -p ~/.superstack
echo "TELEMETRY: $_TEL_TIER"
echo "TEL_PROMPTED: $_TEL_PROMPTED"
if [ "$_TEL_TIER" != "off" ]; then
_TEL_EVENT='{"skill":"deploy-to-mainnet","phase":"launch","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' 
echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null || true
_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"convexUrl":"[^"]*"' | head -1 | cut -d'"' -f4 || echo "")
[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"deploy-to-mainnet","phase":"launch","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
true
fi

If TEL_PROMPTED is no: Before starting the skill workflow, ask the user about telemetry. Use AskUserQuestion:

Help superstack get better! We track which skills get used and how long they take — no code, no file paths, no PII. Change anytime in ~/.superstack/config.json.

Options:

  • A) Sure, help superstack improve (anonymous)
  • B) No thanks

If A: run this bash:

bash
echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
_TEL_TIER="anonymous"
touch ~/.superstack/.telemetry-prompted

If B: run this bash:

bash
echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
_TEL_TIER="off"
touch ~/.superstack/.telemetry-prompted

This only happens once. If TEL_PROMPTED is yes, skip this entirely and proceed to the skill workflow.

Wrong skill? See SKILL_ROUTER.md for all available skills.

Deploy to Mainnet

Overview

Take a devnet-tested Solana project and prepare it for mainnet deployment. Run through a structured pre-flight checklist, configure production infrastructure, and execute the deployment with proper verification.

Workflow

  1. Check for .superstack/build-context.md. If found, verify the build status (tests passing, devnet deployed). If not, ask the user about their current state.
  2. Run through references/deployment-checklist.md item by item.
  3. Help configure production RPC using references/rpc-provider-guide.md.
  4. If deploying a program, follow references/program-upgrade-guide.md.
  5. Write a deployment report HTML artifact.
  6. Update .superstack/build-context.md with deployment status.

Prior Context (Optional — never block on this)

If .superstack/build-context.md exists, check build status and warn if tests aren't passing or devnet hasn't been tested. If it doesn't exist, proceed immediately — ask the user: "Have you tested on devnet?" and go from there.

Non-Negotiables

  • Never block on missing context files. Ask the user directly instead.
  • Ask "Have you tested on devnet?" — if no, recommend it but don't refuse to proceed.
  • Never deploy with a devnet RPC URL. Verify the endpoint.
  • Always check that private keys are not committed to git before deployment.
  • Always verify the deployment on-chain after it completes.
  • If the project has a program, discuss upgrade authority management before deploying.
Show full SKILL.md (209 more words)Show less

Phase Handoff

This skill is Phase 3 (Launch) in the Idea → Build → Launch journey.

Reads: .superstack/build-context.md (from Phase 2) Writes/Updates: .superstack/build-context.md (creates if missing) with:

  • build_status.mainnet_deployed: true
  • build_status.mainnet_program_id: string (if applicable)
  • build_status.deployment_date: ISO timestamp
  • build_status.rpc_provider: string

See ../../../data/specs/phase-handoff.md for the full JSON contract.

Resources

Writing Tone
references/

Quick Start

bash
# Full deploy runbook: see ../../data/guides/deploy-runbook.md

# Quick version:
anchor build
solana config set --url "https://mainnet.helius-rpc.com/?api-key=YOUR_KEY"
solana balance  # Need ~5 SOL

# Pre-flight
grep -rn "devnet" src/ app/ --include="*.ts" --include="*.rs" | grep -v test  # Should be 0 results
sha256sum target/deploy/my_program.so  # Save build hash

# Deploy
anchor deploy --provider.cluster mainnet-beta

# Verify
solana program show <PROGRAM_ID>

Decision Points

  • Which RPC for mainnet? NEVER use public RPC for deployment. Helius paid tier minimum.
  • Upgrade authority: Keep for first 3 months. Transfer to Squads multisig when stable. Freeze only when fully audited.
  • Invariant-critical program? If the program protects high-value assets or has non-trivial conservation / authorization / state-machine / CPI-correctness properties, ask whether those invariants are machine-checked before mainnet. Route to the community skill qedgen-formal-verification for spec-driven Lean proofs + Kani + proptests. Testing alone is not sufficient evidence for these property classes.
  • Full checklist: See ../../data/guides/deploy-runbook.md for complete pre-flight + post-deploy verification.
  • Wallet strategy: See ../../data/guides/rpc-wallet-guide.md — dedicated mainnet keypair, never reuse devnet key.

Telemetry (run last)

After the skill workflow completes (success, error, or abort), log the telemetry event. Determine the outcome from the workflow result: success if completed normally, error if it failed, abort if the user interrupted.

Run this bash:

bash
_TEL_END=$(date +%s)
_TEL_DUR=$(( _TEL_END - ${_TEL_START:-$_TEL_END} ))
_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null | grep -o '"telemetryTier": *"[^"]*"' | head -1 | sed 's/.*"telemetryTier": *"//;s/"$//' || echo "anonymous")
if [ "$_TEL_TIER" != "off" ]; then
echo '{"skill":"deploy-to-mainnet","phase":"launch","event":"completed","outcome":"OUTCOME","duration_s":"'"$_TEL_DUR"'","session":"'"$_SESSION_ID"'","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'","platform":"'$(uname -s)-$(uname -m)'"}' >> ~/.superstack/telemetry.jsonl 2>/dev/null || true
true
fi

Replace OUTCOME with success/error/abort based on the workflow result.

© sendaifun, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/launch/deploy-to-mainnet of sendaifun/solana-new.

  • SKILL.md
  • agents/openai.yaml
  • references/deployment-checklist.md
  • references/program-upgrade-guide.md
  • references/rpc-provider-guide.md

Open the folder on GitHubat commit 38a494a

Compare with similar skills

Deploy To Mainnet next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deploy To Mainnet compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deploy To Mainnet this skillsendaifun/solana-new179—~1.8kAutomated safety check: PassMIT
Alchemy Upgrade Migrationjeremylongshore/tons-of-skills-marketplace2.8k—~1.3kAutomated safety check: PassMIT
Kubeshark Installerkubeshark/kubeshark12k—~3.6kAutomated safety check: NotesApache-2.0
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Mirrord Operatormetalbear-co/mirrord5.4k1 repos~4.6kAutomated safety check: PassMIT
KubeSphere ServiceMesh Managerkubesphere/kubesphere17k—~2.4kAutomated safety check: PassCustom licence

Similar skills

  • Alchemy Upgrade Migration

    jeremylongshore/tons-of-skills-marketplace

    Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence.

    2.8k GitHub stars~1.3k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Mirrord Operator

    metalbear-co/mirrord

    Help users install and configure the mirrord Operator for team/enterprise environments.

    5.4k GitHub starsUsed in 1 repo~4.6k tokens
    DevOps & CloudAuto-check passed
  • KubeSphere ServiceMesh Manager

    kubesphere/kubesphere

    Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.

    17k GitHub stars~2.4k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Vercel

    remotion-dev/remotion

    Official

    Set up a Codex monitor for Vercel deployments and preview URLs.

    63k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from sendaifun/solana-new

All 13 skills in this repo
  • Find Next Crypto Idea

    sendaifun/solana-new

    Interview users sharply to discover, rank, or validate what they should build in crypto.

    179 GitHub stars~2.5k tokensUpdated 8 days ago
    Auto-check passed
  • Colosseum Copilot

    sendaifun/solana-new

    Search and analyze 5,400+ Solana hackathon projects using Colosseum Copilot.

    179 GitHub stars~2.9k tokensUpdated 8 days ago
    Auto-check passed
  • Competitive Landscape

    sendaifun/solana-new

    Map the competitive landscape for a crypto product idea. An agent skill from sendaifun/solana-new.

    179 GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check passed
  • Defillama Research

    sendaifun/solana-new

    Research DeFi protocols and market opportunities using DefiLlama data.

    179 GitHub stars~1.8k tokensUpdated 8 days ago
    Auto-check passed
  • Solana Beginner

    sendaifun/solana-new

    Teach Solana fundamentals to developers new to the ecosystem.

    179 GitHub stars~2.4k tokensUpdated 8 days ago
    Auto-check passed
  • Submit To Hackathon

    sendaifun/solana-new

    Prepare and optimize a hackathon submission for a Solana project.

    179 GitHub stars~1.7k tokensUpdated 8 days ago
    Auto-check passed

Works with

Categories

Questions about Deploy To Mainnet

What does Deploy To Mainnet do?

Guide a Solana project from devnet to mainnet production deployment. Deploy To Mainnet is an agent skill from sendaifun/solana-new. Guide a Solana project from devnet to mainnet production deployment.

When should I use Deploy To Mainnet?

Deploy To Mainnet fits situations like: A user says deploy to mainnet; go to production; deployment checklist; prepare for launch.

How do I install Deploy To Mainnet in Claude Code?

Run `npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a claude-code`. Or copy the skill folder (skills/launch/deploy-to-mainnet in sendaifun/solana-new) into .claude/skills/deploy-to-mainnet in your project. Claude Code loads it when a task matches its description.

How do I install Deploy To Mainnet in Codex?

Run `npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a codex`. Or copy the skill folder (skills/launch/deploy-to-mainnet in sendaifun/solana-new) into .agents/skills/deploy-to-mainnet in your project. Codex loads it when a task matches its description.

Can I use Deploy To Mainnet in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deploy-to-mainnet, .gemini/skills/deploy-to-mainnet, .github/skills/deploy-to-mainnet and .opencode/skills/deploy-to-mainnet in your project.

What does Deploy To Mainnet need to run?

Going by SKILL.md and its folder, Deploy To Mainnet needs the command-line tools its instructions call (curl). Our summary lists: A credential in YOUR_KEY.

Does Deploy To Mainnet access the network?

SKILL.md names 1 domain. In commands or code: mainnet.helius-rpc.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Deploy To Mainnet safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Deploy To Mainnet use?

Deploy To Mainnet is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deploy To Mainnet use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.

What are the alternatives to Deploy To Mainnet?

Skills that share tags, products or a category with Deploy To Mainnet: Alchemy Upgrade Migration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars) and Mirrord Operator (metalbear-co/mirrord, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deploy To Mainnet?

sendaifun (a GitHub organization) maintains it in sendaifun/solana-new, which has 179 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 2, 2026.

Source: sendaifun/solana-new on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.