Skills fingerprint-failure-triage

📦

fingerprint-failure-triage

Name: fingerprint-failure-triage
Author: liarjsdev

Content revision r1 Medium Risk ⚙️ External commands🌐 Network access

Diagnose Browser Fingerprint Failures

Fingerprint scores often hide which component caused each failure. This skill maps liarjs checks to launch, page, network, or machine sources.

Supports: Claude Codex Code(CC)

📊 66 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "fingerprint-failure-triage" from https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage.md and its manifest at https://skillstore.io/api/skills/liarjsdev-fingerprint-failure-triage/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/liarjsdev-fingerprint-failure-triage.md Signed manifest GET /api/skills/liarjsdev-fingerprint-failure-triage/manifest Signed lockfile GET /api/skills/liarjsdev-fingerprint-failure-triage/lockfile

Test it

Using "fingerprint-failure-triage". The report fails worker-consistency while main-thread identity checks pass.

Expected outcome:

Source: page-modifying layer. The change reached the main thread but not the separate Web Worker realm. Assign this to the identity modification owner.

Using "fingerprint-failure-triage". A proxied datacenter run fails tz but passes browser timezone consistency checks.

Expected outcome:

Source: network path. The exit IP region differs from the browser timezone. This is often inherent to proxied datacenter environments.

Using "fingerprint-failure-triage". The new image fails gpu-age, webgpu-empty, and colordepth together.

Expected outcome:

Source: machine image. The failures point to old or software rendering, missing WebGPU adapter details, and a virtual display.

Security Audit

Medium Risk

v1 • 8/8/2026 Open versioned report

Two snippets are genuine npx commands that can download and execute a community package. The remaining backtick, reconnaissance, and URL matches are documentation false positives. The skill also provides a specific technique and iterative workflow that can help reduce browser automation detection.

Files scanned

173

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (1)

Medium

SKILL.md:28-31 SKILL.md:55-57

Automation Detection Evasion Guidance

The skill recommends iterative rescanning and explains that a fixed reserved debugging port avoids the webdriver signal. This can help conceal browser automation.

The cited lines provide both an iterative optimization workflow and a specific configuration distinction that reduces an automation signal.

Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

Medium

SKILL.md:19

Ruby/shell backtick execution

1. **Get the full result, not just the failures.** `npx liarjs@0.3 --all --json scan.json` prints

This is an actual npx command that may download and execute the community liarjs package. The command is legitimate for the skill, but it creates external code execution and supply-chain exposure.

Medium

SKILL.md:30

Ruby/shell backtick execution

5. **Compare rather than re-score:** `npx liarjs@0.3 diff before.json after.json` prints only the

This is an actual npx command that executes the liarjs package against local report files. Its intended use is legitimate, but package execution introduces external command and supply-chain risk.

Risk Factors

⚙️ External commands (19)

SKILL.md:19 SKILL.md:22 SKILL.md:26 SKILL.md:30 SKILL.md:39 SKILL.md:40 SKILL.md:41 SKILL.md:42 SKILL.md:46 SKILL.md:48 SKILL.md:53 SKILL.md:55 SKILL.md:58 SKILL.md:59 SKILL.md:60 SKILL.md:61 SKILL.md:63 SKILL.md:72 SKILL.md:73

🌐 Network access (1)

SKILL.md:75

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/liarjsdev-fingerprint-failure-triage/security.svg)](https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/liarjsdev-fingerprint-failure-triage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/liarjsdev-fingerprint-failure-triage.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

liarjsdev. (2026). fingerprint-failure-triage security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage/audits/1

BibTeX citation

@techreport{liarjsdev-liarjsdev-fingerprint-failure-triage-2026,
  author = {liarjsdev},
  title = {fingerprint-failure-triage security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "fingerprint-failure-triage security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "liarjsdev"
date-released: "2026-08-08"
url: "https://skillstore.io/skills/liarjsdev-fingerprint-failure-triage/audits/1"
identifiers:
  - type: other
    value: "skillstore:liarjsdev-fingerprint-failure-triage:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Triage a low fingerprint score

Group failed checks by likely source and identify the responsible component.

Explain one failed check

Translate a check identifier into its measurement, meaning, and likely owner.

Compare build results

Review changed check statuses after one controlled environment update.

Try These Prompts

Explain one check

Explain the liarjs check [check id]. State what it measures, the likely source, and whether the result is expected.

Group report failures

Review this liarjs report: [report]. Group failures by source, identify owners, and mark failures inherent to the environment.

Compare two scans

Compare these before and after liarjs results: [before] [after]. Explain changed checks and attribute each change to a component.

Build an investigation sequence

Analyze this complete liarjs result: [report]. Prioritize shared root causes, use passing checks as evidence, and separate inherent findings from defects.

Best Practices

Provide the full report because passing checks help distinguish possible sources.
Change one environment variable at a time before rescanning.
Describe improved results as removed contradictions, not guaranteed site acceptance.

Avoid

Do not investigate only the total score without reviewing check identifiers.
Do not treat several failures with one source as unrelated defects.
Do not assume every headless or datacenter failure requires remediation.

Frequently Asked Questions

What input does this skill need?

Provide a complete liarjs report, two reports for comparison, or one check identifier.

Can it explain a single check identifier?

Yes. It can describe the measurement, likely source, and practical meaning for any documented identifier.

Does it fix fingerprint failures?

No. It attributes failures and supports investigation, while configuration decisions remain with the browser operator.

Does a higher score guarantee website acceptance?

No. Websites may also evaluate IP reputation, account history, and behavior.

Why include passing checks?

Passing checks can eliminate competing explanations for a failure and improve source attribution.

Can it analyze offline scans?

Yes, but offline scans omit checks that depend on network and edge observations.

Developer Details

Author

liarjsdev

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/liarjsdev/liarjs-skills/tree/4068c79209753c74f895a4a5a6d117fcde8d94d1/skills/fingerprint-failure-triage

Ref

9939e94735a710f16446f189eea126372136575b

Maintenance freshness

8/9/2026

Usage

0 downloads · 0 views

File structure

📁 references/

📄 interpreting-checks.md

📄 SKILL.md