CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-vitepress

Transform generated wiki Markdown files into a polished VitePress static site with dark theme and interactive Mermaid diagrams. Use when user asks to "build a site" or "package as VitePress", user runs the /deep-wiki, or user wants a browsable HTML output from generated wiki pages.

Quality

80%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wiki-vitepress/SKILL.md

The canonical home for this skill is wiki-vitepress in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 dense, practical skill body with concrete code for the dark-mode mermaid fixes, click-to-zoom, and build steps. Its main weaknesses are a duplicated 'When to Use' section with a filler sentence, a fragmentary theme/index.ts example, and no validation checkpoint for the batch .md post-processing or build output.

Suggestions

Remove the duplicated 'When to Use' section at the end of the body (including the filler line 'This skill is applicable to execute the workflow or actions described in the overview.') to cut redundant padding.

Add a validation checkpoint around the batch post-processing and build steps, e.g. verify the build succeeded and spot-check a rendered page in wiki-site/.vitepress/dist/ before declaring completion.

Make the theme/index.ts example a complete file (full setup() and Layout wiring) and give the post-processing rules a concrete script or command so all guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and code-first with no explanations of concepts Claude already knows. Minor trimmable padding exists: a duplicated "When to Use" section (appears at both the top and the end) and the vacuous closing line "This skill is applicable to execute the workflow or actions described in the overview."

4 / 5

Actionability

Largely executable guidance: complete mermaid config block, copy-paste CSS overrides, and a build command. Gaps keep it below 5: the theme/index.ts snippet is a fragment ("// In setup()") rather than a complete file, and the post-processing rules give direction without a script or command.

4 / 5

Workflow Clarity

Section order implies a sequence (scaffold → config → fixes → post-process → build), but the post-processing step batch-modifies all .md files and the build step has no output verification, so validation checkpoints are absent. Per the rubric, a batch operation without validation caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Single-file skill with no bundle files and clear, well-organized section headers with no nested references. Not 5 because at ~145 lines the detailed mermaid fix layers and post-processing rules could arguably live in a one-level-deep reference file to keep the overview leaner.

4 / 5

Total

15

/

20

Passed

Description

83%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 description that clearly states what the skill does and when to use it, with concrete, natural trigger phrases and a well-defined niche. Minor improvements possible by adding a few more natural synonyms and making the 'build a site' trigger more context-bound.

DimensionReasoningScore

Specificity

"Transform generated wiki Markdown files into a polished VitePress static site with dark theme and interactive Mermaid diagrams" names the domain and concrete deliverable features (dark theme, interactive Mermaid), listing several specific capabilities. It falls short of the 5 anchor because it describes one composite transform action rather than multiple distinct actions like 'extract, fill, merge, convert'.

4 / 5

Completeness

Explicitly answers 'what' (transform wiki Markdown into a VitePress static site with dark theme and Mermaid diagrams) and 'when' ("Use when user asks to 'build a site' or 'package as VitePress', user runs the /deep-wiki, or user wants a browsable HTML output") with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Includes natural user phrases — "build a site", "package as VitePress", "browsable HTML output", "runs the /deep-wiki" — giving good keyword coverage. Not 5 because common synonyms such as 'website', 'publish', 'documentation site', or 'static site' are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (VitePress packaging of generated wiki output, /deep-wiki command) with mostly distinct triggers. Not 5 because "build a site" is a fairly broad phrase that could overlap with other site-building skills.

4 / 5

Total

17

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/wiki-vitepress/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.