Name: outbound
Author: ZDStudios

Imported from ZDStudios/AIOS (openclaw-main/openclaw-main/src/infra/outbound/AGENTS.md). Install upstream with npx skills add ZDStudios/AIOS --skill outbound. Copyright stays with the author.

Outbound Test Performance

Outbound helpers sit on hot reply, action, media, and channel contract paths. Keep argument and payload tests narrow unless they are intentionally exercising real delivery.

Guardrails

Prefer pure param/spec/normalization helpers for send-argument, media-source, alias, and payload-shape coverage. Do not import real delivery runtimes when the test only asserts normalized arguments.
Avoid partial-real mocks with importActual() around broad outbound delivery modules. Mock the exact seam under test, then cover the real delivery runtime in a focused integration test.
Before discovering plugin-owned media/action metadata, first check whether the call actually includes plugin-owned params. Standard send params should not trigger bundled channel message-tool discovery.

Verification

Benchmark the affected outbound test file before/after with pnpm test <file>.
Run the closest media/action/payload contract test when changing a shared outbound helper.

# 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 outbound 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": "zdstudios-aios-outbound", "kind": "skill", "name": "outbound", "description": "Outbound helpers sit on hot reply, action, media, and channel contract paths. Keep argument and payload tests narrow unless they are intentionally exercising real delivery.", "publisher": "ZDStudios", "version": "1.0.0", "capabilities": { "domains": [ "coding", "legal" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Outbound helpers sit on hot reply, action, media, and channel contract paths. Keep argument and payload tests narrow unless they are intentionally exercising real delivery." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/ZDStudios/AIOS", "path": "openclaw-main/openclaw-main/src/infra/outbound/AGENTS.md", "ref": "22a882779a13a6ff7a58973e062e947a35ddb9b9", "url": "https://github.com/ZDStudios/AIOS/blob/22a882779a13a6ff7a58973e062e947a35ddb9b9/openclaw-main/openclaw-main/src/infra/outbound/AGENTS.md", "key": "ZDStudios/AIOS/openclaw-main/openclaw-main/src/infra/outbound/AGENTS.md" } }, "instructions": "# Outbound Test Performance\n\nOutbound helpers sit on hot reply, action, media, and channel contract paths.\nKeep argument and payload tests narrow unless they are intentionally exercising\nreal delivery.\n\n## Guardrails\n\n- Prefer pure param/spec/normalization helpers for send-argument, media-source,\n alias, and payload-shape coverage. Do not import real delivery runtimes when\n the test only asserts normalized arguments.\n- Avoid partial-real mocks with `importActual()` around broad outbound delivery\n modules. Mock the exact seam under test, then cover the real delivery runtime\n in a focused in", "cost": { "context_tokens": 255 } }

outbound

About

Outbound Test Performance

Guardrails

Verification

Use it

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

Manifest

Reviews