CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prettier-formatter

Run Prettier formatting checks and automatically format files in the workspace using `npx prettier`.

Quality

78%

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

Quality

Content

86%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 tight, well-structured body for a simple skill: executable commands, clear triggers, and no wasted tokens. The only meaningful improvement would be a post-write verification step and a touch more operational detail (multi-file handling, interpreting check output).

DimensionReasoningScore

Conciseness

The body is 19 lean lines: a one-sentence purpose, two trigger bullets, and two commands with no explanations of concepts Claude already knows. Every section earns its place; nothing is padded, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Both steps give concrete, executable commands (`npx prettier --check <filepath>`, `npx prettier --write <filepath>`) with only a placeholder to substitute. Not 5 because there are minor gaps: no worked example with a real path, no handling of multiple files/globs, and no guidance on interpreting --check output.

4 / 5

Workflow Clarity

The sequence check → write → report is clear and unambiguous, and the upfront --check acts as a checkpoint before modifying files. Not 5 because there is no post-write verification or error-recovery guidance (e.g., re-run --check after --write), a minor validation gap for a file-modifying operation.

4 / 5

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no need for external references, and the content is well organized into purpose, 'When to Use', and 'Steps' sections. No references are cited and none are needed, so the simple-skill case for a 5 applies.

5 / 5

Total

18

/

20

Passed

Description

61%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 states a clear, concrete 'what' with the specific tool, but entirely omits any 'use when' trigger guidance, which caps completeness and limits trigger-term quality. Adding an explicit trigger clause with a few natural synonyms would lift it into the good-example range.

Suggestions

Append an explicit trigger clause, e.g. "Use when files fail Prettier checks in code review, before committing, or when the user mentions formatting, code style, or Prettier."

Add natural synonym terms users would say ("code style", "formatting issues", ".prettierrc") to broaden trigger coverage.

Optionally mention checking or formatting multiple changed files at once to round out capability coverage.

DimensionReasoningScore

Specificity

"Run Prettier formatting checks" and "automatically format files" name the domain and exactly two concrete actions, matching the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because only two actions are listed with no coverage of related capabilities (e.g., config resolution, output interpretation).

3 / 5

Completeness

The 'what' is clear (run checks, format files via npx prettier), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Natural terms a user would say are present — "Prettier", "formatting checks", "format files" — giving good keyword coverage, missing only a few variants like "code style" or ".prettierrc". Not 5 because it lacks synonym/extension-level comprehensiveness; not 3 because the primary natural phrases users actually say are all there.

4 / 5

Distinctiveness Conflict Risk

Naming Prettier explicitly carves out a clear niche, with only minor overlap risk against closely related linting/formatting skills. Not 5 because the distinctness rests on the tool name alone — the absence of distinct trigger phrases leaves slight ambiguity versus generic format/lint skills.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/prettier-formatter/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.