klyo_game_diagnostics

shallow

pl.klyo/games · Verify this server

Eyes inside the game: for a package in the waiting room (`upload_id`) or a game in the catalogue (`slug`) it returns the files the game asked for that are missing from the package, and the JavaScript errors from the preview in the browser, in the order they happened. Also: the package check result (size, third-party ads, malicious code, missing klyo kit), ready conclusions in `wnioski`, and `dopasowanie`: the fit measurement from publishing on four screens (phone portrait and landscape with touch, tablet, desktop): `uwagi[]` with the codes `przewija` (page scrolls) | `maly_ekran` (screen too small) | `maly_tekst` (text too small) | `ciezka` (too heavy) | `dlugie_wczytanie` (long load) | `niski_fps` (low frame rate) | `male_cele_dotyku` (small touch targets) | `przycisk_bez_nazwy` (button without a name), `dotyk_nasluch` and `zrzut` thumbnails; `null` = the game has not been measured yet (a measurement starts with every version release). Read-only. YOUR BROWSER IS THE EYE HERE: we do not keep a browser farm and do not need one. Open the preview address on YOUR side (Playwright, Chrome, a phone), really play (click, swipe, wait for the second level) and our sensor on that page reports everything that crashed. Then ask with this tool. Order: open, play, ask; the other way round gives an empty answer, because errors are collected only once the game runs. Add `?s=<your marker>` to the address and pass `sesja` with the same value to get only the errors from your own run. NO BROWSER (a conversation in claude.ai or ChatGPT)? Pass `zmierz: true` for a package or a waiting version: we open the preview for you, collect errors and thumbnails of four screens (`zrzut_adres`); one measurement at a time per account, 6 per hour. Add `pelny: true` for the production profile (a slow phone and every declared language). A game with a waiting version (workshop) shows its files, errors and premium review (`przeglad`). Examples: • Why does my game show a white screen? • Check the errors in the package preview • What is missing from the lantern-thief package?

100.0/100

1 trials · measured 14 days ago

klyo_game_diagnostics scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against pl.klyo/games, measured 23 Sept 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-09-23100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: klyo_game_diagnostics
[![Vouch score](https://vouch.tools/api/tools/b296f677-38cf-473f-bd9e-467b47fc5b48/badge.svg)](https://vouch.tools/tools/b296f677-38cf-473f-bd9e-467b47fc5b48)
klyo_game_diagnostics — Vouch