CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-ado-convert

Converts VitePress/GFM wiki markdown to Azure DevOps Wiki-compatible format. Generates a Node.js build script that transforms Mermaid syntax, strips front matter, fixes links, and outputs ADO-compatible copies to dist/ado-wiki/.

59

Quality

74%

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/deep-wiki/skills/wiki-ado-convert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 detailed, actionable skill body with strong domain specifics and a clear workflow, weakened by minor padding, one stub function, and a monolithic structure with no progressive disclosure.

Suggestions

Implement convertContainerDirectives fully (it is currently only comments) and define collectMarkdownFiles, ROOT, and OUTPUT so the main flow is copy-paste runnable.

Add an explicit 'if a verification check fails, fix and re-run' recovery loop after the Verification Checklist to support the batch transformation.

Move the detailed incompatibility tables and/or full function implementations into a reference file (e.g., references/ado-incompatibilities.md) and summarize inline, enabling one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient and rich in genuine domain knowledge (ADO incompatibilities, Mermaid support), but the 'Why This Is Needed' prose and the 'Compatible As-Is' bullet list are trimmable padding Claude largely already knows.

3 / 5

Actionability

Provides executable code for stripFrontMatter, convertMermaidBlocks, convertSourceLinks, and main, but convertContainerDirectives is a comment-only stub and collectMarkdownFiles/ROOT/OUTPUT are referenced without definition.

4 / 5

Workflow Clarity

Clear sequence with explicit checkpoints ('MUST DO FIRST', 'Do NOT proceed') and a 9-item verification checklist, but it lacks a validate→fix→retry recovery loop for what is a batch operation.

4 / 5

Progressive Disclosure

Well-organized into sections with tables, but it is a ~240-line monolithic document with no bundle files or one-level-deep references to split out the detailed tables and code.

3 / 5

Total

14

/

20

Passed

Description

75%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 specific, distinctive description that clearly states what the skill does, but it lacks any explicit 'Use when...' trigger guidance, which limits its completeness score.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., 'Use when publishing VitePress/GFM docs to an Azure DevOps Wiki, or when the user mentions ADO Wiki, Mermaid conversion, or wiki migration').

Include common synonyms or file extensions (e.g., 'markdown', '.md', 'Azure DevOps', 'ADO') to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'transforms Mermaid syntax, strips front matter, fixes links, and outputs ADO-compatible copies to dist/ado-wiki/' — with comprehensive coverage of what the script does.

5 / 5

Completeness

The 'what' is explicit and clear, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Names natural domain terms users would say ('VitePress/GFM wiki markdown', 'Azure DevOps Wiki', 'Mermaid') with good coverage, though a few synonyms or extensions are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear, narrow niche (VitePress/GFM → Azure DevOps Wiki conversion) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing, 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

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.