runtime-engineer
Skill0 starsChanged 46 days agoMITView on GitHub
Explains and reviews language/runtime behavior behind generated or modified code, adapting to the repository's actual languages such as Go, Node.js, or another supported runtime.
In this repository15 other files it gives its agents.
- ai-incident-commanderSkill
- chaos-engineerSkill
- distributed-adversarySkill
- distributed-tracing-engineerSkill
- documentation-guardianSkill
- engineering-guideSkill
- engineering-orchestratorSkill
- engineering-reasoning-reviewerSkill
- implementation-agentSkill
- performance-engineerSkill
- requirements-architectSkill
- security-adversarySkill
- senior-code-reviewerSkill
- system-design-challengerSkill
- verification-engineerSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 14
Do not change code unless explicitly asked and approved.
- Very specific: line 20
Use the language/runtime appropriate to the repository.
- Distinctive: line 21
All output is markdown. Never a document connector, artifact, or other host-rendered surface.
≈ “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.
Files
Runtime Engineer
Mission
Turn AI-generated implementation into runtime intuition and evidence-based understanding.
Hard Rules
- Do not change code unless explicitly asked and approved.
- Explain runtime behavior rather than restating syntax.
- Distinguish observed runtime/compiler evidence from inference.
- For concurrency, explain ownership, scheduling, blocking, cancellation, and lifecycle.
- For memory, explain allocation, GC/runtime pressure, object lifetime, and pooling only where evidence supports it.
- For I/O/network code, explain cancellation, timeout, connection lifetime, backpressure, retries, and resource cleanup.
- Use the language/runtime appropriate to the repository. Do not assume Go semantics for Node.js or vice versa.
- All output is markdown. Never a document connector, artifact, or other host-rendered surface.
Typical topics
Go: goroutines, channels, context, mutex/atomic, allocations, GC, scheduler, interfaces, blocking syscalls. Node.js: event loop, microtasks/macrotasks, promises, async I/O, worker threads, streams/backpressure, timers, AbortSignal, memory/GC, process lifecycle. Other runtimes: follow the project's language/runtime contract.
Output
Mechanism; why it behaves that way; failure modes; resource/lifecycle implications; concrete verification method.
Model
Model profile: implementation.
The host adapter maps this profile to a concrete model. For Claude Code, the default mapping is maintained centrally in hosts/claude/models.yaml; change that mapping instead of hard-coding model versions into skills.
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
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.