CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-mobile-security-xss-scan

Detect and remediate XSS risks in React, Vue, Angular, and browser JavaScript. Use when inspecting injection sinks, untrusted markup, sanitization, or frontend security checks.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/frontend-mobile-security-xss-scan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers genuinely actionable security content — detection patterns, framework-specific checks, secure alternatives, tooling commands, and a prevention checklist — but is undermined by boilerplate filler sections, a long re-implementation of knowledge Claude already has, and an all-in-one monolithic layout with no bundle files. The strongest fix is trimming the filler, moving the scanner implementation to scripts/, and adding an explicit verify-findings step.

Suggestions

Remove the circular 'Use this skill when', 'Do not use', 'Context', and 'Requirements' filler sections; the frontmatter description already carries trigger and scope information.

Replace the ~150-line scanner class with a compact vulnerable-pattern table (or move the implementation to a scripts/xss-scanner.ts bundle file), since Claude already knows these XSS patterns — keep the prevention checklist and secure-pattern examples inline.

Add an explicit workflow step for validating findings (e.g., confirm user-control reachability and filter false positives) between detection and report generation, since the naive indicator matching ('props', 'state', 'query') will over-flag.

DimensionReasoningScore

Conciseness

The body includes circular filler ("Working on xss vulnerability scanner for frontend code tasks or workflows", "Take the requirements, target, and scope from the user's request") and ~150 lines of TypeScript re-implementing XSS pattern detection (innerHTML, v-html, dangerouslySetInnerHTML) that Claude already knows. The core checklist and secure-pattern content is dense and useful, so it is above anchor 2's noticeably-verbose profile but clearly below anchor 4's efficient one.

3 / 5

Actionability

Mostly executable guidance: concrete TypeScript scanner classes, runnable commands ("semgrep --config=p/xss --json", eslint-plugin-security install), and copy-paste secure-pattern snippets. Minor gaps hold it below anchor 5: detectEventHandlerIssues is called but never defined, findJavaScriptFiles is missing, fs is unimported, and "node xss-scanner.js --path=src" references a file that does not exist in the bundle.

4 / 5

Workflow Clarity

Numbered sections 1-6 (detection, framework-specific, secure examples, tooling, reporting, prevention) plus an Output Format list give a topical sequence, but there is no ordered run-through of a scanning engagement and no validation checkpoints such as verifying findings or filtering false positives. Scanning is read-only, so no destructive-operation cap applies; this matches anchor 3 (sequence present, checkpoints missing or implicit).

3 / 5

Progressive Disclosure

The skill is a single ~300-line file with no references/, scripts/, or assets/ bundle; ~200 lines of scanner and report-generator code are inlined in SKILL.md where they belong in a scripts/ file, with the checklist kept inline. Section headers provide real structure, so it fits anchor 3 (structure present but content that should be separate is inline) rather than anchor 2's unstructured wall; it cannot reach anchor 4-5 since nothing is split out.

3 / 5

Total

13

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concise, third-person, with a clear what (detect and remediate XSS) and an explicit "Use when" clause containing concrete triggers. The main gaps are a couple of missing natural trigger variations and slightly broad phrases like "frontend security checks" that could overlap general security-review skills.

DimensionReasoningScore

Specificity

"Detect and remediate XSS risks" names two concrete actions covering the full find-to-fix lifecycle, scoped to "React, Vue, Angular, and browser JavaScript". It sits above anchor 3 (only 1-2 actions, not comprehensive) because detect+remediate fully spans the skill's domain, but below anchor 5, which expects a broader list of specific actions.

4 / 5

Completeness

Explicitly answers both questions: the what is "Detect and remediate XSS risks in React, Vue, Angular, and browser JavaScript" and the when is a concrete "Use when inspecting injection sinks, untrusted markup, sanitization, or frontend security checks" clause. This matches anchor 5 (clear what AND when with concrete trigger phrases), not anchor 4 where the when is only loosely specified.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "XSS", "React, Vue, Angular", "sanitization", "browser JavaScript"; "injection sinks" leans technical. A few natural variations are missing ("cross-site scripting" spelled out, "escape HTML", "DOMPurify"), placing it just below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The XSS-in-frontend-frameworks niche is clearly distinguishable with distinct triggers, but "frontend security checks" and "sanitization" are broad enough to overlap a general security-review or code-audit skill. Minor overlap risk with closely related skills matches anchor 4 rather than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/frontend-mobile-security-xss-scan/SKILL.md

Reviewed

Table of Contents

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.