html-structure-validate
Validate HTML Structure Before Publishing
AI-generated HTML often misses required structure and breaks downstream publishing. This skill checks HTML5 structure and records clear validation results.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "html-structure-validate" from https://skillstore.io/skills/abejitsu-html-structure-validate.md and its manifest at https://skillstore.io/api/skills/abejitsu-html-structure-validate/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "html-structure-validate". A generated page is missing a closing body tag.
Expected outcome:
The result fails. The report identifies the missing closing tag, marks the structure gate as blocked, and recommends repairing the page.
Using "html-structure-validate". A generated page has valid structure but starts with a second-level heading.
Expected outcome:
The result passes with a warning. The report notes the heading hierarchy issue and allows the pipeline to continue unless strict mode is active.
Using "html-structure-validate". A chapter pipeline needs validation before pages are merged.
Expected outcome:
The workflow validates each page, saves a report beside the page artifacts, and stops processing when structural errors appear.
Security Audit
SafeThe static alerts are false positives from Markdown inline code, fenced examples, sample HTML, and project-relative paths. No prompt injection, credential access, network activity, malicious filesystem intent, or hidden command execution was found in SKILL.md.
Risk Factors
⚙️ External commands (55)
📁 Filesystem access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/abejitsu-html-structure-validate/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/abejitsu-html-structure-validate?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/abejitsu-html-structure-validate?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/abejitsu-html-structure-validate/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/abejitsu-html-structure-validate.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
AbeJitsu. (2026). html-structure-validate security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/abejitsu-html-structure-validate/audits/9BibTeX citation
@techreport{abejitsu-abejitsu-html-structure-validate-2026,
author = {AbeJitsu},
title = {html-structure-validate security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/abejitsu-html-structure-validate/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "html-structure-validate security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "AbeJitsu"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/abejitsu-html-structure-validate/audits/9"
identifiers:
- type: other
value: "skillstore:abejitsu-html-structure-validate:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Validate generated web pages
Check AI-generated HTML pages before they move into consolidation, review, or publishing steps.
Enforce publishing quality gates
Stop a chapter or page pipeline when required HTML structure is missing or malformed.
Create repeatable QA reports
Record pass, fail, warning, and summary details for each generated page under review.
Try These Prompts
Validate the generated HTML file at [path]. Check structure, required tags, and tag closure. Summarize errors and warnings clearly.
Review the structure validation result for [page]. Explain each blocking error, likely cause, and the smallest safe HTML fix.
Run structure validation for [chapter] in strict mode. Treat warnings as failures and prepare a concise gate decision.
Design a structure validation step for the generated HTML pipeline. Include inputs, report location, failure behavior, and retry guidance.
Best Practices
- Run this validation immediately after HTML generation and before semantic review.
- Keep the validator script versioned with the project that uses this skill.
- Treat errors as blockers and review warnings before final publishing.
Avoid
- Do not treat successful browser rendering as proof of valid structure.
- Do not suppress failed validation without saving a report and reviewing the root cause.
- Do not reuse project-specific class checks in unrelated templates without updating the rules.