code-formatter
Execute automatically formats and validates code files using Prettier and other formatting tools. Use when users mention "format my code", "fix formatting", "apply code style", "check formatting", "make code consistent", or "clean up code formatting". Handles JavaScript, TypeScript, JSON, CSS, Markdown, and many other file types. Trigger with relevant phrases based on skill purpose.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill code-formatterOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with strong trigger term coverage and good completeness. The main weaknesses are the somewhat generic specificity (could list more concrete formatting actions) and the unnecessary filler phrase at the end ('Trigger with relevant phrases based on skill purpose') which adds no value and slightly undermines the otherwise clear description.
Suggestions
Remove the vague filler phrase 'Trigger with relevant phrases based on skill purpose' as it adds no useful information
Add more specific concrete actions like 'fix indentation', 'enforce consistent quotes', 'organize imports', or 'apply project style rules' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (code formatting) and mentions specific tools (Prettier) and actions (formats, validates), but doesn't list comprehensive concrete actions like 'fix indentation', 'enforce style rules', or 'auto-correct syntax'. | 2 / 3 |
Completeness | Clearly answers both what (formats and validates code using Prettier) and when (explicit 'Use when users mention...' clause with specific trigger phrases). The structure follows best practices. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'format my code', 'fix formatting', 'apply code style', 'check formatting', 'make code consistent', 'clean up code formatting'. Also lists supported file types which users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Fairly specific to code formatting with Prettier, but could potentially overlap with linting skills or general code cleanup tools. The phrase 'Trigger with relevant phrases based on skill purpose' at the end is vague filler that doesn't add distinctiveness. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a thin shell that defers nearly all useful content to external reference files. While the structure is reasonable, the main skill body lacks executable code examples, concrete command syntax, and sufficient detail to be immediately actionable. The instructions are abstract descriptions rather than specific guidance Claude can execute.
Suggestions
Add executable code examples showing actual Prettier commands with common flags (e.g., `npx prettier --check "src/**/*.{js,ts,json}"` and `npx prettier --write "src/**/*.{js,ts,json}"`)
Include a minimal .prettierrc example configuration that can be copy-pasted
Add explicit validation step: 'Run --check after --write to confirm all files pass'
Remove the empty 'Output' section and the generic overview sentence to improve conciseness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some unnecessary filler like 'This skill provides automated assistance for the described functionality' which adds no value. The prerequisites section explains things Claude would know. | 2 / 3 |
Actionability | No executable code examples provided - only vague command references in parentheses. Instructions describe what to do abstractly rather than providing copy-paste ready commands with actual syntax and flags. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack validation checkpoints. No feedback loop for when formatting fails or how to handle errors inline. The 'check then write' pattern is mentioned but not explicitly structured as validate-fix-retry. | 2 / 3 |
Progressive Disclosure | References external files appropriately (implementation.md, errors.md, examples.md) but the main content is too sparse - it defers almost everything to other files rather than providing a useful quick-start in the skill itself. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
- 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.