Skip to content

denghongcai/Operon / skills/operon-services

operon-services

Verified

Use when an agent needs to inspect service metadata, run service health checks, or create explicit local TCP or UDP forwards to policy-allowed Operon services.

Operon Services

Use this skill when a remote node exposes service metadata in policy and the local machine should consume that service through an explicit forward. Operon assumes the two Operon nodes are already reachable through the user's private network.

Inspect exact syntax first:

operon service --help
operon service list --help
operon service check --help
operon service forward --help
operon service forward-udp --help

Command choice:

  • List allowed services: operon service list <node>.
  • Check service health: operon service check <node> <service_id>.
  • TCP forward: operon service forward <node> <service_id> --listen 127.0.0.1:<port>.
  • UDP/datagram forward: operon service forward-udp <node> <service_id> --listen 127.0.0.1:<port>.

Example scenario:

  1. node-a has a policy-allowed service for 127.0.0.1:80.
  2. On node-b, run a local TCP forward on 127.0.0.1:8080.
  3. Local tools on node-b use 127.0.0.1:8080 as if the service were local.

Confirm before binding a public listen address such as 0.0.0.0:<port>. Prefer loopback addresses unless the user explicitly asks for broader exposure. Verify service usage through audit show and stop forwards when the task is complete.

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: 469kUpdated 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