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.

66

Quality

79%

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 compact, well-structured instruction skill that assumes Claude's competence and points at exact files. Its main gap is the absence of a verification step in the add-language workflow, which is a multi-file batch operation that should be validated.

Suggestions

Add a validation step to the "Adding New Language" workflow (e.g., "Run the VitePress dev/build command and confirm the new locale appears in nav and search").

Include a minimal copy-paste config snippet for `configXx.ts` and the `locales` entry to make the add-language steps fully executable.

Optionally note how to verify translations against the English source (e.g., a diff or missing-file check) under Translation Guidelines.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every section (structure tree, add-language steps, editing paths, translation guidelines) earns its place.

5 / 5

Actionability

Gives concrete, specific file paths and steps (e.g., "Create `config/configXx.ts`", "Import and add to `locales` in `config.ts`", "Edit `src/[lang]/guide/*.md"), but provides no copy-paste-ready code or commands.

4 / 5

Workflow Clarity

The "Adding New Language" section lists a clear 4-step sequence but includes no validation/verification checkpoint (e.g., build, run dev server, confirm the locale appears) for this multi-file batch operation, capping the score at 3.

3 / 5

Progressive Disclosure

Under 50 lines with no need for external references, organized into well-signaled sections (Structure, Adding New Language, Editing Content, Translation Guidelines); meets the simple-skill exception for a top score.

5 / 5

Total

17

/

20

Passed

Description

78%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 well-scoped, third-person description that pairs an explicit trigger clause with concrete capability areas tied to a specific project and toolchain. It could be sharpened by replacing the generic "working on" with explicit actions and adding common synonyms/extensions.

Suggestions

Replace the generic verb "working on" with concrete actions (e.g., "Configure VitePress, add and translate multi-language content, manage navigation and sidebars").

Add natural synonyms and extensions users might say, such as "i18n", "localization", or ".ts/.md files".

Make the "what" more distinct from the "when" so the capability list reads as actions rather than trigger contexts.

DimensionReasoningScore

Specificity

Names the domain ("Repomix documentation website") and several concrete capability areas ("VitePress configuration, multi-language content, or translation workflows"), though the verb "working on" is generic and coverage is not comprehensive.

4 / 5

Completeness

Has both a clear "what" (working on the Repomix docs site including the three listed areas) and an explicit "when" ("Use this skill when working on..."), but the "what" leans on the generic verb "working on" rather than enumerating concrete actions.

4 / 5

Trigger Term Quality

Includes natural terms users would say ("documentation website", "VitePress configuration", "multi-language content", "translation workflows") but omits synonyms like "i18n"/"localization" and file extensions like ".ts"/".md".

4 / 5

Distinctiveness Conflict Risk

Scoped to a named project ("Repomix documentation website in `website/` directory") plus a specific tool (VitePress), giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

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.

Validation16 / 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.