Name: run
Author: willhama

Imported from willhama/md-file-study (corpus/openclaw__openclaw/files/src/agents/embedded-agent-runner/run/AGENTS.md). Install upstream with npx skills add willhama/md-file-study --skill run. Copyright stays with the author.

Embedded Runner Test Performance

The embedded attempt runner is one of the most expensive agent test surfaces. Use full-runner tests only when the behavior truly requires the runner.

Guardrails

Prefer focused helper tests for prompt assembly, runtime-context construction, cache metadata, token accounting, and maintenance decision logic.
Keep full runEmbeddedAttempt coverage for cross-component behavior that cannot be proven through helpers, not for a single derived field.
When extracting a helper from runner logic, make production call that helper directly, then test the helper. Avoid test-only copies of runner behavior.
Preserve context-engine coverage for sessionKey, sessionFile, token budget, current token count, prompt cache, and routing fields when slimming tests.
Treat a standalone full-runner test above a few seconds as suspect. First ask whether the proof can move to a production helper plus one cheap integration smoke.

Verification

For runner test slimming, run the touched helper test and the nearest two-file runner/context-engine surface.
Record Vitest duration, wall time, and RSS when the change is performance motivated.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install run and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "willhama-md-file-study-run", "kind": "skill", "name": "run", "description": "The embedded attempt runner is one of the most expensive agent test surfaces. Use full-runner tests only when the behavior truly requires the runner.", "publisher": "willhama", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "The embedded attempt runner is one of the most expensive agent test surfaces. Use full-runner tests only when the behavior truly requires the runner." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/willhama/md-file-study", "path": "corpus/openclaw__openclaw/files/src/agents/embedded-agent-runner/run/AGENTS.md", "ref": "c19de1e5213e9860055ac2385c28916a272efb46", "url": "https://github.com/willhama/md-file-study/blob/c19de1e5213e9860055ac2385c28916a272efb46/corpus/openclaw__openclaw/files/src/agents/embedded-agent-runner/run/AGENTS.md", "key": "willhama/md-file-study/corpus/openclaw__openclaw/files/src/agents/embedded-agent-runner/run/AGENTS.md" } }, "instructions": "\n\n# Embedded Runner Test Performance\n\nThe embedded attempt runner is one of the most expensive agent test surfaces.\nUse full-runner tests only when the behavior truly requires the runner.\n\n## Guardrails\n\n- Prefer focused helper tests for prompt assembly, runtime-context construction,\n cache metadata, token accounting, and maintenance decision logic.\n- Keep full `runEmbeddedAttempt` coverage for cross-component behavior that\n cannot be proven through helpers, not for a single derived fiel", "cost": { "context_tokens": 327 } }

run

About

Embedded Runner Test Performance

Guardrails

Verification

Use it

Install run and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews