CtrlK
BlogDocsLog inGet started
Tessl Logo

hygiene

Use when making code changes to ensure they pass VS Code's hygiene checks. Covers the pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint. Run the hygiene check before declaring work complete.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, actionable skill body that gives exact commands, a clear pre-completion checkpoint, and well-structured sections without any redundant explanation. It is an exemplar of a simple, single-purpose skill done well.

DimensionReasoningScore

Conciseness

Lean body with no concepts Claude already knows; every line earns its place — runnable commands and a tight bullet list of checks with no padding.

3 / 3

Actionability

Provides copy-paste-ready commands ('npm run precommit', 'node --experimental-strip-types build/hygiene.ts path/to/file.ts') and concrete rules with suppression directives, fully executable.

3 / 3

Workflow Clarity

Single-purpose skill with an unambiguous action and an explicit 'run before declaring work complete' checkpoint; the simple-skill note allows 3 without a multi-step loop, and this is not a destructive/batch operation.

3 / 3

Progressive Disclosure

Under 50 lines with well-organized sections ('Running the hygiene check', 'What it checks') and no need for external references, matching the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

100%

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 tight, well-constructed description that states a natural trigger, enumerates concrete capabilities, and carves out a distinct niche without padding. It cleanly answers both 'what' and 'when'.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'pre-commit hook, unicode restrictions, string quoting rules, copyright headers, indentation, formatting, ESLint, and stylelint' — matching the comprehensive-actions anchor, not the partial level 2.

3 / 3

Completeness

Explicitly answers both: what it covers ('Covers the pre-commit hook...') and when to use it ('Use when making code changes...'), satisfying the explicit-trigger anchor.

3 / 3

Trigger Term Quality

Natural triggers like 'making code changes', 'hygiene checks', and 'pre-commit' are terms a user would plausibly say, giving good coverage rather than just jargon.

3 / 3

Distinctiveness Conflict Risk

The VS Code hygiene/pre-commit niche with ESLint/stylelint triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
posit-dev/positron
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.