Context ManageSAFE
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
Overview
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
938b496bbe73OBSERVED · 2026-10-14What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: context-manage description: Manage Kurtosis contexts for connecting to different Kurtosis instances. Add, list, switch, and remove contexts. Use when working with multiple Kurtosis environments (local, remote, team shared). compatibility: Requires kurtosis CLI. metadata: author: ethpandaops version: "1.0" --- # Context Manage Manage Kurtosis contexts for connecting to different Kurtosis instances. ## What are contexts? Contexts define which Kurtosis instance the CLI talks to. The default context is `default` which connects to the local engine (Docker or Kubernetes). ## List contexts ```bash kurtosis context ls ``` Shows all configured contexts and which one is active. ## Add a context ```bash kurtosis context add <context-name> ``` ## Switch context ```bash kurtosis context set <context-name> ``` After switching, restart the engine or portal as needed. ## Remove a context ```bash kurtosis context rm <context-name> ``` ## Common workflow ```bash # Check which context is active kurtosis context ls # Switch to a different environment kurtosis context set staging # Verify the switch succeeded kurtosis context ls # Start portal if using a remote context kurtosis portal start # Switch back to local kurtosis context set default ``` ## Error handling | Scenario | Behavior | Resolution | |----------|----------|------------| | Switch to non-existent context | Command fails with error | Run `kurtosis context ls` to see available contexts | | Remove active context | Command fails — cannot remove active | Switch to another context first with `kurtosis context set` | | Engine running after switch | Engine still connected to old context | Run `kurtosis engine restart` after switching contexts |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
938b496bbe73full audit observations/trust-audit/skill/kurtosis-tech__context-manage.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-14 | 938b496bbe73 | SAFE | B | 89 | first audit |
Questions
What does the Context Manage skill do?
A platform for packaging and launching blockchain infra. Think docker compose for blockchain
Is Context Manage safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Context Manage access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (938b496bbe73), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.