DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to catch missing service dependencies before a plugin runs with Rutis

List what each plugin needs and provides, and fail early on a service nothing provides.

Who it is forA developer assembling several plugins who needs to confirm the system is wired correctly before starting it.

The problemA plugin that depends on a service nobody provides can fail in confusing ways at runtime, and it is hard to see the full dependency picture by hand.

The outcomeA printed view of every plugin's dependencies and provided services, and a clear failure when a required service has no provider.

What you need first

  • Node.js with npm, or Bun, for the TypeScript path
  • uv for the Python path
  • Go for the Go path
  • A Rust toolchain with cargo for the embedding path

Steps

  1. Run npx @arcships/rutis-host new weather --lang node and cd weather && npm install to create a project with a plugin.
  2. Run npx rutis-host check to see what each plugin needs and provides.
  3. Fix any reported service that nothing provides, then run npx rutis-host dev.

Prompt for your agent

Using the repo arcships/rutis, run `npx rutis-host check` inside the project at <target>. Expected output: a list of each plugin's dependencies and provided services, or a failure naming a service nothing provides. Verify that adding a provider for the missing service makes the check pass.

Caveat. The check reports dependencies declared in plugin code, so it only catches services the plugins actually declare.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page