Fingerprint Failure Triage
Attribute each failing fingerprint check to the component that produced it — config, page layer, network, or image
- What
- Attribute each failing fingerprint check to the component that produced it — config, page layer, network, or image
- Cost
- Free
- Needs
- a liarjs fingerprint scan saved as JSON (from the fingerprint-ci-gate or browser-fingerprint-audit skills)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a diagnostic skill for your own automation harnesses: feed it a liarjs fingerprint report and it attributes each failing check id (webdriver, worker-consistency, gpu-triad, native-integrity, tz, …) to the component that produced the signal — launch configuration, page-modifying layer, network path, or machine image — distinguishing failures inherent to headless or datacenter environments from real regressions. Turns a score into an owner list. By @liarjsdev, listed here with credit to its creator. Transparency: measurement only, for your own harnesses — it explains what was measured; remediation decisions belong to whoever operates the browser. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a liarjs fingerprint scan saved as JSON (from the fingerprint-ci-gate or browser-fingerprint-audit skills) Install "Fingerprint Failure Triage" for me. Attribute each failing fingerprint check to the component that produced it — config, page layer, network, or image Repository: https://github.com/liarjsdev/liarjs-skills/blob/main/skills/fingerprint-failure-triage/SKILL.md 1. Fetch the SKILL.md file for the liarjsdev-fingerprint-failure-triage skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "liarjsdev-fingerprint-failure-triage". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.