Review the HTML delivered to browsers for a correct UTF-8 character encoding declaration. Find missing or misplaced charset tags in templates and rendered pages, then position the declaration early to help prevent garbled multilingual text.
Use when reviewing templates, rendered HTML, or shared components related to Declare UTF-8 character encoding. Validate the final browser-facing markup, not just the source framework abstraction.
This skill checks whether HTML declares UTF-8 character encoding and fixes missing or misplaced declarations. UTF-8 is an encoding used for multilingual text and special characters. It checks that <meta charset="UTF-8"> appears near the beginning of <head> and within the document’s first 1024 bytes. If the declaration is missing, it adds it as the first meta tag in <head>.
Use it to investigate pages with garbled Japanese text or symbols, or to check a multilingual site before publication. It also helps confirm that encoding declarations are output correctly after changes to templates or shared components. For server-generated HTML, the review identifies the specific elements or page routes with problems.
Check the final HTML delivered to the browser. A declaration in framework settings or a source template is not enough: verify its position and content in the actual output.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Missing or incorrect charset causes mojibake (garbled text), broken special characters, and security vulnerabilities from character encoding attacks.
<meta charset="UTF-8"> as the first element in <head>Verify that this HTML document declares UTF-8 character encoding in the head section and that it's positioned early in the document.
Add <meta charset="UTF-8"> as the first meta tag in the head section of the HTML document.
Explain why UTF-8 character encoding is essential for international content support and preventing character display issues.
Review templates, server-rendered HTML, and shared components that output markup related to Declare UTF-8 character encoding. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.