skills.rest
oxie
oxieCOMMUNITY
Explore all skills by this author →
GitHub

impeccable-check

Scan selected source and static HTML files for mechanical UI anti-pattern findings.

Updated Sep 6, 2026
Search Tags:#static analysis#code review#html#frontend#css#ui anti-patterns#sandboxed scan
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill impeccable-check-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impeccable-check
Source: https://github.com/oxie/prime-agent-skills/tree/main/impeccable-check
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill impeccable-check-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewing frontend source for recurring UI anti-patterns by hand is slow and inconsistent. This Skill runs a pinned, read-only Impeccable detector over explicitly selected source or static HTML files and returns structured, hash-verified findings with rule IDs, locations, and coverage data. ## Core Features & Use Cases - Bounded source scanning: Checks 1-16 explicitly selected UTF-8 files (CSS, JS/TS, Vue, Svelte, Astro, HTML) against the upstream Impeccable rule set, with per-file size and total limits. - Sandboxed execution: Runs the hash-pinned native engine under Linux Landlock ABI 4 and seccomp with no network, no process creation, and read-only input snapshots. - Structured JSON evidence: Reports rule IDs, files, snippets, source hashes, executed coverage events, and primary/advisory counts with clear exit codes (0 clean, 2 findings, 1 error). - Use Case: Before shipping a landing page, ask the agent to run an Impeccable source check on src/page.html and its linked stylesheet to surface heuristic style observations, then reconcile them against the product brief. ## Quick Start Ask the agent to run an Impeccable source check on a specific HTML file and its linked CSS file within the current Git project root.

Frequently Asked Questions about impeccable-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an Impeccable source check on my frontend files?▼

Invoke the skill with an absolute canonical Git root and 1-16 explicitly selected files, for example an HTML page plus its linked CSS. The script runs the pinned engine and returns JSON findings with rule IDs, files, and snippets.

What file types does the Impeccable source scan support?▼

Supported extensions are CSS, SCSS, SASS, LESS, JS, JSX, TS, TSX, MJS, CJS, Vue, Svelte, Astro, HTML, and HTM. Files must be UTF-8, non-hidden, at most 256 KiB each and 2 MiB total.

Does impeccable-check support rendered or browser-based scanning?▼

No. The rendered mode is unsupported and refuses before any HTTP or browser launch because the host cannot provide the required Chromium namespace sandbox. Browser-assisted review must use the separate Browser Check skill.

What do the exit codes 0, 1, and 2 mean?▼

Exit 0 means a complete supported scan with no primary findings. Exit 2 means primary heuristic findings exist. Exit 1 signals an operational error or incomplete scan and must never be treated as a clean result.

Why does a scan fail on HTML with external stylesheets or @import?▼

Static mode requires self-contained CSS: external, absolute, or encoded stylesheet links, base tags, and CSS @import are refused rather than silently losing coverage. Every linked stylesheet must be a relative CSS file explicitly selected with --file.

Are Impeccable findings proof of design defects?▼

No. Findings are heuristic observations, not objective defects, accessibility certificates, or authorship evidence. Upstream slop-category findings are downgraded to advisory and all results should be reconciled against the actual product brief.

Related Skills

Explore More Software Engineering Skills→
legioncodeinclegioncodeinc
84

impeccable-stinger

Operates the Impeccable design system to build and audit frontend UI through a four-phase loop.

Official
Advanced
JYeswakJYeswak

sheets-reconciliation

Compare a sheet range against its source of truth and report mismatches with cell-level citations.

Community
Intermediate
izzoaizzoa
22

ss-verify

Inspect rendered browser screenshots for visual defects in layout, typography, contrast, and spacing.

Community
Advanced
ehtbantonehtbanton

lint-staged-config-generator

Generate lint-staged configuration files for multiple languages and linters.

Community
Basic