Fingerprint Failure Triage

Triage a liarjs fingerprint report by attributing each failing check to the part of the setup that produced it: the launch configuration, the page-modifying layer, the network path, or the base machine image. It's the difference between a score of 62 and a list of owners. The bundled reference covers all 40 check ids, and the sharpest tips are the ones that save wasted debugging, like noting that `--remote-debugging-port=0` trips the `webdriver` check while a fixed port does not, and that `worker-consistency` failing alone means a patch reached the main thread but not Web Workers. The useful habit here is re-scanning one change at a time, since several ids move together. It explains measurements rather than prescribing fixes, and it won't forecast how a real site will treat the browser.

skills.sh installs: 119K
GitHub stars: 5
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add liarjsdev/liarjs-skills --skill fingerprint-failure-triage --agent claude-code

Installs into .claude/skills of the current project.

Files

Triage a fingerprint report

A score is a summary; the check ids are the finding. The job here is attribution: for each failing id, say what it measures and which component of the setup produced that signal. That turns a number into an owner list.

This skill explains measurements. What to do about a given finding depends on what the browser is for, and that call belongs to whoever operates it.