Marineconnect starlink ops

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

Inspect MarineConnect Starlink operations. Use for Starlink service lines, terminals, kits, provider telemetry, service-line monitors, warning kits, devices missing subscription, command history, trace logs, provider update age, provisioning checks, Starlink monthly analytics, report rows, and Starlink support diagnostics.From its SKILL.md

Install

npx -y skills add Marineconnect/marineconnect-agent-skills --skill marineconnect-starlink-ops

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

2 things to look at

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.

SKILL.md

1.3 KB, 207 tokens by cl100k_base, as published. Nobody here has run it

MarineConnect Starlink Ops

Workflow

Resolve device/kit/service line with tech_search_devices and tech_get_kit_detail.
Inspect service-line state with tech_list_service_line_monitors, tech_list_warning_kits, tech_list_devices_missing_subscription.
Inspect commands and traces with tech_get_service_line_command_history, tech_get_starlink_trace_logs.
Use analytics for provider update age, telemetry, throughput, monthly analytics, and Starlink reports.
Use provisioning check tools as read/preflight: starlink_provisioning_check_add_terminal, starlink_provisioning_check_reactivate_service_line.

Guardrails

Do not opt in, opt out, reactivate, deactivate, or mutate service line state in Phase 2.
Report provider/source gaps explicitly.

Output

Kit/service line/terminal, linked device, subscription context, telemetry recency, command/trace evidence, and safe next action.

What ships with it: 1 file

481 B alongside SKILL.md

agents/

openai.yaml481 B

Gives 0 of the 12 instructions most ship operate skills give in 207 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

Resolve device, kit, or service line identifiers
Inspect service-line state and warning kits
Inspect commands and trace logs
Use analytics for provider and telemetry data
Run provisioning checks as read or preflight
Report provider or source gaps explicitly

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.