CtrlK
BlogDocsLog inGet started
Tessl Logo

syntax-text-handling

Use this skill when extracting or storing Biome AST/CST source text, working with any `SyntaxNode`, `SyntaxToken`, `TokenText`, quoted strings, token-relative ranges, or embedded-language attribute values, or diagnosing trivia, allocation, range, and temporary-borrow problems. Do not use for parser implementation or formatter comment placement.

74

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A high-quality, actionable body with lean prose, executable code, and a helpful review checklist. It lacks an explicit validation feedback loop and has no progressive file split, which cap two dimensions at 4.

Suggestions

Add an explicit numbered workflow with a validate→fix→retry loop (e.g., after editing, run the language quick test and only proceed when it passes) to lift workflow_clarity to 5.

Consider extracting the API reference table or per-framework embedded-language details into a bundled reference file linked from SKILL.md to deepen progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and efficient: no padding or explanations of basic concepts, assumes Claude's competence, and every section (table, code blocks, checklist) earns its place with non-obvious, decision-relevant detail.

5 / 5

Actionability

Fully executable Rust examples using real Biome APIs, plus a concrete API→result→use table and copy-paste-ready patterns for slicing, borrowing, and quote stripping that cover the common cases.

5 / 5

Workflow Clarity

A clear implicit sequence (Inspect Before Implementing → accessors/patterns → Review Checklist) with a verification checklist, but no explicit numbered validate→fix→retry feedback loop, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

Well-organized single-file overview with clear section headers and one-level-deep References pointing to real repo source paths; no bundle files are provided, and the inline content is appropriately sized rather than a monolithic wall, though nothing is progressively split into separate files.

4 / 5

Total

18

/

20

Passed

Description

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

A strong, specific description that clearly states both capability and trigger conditions with an explicit out-of-scope clause. Its only weakness is a reliance on API names over natural-language synonyms in some trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'extracting or storing Biome AST/CST source text', 'working with any SyntaxNode, SyntaxToken, TokenText', and 'diagnosing trivia, allocation, range, and temporary-borrow problems' — covering the domain comprehensively.

5 / 5

Completeness

Explicitly answers both what (Biome syntax text handling) and when ('Use this skill when extracting or storing... working with... diagnosing...') with concrete trigger phrases, plus an explicit exclusion ('Do not use for parser implementation or formatter comment placement').

5 / 5

Trigger Term Quality

Good keyword coverage with natural problem phrases ('diagnosing trivia, allocation, range, and temporary-borrow problems'), though several terms are API names (SyntaxNode, TokenText) rather than natural-user synonyms, leaving a few common phrasings uncovered.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Biome AST/CST source-text handling) with distinct triggers and an explicit 'Do not use for...' boundary clause, minimizing overlap with parser or formatter skills.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
biomejs/biome
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.