SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Audit UI artifacts with frontclippy and summarize findings, including capture, analysis, and SARIF output.
Run frontclippy against a local HTML file, live URL, snapshot JSON, suite, or manifest and summarize the findings. Use when the user asks to audit a UI, inspect frontclippy output, emit SARIF, or run capture plus analysis.
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
Original instructions from the publisher’s SKILL.md
# frontclippy-audit Use this in the `frontclippy` repo when the user wants a real audit run instead of a theoretical explanation. ## Workflow 1. Work from the repo root. 2. Choose the narrowest command for the artifact the user provided: - Local HTML file or live URL: ```bash cargo run -p frontclippy-cli -- check <target> ``` - Behavioral or keyboard-flow audit: ```bash cargo run -p frontclippy-cli -- trace-check <target> ``` - Stress or matrix audit: ```bash cargo run -p frontclippy-cli -- matrix-check <target> ``` - Snapshot JSON: ```bash cargo run -p frontclippy-cli -- analyze <snapshot.json> ``` - Related snapshots: ```bash cargo run -p frontclippy-cli -- suite-analyze <snapshot-a.json> <snapshot-b.json> [...] ``` - Manifest: ```bash cargo run -p frontclippy-cli -- manifest-check <manifest.toml> ``` 3. Add `--format sarif` when the user wants CI or code-scanning output. 4. Add `--config`, `--baseline`, `--suppressions`, or `--write-baseline` when review state matters. 5. If no target is provided, use `fixtures/frontclippy.manifest.toml` for a broad demo or `fixtures/checkout-chaos.html` for a single-surface demo. ## Response Pattern Return: 1. the exact command that ran 2. the finding count and highest severity 3. whether findings were configured, suppressed, or baselined 4. the most relevant next step
Files included alongside SKILL.md in the publisher’s repository.