Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/charset
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.
Passed 21 of 22 test cases with the skill, and 20 of 22 without it.
2 fixed19 passed either way0 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are rendering HTML templates via Express EJS views. Write the `<head>` block template snippet ensuring standard UTF-8 charset compliance.
| Checked | Without skill | With skill |
|---|---|---|
| Includes <meta charset="UTF-8"> as the very first line inside <head>. | Missed | Passed |
The instructions your model reads when the skill loads.
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 Verify that this HTML document declares UTF-8 character encoding in the head section and that it's positioned early in the document.
Add 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.
test cases passed, vs 20 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.