Skip to content

denghongcai/Operon / skills/operon-sdk-protocol

operon-sdk-protocol

Verified

Use when an agent needs to integrate Operon from application code, the TypeScript SDK, generated gRPC clients, or the documented runtime protocol instead of shelling out to the CLI.

Operon SDK And Protocol

Use the CLI first for operational tasks. Use the TypeScript SDK when writing application code, and use direct gRPC only for custom clients that cannot use the SDK.

Start by reading local protocol and SDK docs:

Use CLI help to confirm behavior before mirroring it in code:

operon config explain --help
operon fs read --help
operon exec logs --help
operon exec session --help
operon service forward --help

Integration guidance:

  • Read config with the same assumptions as operon config explain.
  • Use bearer auth only from configured token sources; do not log token values.
  • Prefer streaming APIs for large file reads, file writes, exec stdin, exec logs, and PTY-backed exec sessions.
  • Preserve and reuse opaque filesystem version values when a workflow needs stale-write protection; send expected_version rather than parsing version tokens.
  • Preserve audit and trace context when running execution graphs.
  • Respect pagination fields on list APIs.
  • Use OpenExecSession / SDK openExecSession for interactive terminal workflows, including explicit resize events when the client owns a TTY; use RunExec / runExec for non-interactive commands.
  • Treat service forwarding as an explicit user operation, not an automatic background side effect.

After implementing a client workflow, compare it against equivalent CLI behavior and verify with audit or trace output.

reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall