agentsclimarketplace

Marineconnect ops router

Skill Marineconnect/marineconnect-agent-skills/plugins/marineconnect-ops/skills/marineconnect-ops-router

Installable MarineConnect agent skills and OAuth-backed MCP plugin for Codex and ChatGPT Work mode.

Install
npx -y skills add Marineconnect/marineconnect-agent-skills --skill marineconnect-ops-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

  • 17 days oldThe repository was created 17 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route MarineConnect operations requests to the correct specialized workflow. Use for broad or ambiguous MarineConnect MCP requests, SuperAdmin operations, tenant/device/subscription/support/finance/radius/starlink diagnostics, and deciding which MarineConnect skill or MCP tool chain should be used first.

SKILL.md

3.2 KB, as published. Nobody here has run it

MarineConnect Ops Router

Use this as the first-pass dispatcher for broad MarineConnect operations prompts.

Routing

  • Support ticket, customer complaint, reboot request: use marineconnect-support-triage.
  • Device/router/telemetry/speed/connectivity: use marineconnect-technical-device-diagnostics.
  • Router reboot, Wi-Fi config, router action readiness: use marineconnect-router-actions.
  • Radius, radcheck, smartbox usage, online sessions, quota: use marineconnect-radius-smartbox.
  • ICT plan, bandwidth, VPN, firewall, customer internet plan: use marineconnect-ict-network.
  • Fleet, vessel, VMS, IoT profile/dashboard/device: use marineconnect-fleet-vms-iot.
  • Starlink service line, terminal, provider telemetry, trace, command history: use marineconnect-starlink-ops.
  • Tenant/device/vessel subscription: use marineconnect-subscription-ops.
  • Plan price, tenant price, quote, pricing import preview: use marineconnect-pricing-quote.
  • Invoice, payment, QR, debt, payment order: use marineconnect-invoice-payment.
  • Pricing mismatch, financial anomaly, currency, audit: use marineconnect-finance-audit.
  • Monthly activation, cutoff, payment-late, import batches: use marineconnect-monthly-lifecycle.
  • Dashboards, analytics reports, telemetry aggregates: use marineconnect-analytics-reporting.
  • OAuth clients, audit log, admin user, compliance, app release: use marineconnect-admin-audit.
  • eSIM, voucher marketplace, telephony CDR, provider package: use marineconnect-provider-marketplace.
  • QC, proof, evidence report, all-tool smoke: use marineconnect-qc-reporting.

Default Discovery

  1. Call mcp_list_tools_by_role with { role: "SuperAdmin", query: <user request>, include_planner: true, limit: 12 } when the exact chain is not obvious.
  2. Follow the planner resolver chain before id-scoped tools.
  3. If multiple tools look valid, choose the least risky read/preflight tool first.

Baseline Rules

  • Use the MarineConnect MCP server named marineconnect.
  • Assume Phase 2 is read-safe: do not call write, mutation, opt-in, opt-out, deactivate, cancel, delete, or execute tools unless a later phase explicitly allows it.
  • Treat SuperAdmin as the active runtime role unless the user explicitly states otherwise.
  • When the user gives a name, label, kit, service line, username, invoice number, or ticket number instead of an id, resolve the entity first before calling id-scoped tools.
  • Use UTC for date/time filters unless a smartbox data-usage tool specifically requires a timezone parameter.
  • Prefer DATA_ANALYTICS for telemetry, throughput, dashboard/report, and time-series questions when an equivalent analytics tool exists; use CORE for source-of-truth state, invoices, pricing, support tickets, admin, OAuth, Radius, and audit logs.
  • Return concise evidence: tool chain, params, important rows/counts/status, risks, and recommended next action.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.