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.
Guide a Solana project from devnet to mainnet production deployment.
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .claude/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnetType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .agents/skills/deploy-to-mainnet && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .agents/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .cursor/skills/deploy-to-mainnet && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .cursor/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sendaifun/solana-new.git --path skills/launch/deploy-to-mainnet--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .gemini/skills/deploy-to-mainnet && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .gemini/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sendaifun/solana-new deploy-to-mainnetInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .github/skills/deploy-to-mainnet && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .github/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sendaifun/solana-new --skill deploy-to-mainnet -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sendaifun/solana-new deploy-to-mainnet --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sendaifun/solana-new.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch/deploy-to-mainnet .opencode/skills/deploy-to-mainnet && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "deploy-to-mainnet" agent skill from https://github.com/sendaifun/solana-new/tree/main/skills/launch/deploy-to-mainnet into .opencode/skills/deploy-to-mainnet/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "deploy-to-mainnet", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
deploy-to-mainnetGuide 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. 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.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 38a494a. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
curlFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
mainnet.helius-rpc.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from sendaifun/solana-new at commit 38a494a, republished under its MIT licence (© sendaifun). 499 words, ~1,769 tokens.
.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._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
fiIf 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:
If A: run this bash:
echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
_TEL_TIER="anonymous"
touch ~/.superstack/.telemetry-promptedIf B: run this bash:
echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
_TEL_TIER="off"
touch ~/.superstack/.telemetry-promptedThis 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.
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.
.superstack/build-context.md. If found, verify the build status (tests passing, devnet deployed). If not, ask the user about their current state..superstack/build-context.md with deployment status.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.
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: truebuild_status.mainnet_program_id: string (if applicable)build_status.deployment_date: ISO timestampbuild_status.rpc_provider: stringSee ../../../data/specs/phase-handoff.md for the full JSON contract.
# 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>qedgen-formal-verification for spec-driven Lean proofs + Kani + proptests. Testing alone is not sufficient evidence for these property classes.../../data/guides/deploy-runbook.md for complete pre-flight + post-deploy verification.../../data/guides/rpc-wallet-guide.md — dedicated mainnet keypair, never reuse devnet key.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:
_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
fiReplace 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
SKILL.md and 4 other files (references) in skills/launch/deploy-to-mainnet of sendaifun/solana-new.
Open the folder on GitHubat commit 38a494a
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Deploy To Mainnet this skillsendaifun/solana-new | 179 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Alchemy Upgrade Migrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Mirrord Operatormetalbear-co/mirrord | 5.4k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence |
jeremylongshore/tons-of-skills-marketplace
Migrate archived Alchemy JavaScript SDK integrations to current capability-specific clients with parity, canary, and rollback evidence.
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
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.
metalbear-co/mirrord
Help users install and configure the mirrord Operator for team/enterprise environments.
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
sendaifun/solana-new
Interview users sharply to discover, rank, or validate what they should build in crypto.
sendaifun/solana-new
Search and analyze 5,400+ Solana hackathon projects using Colosseum Copilot.
sendaifun/solana-new
Map the competitive landscape for a crypto product idea. An agent skill from sendaifun/solana-new.
sendaifun/solana-new
Research DeFi protocols and market opportunities using DefiLlama data.
sendaifun/solana-new
Teach Solana fundamentals to developers new to the ecosystem.
sendaifun/solana-new
Prepare and optimize a hackathon submission for a Solana project.
Works with
Categories
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.
Deploy To Mainnet fits situations like: A user says deploy to mainnet; go to production; deployment checklist; prepare for launch.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.