CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa-static-scan

Search served JavaScript, templates, CSS, and source code for known bug classes (unchecked fetch responses, innerHTML with user data, removed focus outlines, unvalidated redirects, swallowed errors, secrets) and turn every hit into a targeted live test. Use early in any test run or code review.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Static Scan

Static hits are SOURCE evidence and count only as hints. Each one must become a live case before it can be called a bug.

Patterns to search (served code first, then repo)

PatternRegex ideaBug class
fetch result used without r.ok / res.ok checkawait fetch( with no .ok / status nearby before navigationSilent failure (A1)
innerHTML / dangerouslySetInnerHTML / v-html with datainnerHTML\s*=Stored XSS
Focus removedoutline:\s*none without :focus-visible replacementAccessibility (D7)
Redirect from queryget('next'), return_url, redirect= assigned to location or res.redirectOpen redirect
Swallowed errorscatch\s*\(\w*\)\s*\{\s*\}, continueOnFail, alwaysOutputData, never-errorSilent failure (A2)
Secretssk_live_, whsec_, AKIA, -----BEGIN, JWTs in bundles or source mapsSecret exposure
Lazy images in transformed or off-canvas containersloading="lazy" inside carousels or tracksImage never loads (D1)
Passive touch handlers that call preventDefaultonTouchMove + preventDefaultMobile gesture (D2)
Duplicate implementationsTwo handlers or endpoints for one actionDrift (E6)

Learned rules

Also run every rule in tools/harness/tester-static-rules.json (15 rules exported by the Fixer from verified fixes, G01–G15). Rules marked guard-ok: <rule> <reason> in the source are reviewed exceptions.

Procedure

  1. Fetch every route's served HTML/JS (and source maps if public), plus the repo at the deployed commit.
  2. Run the patterns and record file:line or route.
  3. For each hit, write a live case ID in the matrix.

Exit criteria

Every hit is either converted into a live case or dismissed with a written reason.

Repository

itsablabla/qa-bug-agent-skills

Path

skills/qa-static-scan/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.