CtrlK
BlogDocsLog inGet started
Tessl Logo

devtools-unicode-escaping

Guidelines for escaping strings and handling user-controlled data in DevTools to prevent layout bleed-through, XSS, and security issues.

62

Quality

72%

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 ./.agents/skills/devtools-unicode-escaping/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 well-structured, actionable reference covering the two escaping functions, the auto-escaping Lit wrapper, and manual DOM contexts. Minor gains are possible by tightening behavior prose and adding a concrete code snippet for §2.

Suggestions

Replace the §2 'Used automatically by the global Lit template wrapper' line with a small code snippet so every section has executable guidance.

Tighten the 'Behavior' bullets, which partly restate the heading intent, to remove minor verbosity.

Consider a short decision table mapping rendering context → recommended function to make the workflow even more scannable.

DimensionReasoningScore

Conciseness

Lean and assumes competence — no padding about what Unicode or escaping is — with only minor restatement of behavior in the 'Behavior' bullets that could be trimmed.

4 / 5

Actionability

Provides concrete executable TypeScript with named module paths and an explicit directives rule, though the §2 example lacks code ('Used automatically…') and the directive example is a fragment.

4 / 5

Workflow Clarity

Organized into four clearly sequenced scenarios with 'use X when… / use Y when…' decision guidance; not a destructive/batch workflow so the cap-3 does not apply, and validation checkpoints are not strictly required here.

4 / 5

Progressive Disclosure

A single tightly organized, self-contained file with clear numbered sections and subsections; no bundle files exist and none are needed, which satisfies the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

66%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 is specific and well-scoped to DevTools Unicode escaping, but lacks an explicit 'when to use this' trigger clause. Adding a 'Use when…' sentence with natural user-facing triggers would lift completeness.

Suggestions

Add an explicit 'Use when…' clause naming when to invoke the skill (e.g. when rendering inspected/untrusted strings in DevTools UI, console messages, or DOM tree nodes).

Reframe the opening around action verbs ('Escapes strings and handles user-controlled data…') rather than the noun phrase 'Guidelines for…'.

Include natural user-facing synonyms such as 'sanitizing', 'untrusted input', or 'rendering' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the DevTools domain and several concrete actions ('escaping strings', 'handling user-controlled data', 'prevent layout bleed-through, XSS, and security issues'), but the 'Guidelines for…' framing and absence of enumerated functions leave minor coverage gaps.

4 / 5

Completeness

Provides a clear 'what' but no 'Use when…' or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms like 'escaping strings', 'user-controlled data', 'XSS', 'security issues', and 'DevTools', though some are internal jargon and common synonyms (e.g. 'sanitizing', 'untrusted input') are missing.

4 / 5

Distinctiveness Conflict Risk

DevTools-specific niche with distinctive terms ('layout bleed-through', RTL leaks) keeps it mostly distinct, with only minor overlap with generic XSS/security skills.

4 / 5

Total

15

/

20

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
ChromeDevTools/devtools-frontend
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.