runtime-engine
Skill119 starsChanged 5 months agoMITView on GitHub
Working on RuntimeEngine, ExecutionContext, agent execution, or the request lifecycle. Primary tasks are tasks/0003-compiled-agent-graph.md and tasks/0004-runtime-engine.md.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- theseus-run/theseustheir own version, first seen May 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- theseus-run/theseus★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architecture-reviewSkill
- code-reviewSkill
- documentationSkill
- git-workflowSkill
- mcp-toolsSkill
- project-architectureSkill
- prompt-renderingSkill
- refactoringSkill
- senior-python-engineeringSkill
- sidecar-auth-contextSkill
- skill-authoringSkill
- testingSkill
- vercel-react-best-practicesSkill
- yaml-schemaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Do not edit this file directly.
- Very specific: line 18
Use this when modifying RuntimeEngine, ExecutionContext, agent execution, or the request lifecycle.
- Very specific: line 40
Do not put request state (identity, tenant, current request, rendered prompts) on RuntimeEngine or the compiled graph.
- Distinctive: line 44
Keep the engine concurrency-safe by keeping it stateless w.r.t.
≈ “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
<!--
This file is generated by tools/skills.
Do not edit this file directly.
Edit .ai/skills/runtime-engine.md and run `make generate-ai`.
-->Skill: Runtime Engine
When to use this skill
Use this when modifying RuntimeEngine, ExecutionContext, agent execution, or
the request lifecycle. Primary tasks: tasks/0003-compiled-agent-graph.md,
tasks/0004-runtime-engine.md.
Files to read first
AGENTS.mddocs/ARCHITECTURE.mddocs/RUNTIME_LIFECYCLE.mddocs/adr/0001-runtime-engine-created-once.md
Architecture rules
RuntimeEngineis long-lived, created once at startup from theCompiledAgentGraph.ExecutionContextis per-request and carries all request-scoped state.- The compiled graph is immutable at runtime.
- The runtime operates only on compiled, typed models — never raw YAML.
Implementation rules
- Construct the engine only on startup paths; never inside request handlers.
- Do not put request state (identity, tenant, current request, rendered prompts)
on
RuntimeEngineor the compiled graph. - Pass
ExecutionContextexplicitly through routing, context resolution, prompt rendering, and tool execution. - Keep the engine concurrency-safe by keeping it stateless w.r.t. requests.
- Build the engine in
src/agentplatform/runtime; the graph insrc/agentplatform/graph.
Validation checklist
- Engine constructed once (startup), not per request.
- No request-scoped fields on the engine or graph.
- All per-request data lives on
ExecutionContext. - Compiled graph treated as immutable.
- Tests cover concurrent requests not leaking state.
make checkpasses.
Common mistakes to avoid
- Recreating the runtime or recompiling the graph per request.
- Storing "current user/request" on the engine.
- Mutating the compiled graph during execution.
- Hidden global/singleton request state.
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.