CtrlK
BlogDocsLog inGet started
Tessl Logo

website-maintainer

Use this skill when working on the Repomix documentation website in `website/` directory, including VitePress configuration, multi-language content, or translation workflows.

64

Quality

76%

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 ./website/.claude/skills/website-maintainer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 lean, highly organized instruction-only skill body with actionable file-level guidance and no token waste. Its single notable weakness is the absence of validation steps in the multi-file 'Adding New Language' workflow, which leaves the most fragile operation without a verification checkpoint.

Suggestions

Add a verification step to the 'Adding New Language' workflow, e.g. 'Run the dev build and confirm the new locale renders in the language dropdown and search works before committing'.

Name the template file explicitly in step 1 ('copy `config/configEn.ts`…') and show the minimal shape of the search-config addition in `configShard.ts` to close the actionability gaps.

DimensionReasoningScore

Conciseness

Every section is lean and earns its tokens: an ASCII structure tree, terse numbered steps, and short bullets. There is no explanation of concepts Claude already knows and no padding, matching the 5 anchor ('every token earns its place').

5 / 5

Actionability

Guidance is concrete and executable ('Create `config/configXx.ts` based on existing', 'Import and add to `locales` in `config.ts`', 'Edit `config/config[Lang].ts` → `themeConfig.sidebar`'). Minor gaps keep it from 5: 'based on existing' does not name the template config, and the search-config addition in configShard.ts is mentioned without a snippet or shape.

4 / 5

Workflow Clarity

The 'Adding New Language' section is a clearly sequenced 4-step list, but there are no validation or verification checkpoints anywhere — no step to build/dev-run the site to confirm the locale, nav, and search load correctly. Steps listed with validation absent matches the 3 anchor; not 4 because checkpoints are missing entirely rather than minor.

3 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references (none are provided in references/, scripts/, or assets/), and is organized into four well-labeled sections that make navigation trivial. Per the simple-skill exception, well-organized sections alone warrant a 5.

5 / 5

Total

17

/

20

Passed

Description

73%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, concise description with an explicit 'Use when' trigger, good natural keywords, and a clearly distinct niche. Its main weakness is that it defines scope (work areas) rather than concrete actions, leaving the 'what' slightly under-specified.

Suggestions

State 1-2 concrete capabilities alongside the scope, e.g. 'Adds new language locales, edits navigation/sidebars, and updates translated content' — this would raise specificity from naming the domain to listing actions.

Add a couple of natural synonyms users might say, such as 'i18n/localization', 'docs site', or 'locale files', to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description precisely names the domain ('Repomix documentation website', 'VitePress configuration', 'multi-language content, or translation workflows') but describes scope rather than concrete actions — no verbs like 'adds languages' or 'edits sidebars'. It names the domain with 1-2 implied actions, matching the 3 anchor better than 4, which requires several explicitly listed actions.

3 / 5

Completeness

It explicitly answers 'when' ('Use this skill when working on…') and answers 'what' via the enumerated work areas (VitePress configuration, multi-language content, translation workflows). Not 5 because the 'what' is framed as scope rather than concrete capabilities with trigger phrases; well above 3 since both what and when are present.

4 / 5

Trigger Term Quality

'VitePress configuration', 'multi-language content', and 'translation workflows' are natural phrases a user would say when working on this site. Common variations like 'docs', 'i18n', 'localization', 'locale', or '.md' are absent, so coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Repomix documentation website in `website/` directory' with VitePress/translation specifics carves out a clear niche with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

16

/

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
yamadashy/repomix
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.