How do I install the Se Pb Scripts skill?

Run npx skillmds@latest add godimas101/se-pb-scripts in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Se Pb Scripts safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Se Pb Scripts?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Se Pb Scripts free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Se Pb Scripts?

Godimas101 (@godimas101) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Se Pb Scripts by godimas101 — Agent Skill

Name: Se Pb Scripts
Rating: 4.5 (4 reviews)
Author: Godimas101

Se Pb Scripts

Use for Space Engineers in-game Programmable Block scripts — user-written C# code that runs in a sandboxed VM inside a PB. Covers the Main loop, `Program` class structure, `UpdateFrequency`, `IMyGridTerminalSystem`, `IMyIntergridCommunicationSystem` (IGC), coroutines, `Echo`, `Me.CustomData`, `Storage`, and the whitelist. Concrete triggers: writing a Main method that runs on a PB, GridTerminalSystem.GetBlocksOfType, IGC broadcasting, PB CustomData config, unbounded-loop instruction limit errors. SKIP for: compiled DLL mods with full .NET (use se-csharp or se-tss — different sandbox, different capabilities), SBC-only mods (use se-sbc). PB scripts CANNOT do I/O, threading, reflection, or use most `System.*` namespaces — this skill enforces those constraints throughout.

Godimas101 Updated Sep 22, 2026

File contents

SE PB Scripts — Programmable Block scripts

Sandboxed C# that runs inside a Programmable Block. Whitelisted namespaces only. Whitelist restrictions apply throughout — enforce them in every suggestion.

Read first

references/scripts.md — Main loop, UpdateFrequency, IMyGridTerminalSystem, IMyIntergridCommunicationSystem (IGC), coroutines, sandbox restrictions, whitelist reference.

Sandbox — the hard constraints

No I/O. No System.IO, no file access, no Console. State goes in Storage (persistent string) or Me.CustomData (mutable in-game).
No threading. No Task, no Thread, no async/await. Long work uses coroutines (yield return).
No reflection. No Type.GetType() beyond whitelisted names.
Limited System.*. System.Collections.Generic, System.Linq, System.Text mostly OK. System.Net — no.
Instruction budget per tick. Long loops trip ScriptOutOfRangeException. Break large sweeps across ticks with coroutines.

The five mod types — where PB fits

PB scripts are a completely separate environment from compiled mods. See ../se-core/references/mod-types.md for the table. Get this wrong and none of your compiled-mod code will work in a PB.

Shipping checklist

Instruction count checked — no unbounded loops over large block lists per tick
Storage used for state that must survive recompile
Echo() used for debug output, not Me.GetSurface(0) hardcoded
Graceful handling when expected blocks are missing from the grid
Save() implemented if state persistence matters

---name: se-pb-scriptsdescription: Use for Space Engineers in-game Programmable Block scripts — user-written C# code that runs in a sandboxed VM inside a PB. Covers the Main loop, `Program` class structure, `UpdateFrequency`, `IMyGridTerminalSystem`, `IMyIntergridCommunicationSystem` (IGC), coroutines, `Echo`, `Me.CustomData`, `Storage`, and the whitelist. Concrete triggers: writing a Main method that runs on a PB, GridTerminalSystem.GetBlocksOfType, IGC broadcasting, PB CustomData config, unbounded-loop instruction limit errors. SKIP for: compiled DLL mods with full .NET (use se-csharp or se-tss — different sandbox, different capabilities), SBC-only mods (use se-sbc). PB scripts CANNOT do I/O, threading, reflection, or use most `System.*` namespaces — this skill enforces those constraints throughout.---# SE PB Scripts — Programmable Block scriptsSandboxed C# that runs inside a Programmable Block. Whitelisted namespaces only. **Whitelist restrictions apply throughout — enforce them in every suggestion.**## Read first**[references/scripts.md](references/scripts.md)** — Main loop, `UpdateFrequency`, `IMyGridTerminalSystem`, `IMyIntergridCommunicationSystem` (IGC), coroutines, sandbox restrictions, whitelist reference.## Sandbox — the hard constraints- **No I/O.** No `System.IO`, no file access, no `Console`. State goes in `Storage` (persistent string) or `Me.CustomData` (mutable in-game).- **No threading.** No `Task`, no `Thread`, no `async`/`await`. Long work uses coroutines (`yield return`).- **No reflection.** No `Type.GetType()` beyond whitelisted names.- **Limited System.*.** `System.Collections.Generic`, `System.Linq`, `System.Text` mostly OK. `System.Net` — no.- **Instruction budget per tick.** Long loops trip `ScriptOutOfRangeException`. Break large sweeps across ticks with coroutines.## The five mod types — where PB fitsPB scripts are a completely separate environment from compiled mods. See [../se-core/references/mod-types.md](../se-core/references/mod-types.md) for the table. Get this wrong and none of your compiled-mod code will work in a PB.## Shipping checklist- [ ] Instruction count checked — no unbounded loops over large block lists per tick- [ ] `Storage` used for state that must survive recompile- [ ] `Echo()` used for debug output, not `Me.GetSurface(0)` hardcoded- [ ] Graceful handling when expected blocks are missing from the grid- [ ] `Save()` implemented if state persistence matters

Frequently asked questions