CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

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/charset/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 is a tight, well-structured overview for a simple single-purpose rule: concrete fix guidance with the exact meta tag and 1024-byte constraint, a clean section flow, and an appropriately deferred reference file. Only minor improvements are available — trimming the small amount of common-knowledge explanation and clarifying how to verify rendered output.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and sectioned, but two snippets explain what Claude already knows: the mojibake consequence sentence ("Missing or incorrect charset causes mojibake (garbled text), broken special characters...") and "UTF-8 supports all languages and special characters". This is anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') — tighter than anchor 3 but not the every-token-earns-its-place leanness of anchor 5.

4 / 5

Actionability

The Fix section gives copy-paste-ready guidance ("Add <meta charset="UTF-8"> as the first meta tag in the head") and Quick Reference supplies the concrete 1024-byte constraint, matching anchor 4's 'concrete code or commands with minor gaps'. It falls short of anchor 5 because the Check section states what to verify but not how (no command or method for locating the charset in rendered output vs. source), leaving a minor execution gap.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and the single action (ensure <meta charset="UTF-8"> is first in <head>) is unambiguous, but the Check and Code Review sections partially restate each other, and there is no verification step after the Fix. This sits between anchor 4 ('clear sequence with most checkpoints present') and the simple-skill 5; the mild redundancy keeps it at 4, noticeably above the midpoint.

4 / 5

Progressive Disclosure

The body is a concise overview with well-organized sections, and implementation details are split into a single, clearly signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`") that exists in the bundle. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split').

5 / 5

Total

17

/

20

Passed

Description

62%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.

The description has a correct structure — third person, explicit 'Use when...' trigger, and a differentiating what-statement about validating rendered markup rather than source abstractions. Its weaknesses are limited action specificity, absence of the natural keyword 'charset', and awkward trigger phrasing ('related to Declare UTF-8 character encoding') that dilutes both clarity and trigger matching.

Suggestions

Enumerate the skill's concrete actions in the 'what' clause, e.g. "Detects missing or misplaced <meta charset="UTF-8"> declarations, flags the offending template or route, and provides the corrected tag" — this would raise specificity from naming the domain to listing several specific actions.

Add the natural trigger term "charset" (and variants like "meta charset" or "garbled text"/"mojibake") — users asking for this rule say "charset" far more often than "Declare UTF-8 character encoding", and the term is currently absent.

Rewrite the convoluted trigger phrase "related to Declare UTF-8 character encoding" into a direct statement such as "Use when reviewing templates, rendered HTML, or shared components for the <meta charset> declaration" so both the what and when are explicit.

DimensionReasoningScore

Specificity

The description names the domain ("Declare UTF-8 character encoding") and two concrete actions ("reviewing templates, rendered HTML, or shared components" and "Validate the final browser-facing markup"), but coverage is not comprehensive — it never states what the skill actually does about the encoding (detect, fix, flag). This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') better than anchor 4, which expects several listed specific actions.

3 / 5

Completeness

Both halves are present: an explicit trigger ("Use when reviewing templates, rendered HTML, or shared components...") and a what-statement ("Validate the final browser-facing markup, not just the source framework abstraction"). However, the 'what' only becomes fully clear in combination with the 'when' clause, and the trigger phrasing "related to Declare UTF-8 character encoding" is convoluted rather than concrete — matching anchor 4 ('both present; when could be more explicit or specific') rather than anchor 5's clearly explicit dual answer.

4 / 5

Trigger Term Quality

Relevant keywords are present ("templates", "rendered HTML", "shared components", "UTF-8", "character encoding"), but the most natural term a user would say for this rule — "charset" — is absent, as are common variations like "meta charset", "garbled text", or "mojibake". This fits anchor 3 ('some relevant keywords but missing common variations or synonyms'); it is above anchor 2 (no generic-only terms) but below anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The UTF-8 charset niche is distinct with clear triggers, but "reviewing templates, rendered HTML, or shared components" is broad enough to overlap with general HTML/code-review skills. This is anchor 4 ('mostly distinct; minor overlap risk with closely related skills') — clearer scoping than anchor 3, but not the minimal-conflict niche of anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/charset/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.