CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-vitepress

Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output. Use when the user wants to create a browsable website from generated wiki pages.

69

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

Highly actionable, executable guidance focused on non-obvious VitePress/Mermaid gotchas. The main gap is the absence of explicit validation/verification checkpoints for the batch post-processing and build steps.

Suggestions

Add a verification checkpoint after `npm run docs:build` (e.g. confirm `wiki-site/.vitepress/dist/` exists and spot-check that Mermaid SVGs render with dark fills) so errors are caught before declaring success.

Add a validate-then-retry loop for the batch post-processing step (scan .md files → apply fixes → re-scan to confirm no `<br/>` or bare `<T>` remain) since it is a batch operation.

Consider moving the full `themeVariables` color map and the three-layer Mermaid fix detail into a `references/mermaid-dark-mode.md` file to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dense with hard-won technical specifics (mermaid themeVariables, inline-style polling, gotchas) and mostly assumes Claude's competence; a few prose lines like the "Use setup()... NOT enhanceApp()" rationale could be trimmed but largely earn their place.

4 / 5

Actionability

Copy-paste-ready code is provided throughout — config.mts mermaid block, CSS overrides, theme/index.ts onMounted polling, click-to-zoom JS, modal CSS, post-processing rules, and the build command — covering the common cases fully.

5 / 5

Workflow Clarity

Sections sequence the build (scaffold → config → three-layer Mermaid fix → click-to-zoom → post-processing → build), but there are no validation/verification checkpoints for the batch .md post-processing or the build output, capping this dimension at 3.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections in a single file with no nested references; for a build recipe this density is appropriate, though some detail (full themeVariables, three-layer fix) could live in reference files.

4 / 5

Total

16

/

20

Passed

Description

92%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, third-person description that concretely states both the capability and the use-case trigger. Minor upside would come from using more literal user phrasing and adding file-extension keywords.

DimensionReasoningScore

Specificity

"Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output" lists multiple concrete actions (dark theme, dark-mode Mermaid with zoom, production build) with comprehensive coverage.

5 / 5

Completeness

It explicitly answers what ("Packages generated wiki Markdown into a VitePress static site...") and when ("Use when the user wants to create a browsable website from generated wiki pages") with concrete trigger guidance.

5 / 5

Trigger Term Quality

"Use when the user wants to create a browsable website from generated wiki pages" plus "VitePress static site" gives good keyword coverage, but the phrasing is paraphrased rather than the exact terms users say (e.g. "build a site", "package wiki") and file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

The VitePress + generated-wiki-Markdown niche with dark-mode Mermaid is a clear, narrow specialty unlikely to trigger for unrelated skills.

5 / 5

Total

19

/

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
freightCognition/linehaulai-claude-marketplace
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.