CtrlK
BlogDocsLog inGet started
Tessl Logo

html-injection-testing

This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test content injection vulnerabilities". It provides comprehensive HTML injection attack techniques and testing methodologies.

65

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/html-injection-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable with extensive executable examples, but it is verbose and redundant, lacks a true sequenced workflow with validation checkpoints, and is a monolithic wall of text with no progressive disclosure into separate reference files.

Suggestions

Collapse the duplicated Quick Reference payload/encoding tables into the inline code blocks they repeat, and trim explanations of basic concepts (what HTML injection is, HTML-vs-XSS differences) that Claude already knows.

Restructure the Phases into an ordered testing workflow with explicit validation steps — e.g., after batch fuzzing in Phase 9, require manually verifying each flagged reflection before reporting it as a finding.

Move the payload catalogs (Phases 3, 4, 8) and the remediation guide (Phase 10) into separate reference files (e.g., references/payloads.md, references/remediation.md) and keep SKILL.md as a concise overview that links to them.

DimensionReasoningScore

Conciseness

The body is substantive but padded: it restates basics Claude already knows ("HTML injection occurs when user input is reflected... without proper sanitization") and the Quick Reference tables duplicate payloads already shown in Phases 3 and 8.

2 / 3

Actionability

Provides copy-paste-ready executable guidance throughout: curl probes, a runnable Python fuzzing script, concrete Burp/ZAP steps, and PHP/Python/JavaScript remediation code.

3 / 3

Workflow Clarity

The ten "Phases" read as a topical catalog rather than a sequenced operational workflow, and Phase 9 (automated batch fuzzing) lacks the validation/feedback checkpoints that the rubric requires for batch operations, capping this at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the entire ~490-line skill is a single monolithic SKILL.md; payload catalogs and remediation guidance that should live in one-level-deep reference files are inlined, though sections are reasonably organized.

2 / 3

Total

9

/

12

Passed

Description

90%

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

The description cleanly states what the skill does and when to use it, with strong, natural trigger phrases and a distinct niche. Its only weakness is vague specificity — "comprehensive attack techniques and testing methodologies" lists categories rather than concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain and broad categories ("HTML injection attack techniques and testing methodologies") but relies on the vague qualifier "comprehensive" rather than enumerating multiple concrete actions.

2 / 3

Completeness

Explicitly answers both what ("provides comprehensive HTML injection attack techniques") and when ("This skill should be used when the user asks to...") with an explicit trigger clause.

3 / 3

Trigger Term Quality

Five quoted natural phrases ("test for HTML injection", "inject HTML into web pages", "deface web applications", etc.) give good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (HTML injection) with differentiated triggers ("deface web applications", "inject HTML into web pages") that are unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zebbern/claude-code-guide
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.