agentleFS
kurtosis-techkurtosis-tech/kurtosis/skills/port-forward/SKILL.md

port-forward

Skill558 starsChanged 3 years agoApache-2.0View on GitHub

View and manage port mappings for Kurtosis services. Check which local ports map to service ports and troubleshoot connectivity. Use when services aren't reachable or you need to find the right port.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If you ran with --no-connect, ports won't be forwarded locally:

    line 59
  2. Distinctive:

    When a port is unreachable, follow this diagnostic workflow:

    line 80

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Port Forward

View and manage port mappings for Kurtosis services.

View port info

kurtosis port print <enclave-name> <service-name> <port-id>

This prints the local URL for a specific port.

Find all ports

The easiest way to see all port mappings is enclave inspect:

kurtosis enclave inspect <enclave-name>

Output shows mappings like:

rpc: 8545/tcp -> 127.0.0.1:61817
ws: 8546/tcp -> 127.0.0.1:61813

The right side (127.0.0.1:61817) is how you access the service locally.

Port IDs

Port IDs are defined in the Starlark ServiceConfig:

plan.add_service(
    name="my-service",
    config=ServiceConfig(
        image="ethereum/client-go:latest",
        ports={
            "rpc": PortSpec(number=8545),      # port ID: "rpc"
            "ws": PortSpec(number=8546),        # port ID: "ws"
            "metrics": PortSpec(number=9001),   # port ID: "metrics"
        },
    ),
)

No-connect mode

If you ran with --no-connect, ports won't be forwarded locally:

# Ports not forwarded
kurtosis run --no-connect ./my-package

# Ports forwarded (default)
kurtosis run ./my-package

Kubernetes

On Kubernetes, port forwarding goes through the gateway. If ports stop working, restart the gateway:

pkill -f "kurtosis gateway"
kurtosis gateway &

Troubleshooting

When a port is unreachable, follow this diagnostic workflow:

# 1. Verify the enclave is running and check port mappings
kurtosis enclave inspect <enclave-name>

# 2. Confirm the specific service is running (not STOPPED)
kurtosis service inspect <enclave-name> <service-name>

# 3. If service is running but port fails, check service logs for errors
kurtosis service logs <enclave-name> <service-name>

# 4. On Kubernetes, verify the gateway is running
kurtosis gateway
SymptomCauseFix
Port not accessibleService not running or port not exposedCheck step 1-2 above
Connection refusedService crashed or wrong interfaceCheck service logs (step 3)
No port mapping shownRan with --no-connectRe-run without --no-connect
K8s ports unreachableGateway not runningRestart gateway (step 4)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.