Name: Simulation dry-run testing on Gorlami forks
Author: Skills Guide Bot

Automated summary

Runs scenario tests against Gorlami forked RPCs to validate fund-moving scripts before live broadcasting.

Strengths

Safe dry-run environment without real fund risk
Accurate gas estimation and calldata verification
Supports multi-step sequencing for complex strategies

Limitations

Requires Gorlami fork infrastructure and configuration
Not a general sandbox for non-blockchain scripts
Assumes familiarity with strategy scripts and DeFi concepts

When to use it

Use when you need to verify a DeFi transaction flow (swap, lend, bridge) without risking real funds.

When not to use it

Avoid for simple read-only queries or non-blockchain scripting tasks.

Security analysis

Safe

Quality score80/100

The skill is a high-level guide for dry-run testing on a fork RPC before live transactions. It references only safe practices (scenario testing, validation checklists, safe script patterns) and contains no executable commands, destructive instructions, or data exfiltration risks.

No concerns found

How this analysis is made

Examples

Swap dry-run on forked Uniswap

Run a dry-run simulation of swapping 10 ETH for USDC on a forked Ethereum mainnet using Gorlami fork RPC, checking for slippage and approval issues.

Lending deposit scenario test

Simulate depositing 5 ETH into Aave on a Gorlami fork and verify the resulting aToken balance, health factor, and gas cost before broadcasting live.

Multi-step strategy dry-run

Test a looping strategy: supply ETH to Compound, borrow USDC, swap to ETH, and supply again — all as a dry run on a Gorlami fork to validate the sequence and gas usage.

name: simulation-dry-run description: How to run scenario tests against Gorlami fork RPCs (dry runs) before broadcasting live transactions. Covers config, seeding balances, runner flags, and safe script patterns. metadata: tags: simulation, dry-run, fork, gorlami, safety, strategies, scripts

When to use

Use this skill when you are:

Writing or modifying a fund-moving script (swaps, lending, bridging, looping)
Iterating on a strategy deposit/update/withdraw/exit flow
Debugging approvals, units, calldata shapes, gas issues, or multi-step sequencing

How to use

rules/quickstart.md - Config + fastest way to run a fork scenario
rules/scenario-checklist.md - What to validate before “live”
rules/script-pattern.md - Recommended CLI + gorlami_fork(...) pattern
rules/gotchas.md - Common fork-mode failures and mitigations

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/download' --output '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md.part' && mv '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md.part' '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md' && test -s '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/simulation-dry-run' && cp -R '.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub' '.claude/skills/simulation-dry-run'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub'

openskills read 'simulation-dry-run-testing-on-gorlami-forks-mm5t89ub'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/simulation-dry-run-testing-on-gorlami-forks-mm5t89ub/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.