Przejdź do treści
Biblioteka skilli
Produktywność osobista · Analiza

connection-status

/connection-status

Odczytuje z widżetu na Macu, czy połączenie internetowe jest szybkie, mobilne lub wolne, zanim rozpoczniesz duże pobieranie, wysyłkę albo wdrożenie.

Repozytorium
speedwidget ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.2026

Ocena i bezpieczeństwo

85/ 100Klasa: dobry
Format20 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Odczytuje z widżetu na Macu, czy połączenie internetowe jest szybkie, mobilne lub wolne, zanim rozpoczniesz duże pobieranie, wysyłkę albo wdrożenie.

Wyzwalacze z opisu

how fast is the internetam I onlineare we on the hotspot / metered / mobile datawhy is everything slowwas the connection downpingspeed testpublic IP
Oryginalny opis (EN)

Use whenever you need to know your current internet connection on this Mac - "how fast is the internet", "am I online", "are we on the hotspot / metered / mobile data", "why is everything slow", "was the connection down", "ping", "speed test", "public IP", "Wi-Fi signal", or before deciding whether a large download, upload, install or deploy is OK right now. Reads the always-running speedwidget desktop widget for free (0 bytes); can trigger a 256 KB speed test.

Jak działa

  1. Commands (put build/speedwidget or /Applications/speedwidget.app/Contents/MacOS/speedwidge
  2. status.json fields
  3. Good / bad thresholds (same as the widget's mouse-over texts, sources in docs/SOURCES.md i
  4. Data budget (why it is cheap)
  5. How to answer
Sekcje z nagłówków SKILL.md, w oryginale · 65 linii, 741 słów
Podgląd SKILL.md
---
name: connection-status
description: Use whenever you need to know your current internet connection on this Mac - "how fast is the internet", "am I online", "are we on the hotspot / metered / mobile data", "why is everything slow", "was the connection down", "ping", "speed test", "public IP", "Wi-Fi signal", or before deciding whether a large download, upload, install or deploy is OK right now. Reads the always-running speedwidget desktop widget for free (0 bytes); can trigger a 256 KB speed test.
---

# connection-status (speedwidget API)

The desktop widget `speedwidget` (https://github.com/franzenzenhofer/speedwidget, LaunchAgent `io.github.franzenzenhofer.speedwidget`, or the Mac App Store app `com.franzai.speedwidget`) measures
the connection all the time with almost no data and exposes it to Claude. **Read before you guess:**
never claim the connection is fast/slow/down without this tool output.

## Commands (put `build/speedwidget` or `/Applications/speedwidget.app/Contents/MacOS/speedwidget` on your PATH, see README)

| Command | Network cost | What you get |
|---|---|---|
| `speedwidget status` | 0 bytes | live status JSON; **exit 2 = widget not running / stale (>3 min)** |
| `speedwidget history [hours]` | 0 bytes | one JSONL line per minute (default 6 h, kept 7 days) |
| `speedwidget events [hours]` | 0 bytes | connection events JSONL: offline / noInternet / online, network switches (default 24 h) |
| `speedwidget test` | ~262 KB (only when really needed) | asks the widget for a speed burst now, waits up to 40 s, prints the new status |
| `speedwidget --once` | ~262 KB | standalone ping + burst, works without the widget |

Raw files: `~/Library/Application Support/speedwidget/{status.json,history.jsonl,events.jsonl}` (source install) or
`~/Library/Containers/com.franzai.speedwidget/Data/Library/Application Support/speedwidget/` (App Store app).
The CLI always reads the right one; if you read files directly, use whichever status.json is newer.

## status.json fields

- `state`: `online` | `noInternet` (link up, but 2 TCP pings in a row failed - e.g. hotspot without mobile data) | `offline` (no usable interface). `stateSince`, `lastEvent` (e.g. "back online (down 2 min)").
- `network` (e.g. "iPhone hotspot · metered"), `kind` (Wi-Fi/Ethernet/Cellular), `interface`, `gateway`,
  `iPhoneHotspot` (gateway 172.20.10.x), `metered` (macOS expensive/constrained = Low Data Mode / hotspot).
- `wifi`: `rssiDbm` (> -60 good, < -75 bad), `noiseDbm`, `linkMbps` (radio link rate Mac<->router, NOT internet speed), `channel`, `band`.
  SSID is not available (macOS hides it without location permission).
- `publicIP`, `cloudflareLocation` (Cloudflare colo + country, from a ~200 byte trace on network change / every 30 min).
- `pingMs`: TCP handshake time to 1.1.1.1:443 (once a minute online, every 10 s while down).
- `burstMbps`, `burstAt`: last 256 KB download burst (rate over the second half of the bytes). On fast links this is a
  LOWER BOUND (TCP slow start) - say so when quoting it.
- `last6h`: `medianPingMs`, `maxObservedMbps` (peak of real traffic from the kernel byte counters, 0 bytes, shows what
  the line actually delivered when used), `maxBurstMbps`, `minutesOffline`, `minutesNoInternet`.
- `stability` (last 60 min, or since the last switch to a different network - field `since`; a widget restart,
  Mac sleep or drop + reconnect to the same network does not reset it): `label` stable | unstable | down, `score` 0-100 (>= 80 = stable), `drops`,
  `downMinutes`, `lostPings`, `failedTests`, `pingMedianMs`, `pingP90Ms`, `reasons` (human list).
  Penalties: drop -25, failed test -15, lost ping -5, minute down -10, ping spikes (p90 > 2.5x median and > 500 ms) -20.
- `lastFailedTest`, `lastFailedTestAt`: a failed speed test is logged as an event (`testFailed: true`), counts as a
  failed probe and triggers an immediate ping - it is often the first sign the connection broke.
- `widgetBytesToday`: data the widget itself used today.

## Good / bad thresholds (same as the widget's mouse-over texts, sources in docs/SOURCES.md in the repo)

- Ping (round trip): good < 100 ms, OK < 300, bad < 800, very bad above (ITU-T G.114: 150 ms one-way transparent,
  400 ms one-way unacceptable - https://www.itu.int/rec/T-REC-G.114).
- Download: bad < 3 Mbps, OK 3-5 (HD), good 5-15 (Full HD), very good 15+ (4K) (https://help.netflix.com/en/node/306).
- Wi-Fi RSSI: good >= -67 dBm, OK >= -70, weak >= -80, unusable below
  (https://www.metageek.com/training/resources/understanding-rssi/).

## Data budget (why it is cheap)

Passive traffic counters: 0 bytes. Ping: bare TCP handshake ~250 bytes/min (~0.36 MB/day).
Automatic speed burst (256 KB): at most every 3 h, also on mobile; never on a widget restart (last test time is read
from history); skipped when real traffic in the last hour already reached the last measured speed.
Manual: click / `speedwidget test`. Cap without manual tests: ~2.5 MB/day. Footer shows tests vs pings split.

## How to answer

1. Run `speedwidget status` and quote the numbers with their timestamps; for "is it stable?" quote `stability` with its reasons.
2. Outage question -> `speedwidget events 24` and give start, end, duration per event.
3. Need a fresh number -> `speedwidget test` (costs ~262 KB; fine on mobile).
4. Exit 2 -> the widget is not running: `launchctl kickstart -k gui/$(id -u)/io.github.franzenzenhofer.speedwidget`, or
   reinstall with `bash install.sh` in the cloned repo.

Wersje

W bazie nie ma innych skilli o nazwie connection-status.

Migawka bazy z 13.11.2026 · wersja paczki 19bc0b9268ae (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100mac-hotspot-data-saver
    Oszczędza transfer danych na Macu podłączonym do hotspotu telefonu lub Wi-Fi w hotelu, pokazuje zużycie i ustawia budżet.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.