Run any Skill in Manus with one click

jarvis-add-plugin

Stars4

Forks1

UpdatedJune 20, 2026 at 09:10

Use when adding a new third-party integration / plugin to the jarvis hub (agents/core/plugins/*), or wiring an external API an agent can call. Triggers on "add a plugin", "integrate <service>", "new integration", or "let an agent call <API>".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

andrei649

andrei649/jarvis-hub

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	jarvis-add-plugin
description	Use when adding a new third-party integration / plugin to the jarvis hub (agents/core/plugins/*), or wiring an external API an agent can call. Triggers on "add a plugin", "integrate <service>", "new integration", or "let an agent call <API>".

Adding a plugin

Create agents/core/plugins/<myplugin>.py with a class MyPlugin. Keep the live HTTP/SDK client injectable (the network client is the host seam) so logic stays offline-testable — mirror an existing plugin (e.g. weather.py, n8n.py).

Instantiate in Orchestrator.load_agents() (orchestrator.py):

self.plugins["myplugin"] = MyPlugin(key=os.environ.get("MYPLUGIN_KEY", ""))

Trigger it in agents/core/plugin_gatherer.py:_eligible_plugins — add a keyword/permission branch that appends a (result_key, lambda: plugin.call(...)) spec. The fan-out runs eligible plugins concurrently; never await inline there.
Permission: gate access with any_agent_can(orch, "myplugin", intent); log E_PLUGIN_BLOCKED when denied.
Toggle (optional): add plugins.<name> to settings_db.py:DEFAULTS. Per-plugin secrets go under category "plugins"; prefer resolving them via secrets_vault.py, not raw .env.
Test: tests/test_<plugin>.py with a fake client — no real network.

Common mistakes

await plugin.x() inline in the gatherer → reintroduces serial fan-out; append a spec instead.
Hardcoding a secret instead of env/vault resolution.

More from this repository

same repository

jarvis-load-context

andrei649/jarvis-hub

Use FIRST, before reading source, when starting any task in the jarvis hub repo — to load the right files instead of the ~2M-token raw repo. Triggers at the start of backend, frontend, voice, security, WorldView, or marketing work, or when unsure "what should I read".

2026-07-194

jarvis-add-route

andrei649/jarvis-hub

Use when adding, moving, or removing an HTTP endpoint in the jarvis hub backend (agents/web.py or agents/core/routers/*). Triggers on "add a route", "new endpoint", "new API", route 4xx/parity-test failures, or any change to app.routes.

2026-06-204

jarvis-write-test

andrei649/jarvis-hub

Use when writing or fixing a pytest test in the jarvis hub (tests/test_*.py), or when a test fails on import/path/async-decorator issues. Triggers on "write a test", "add coverage", ModuleNotFoundError in tests, or "test hangs".

2026-06-204

name	jarvis-add-plugin
description	Use when adding a new third-party integration / plugin to the jarvis hub (agents/core/plugins/*), or wiring an external API an agent can call. Triggers on "add a plugin", "integrate <service>", "new integration", or "let an agent call <API>".

Adding a plugin

Create agents/core/plugins/<myplugin>.py with a class MyPlugin. Keep the live HTTP/SDK client injectable (the network client is the host seam) so logic stays offline-testable — mirror an existing plugin (e.g. weather.py, n8n.py).

Instantiate in Orchestrator.load_agents() (orchestrator.py):

self.plugins["myplugin"] = MyPlugin(key=os.environ.get("MYPLUGIN_KEY", ""))

Trigger it in agents/core/plugin_gatherer.py:_eligible_plugins — add a keyword/permission branch that appends a (result_key, lambda: plugin.call(...)) spec. The fan-out runs eligible plugins concurrently; never await inline there.
Permission: gate access with any_agent_can(orch, "myplugin", intent); log E_PLUGIN_BLOCKED when denied.
Toggle (optional): add plugins.<name> to settings_db.py:DEFAULTS. Per-plugin secrets go under category "plugins"; prefer resolving them via secrets_vault.py, not raw .env.
Test: tests/test_<plugin>.py with a fake client — no real network.

Common mistakes

await plugin.x() inline in the gatherer → reintroduces serial fan-out; append a spec instead.
Hardcoding a secret instead of env/vault resolution.