CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dsh-doc-site-sync

Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.

Quality

98%

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

The canonical home for this skill is dsh-doc-site-sync in river666/deepseek-harness-enterprise

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a model instruction-only skill: dense project-specific contracts, executable validation commands at every gate, an explicit error-recovery loop, and clean one-level-deep references to the owning files. It neither pads with known concepts nor omits key details, and it clearly separates content synchronization from deployment concerns.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence throughout: no explanation of what VitePress, Markdown, or manifests are — only project-specific contracts ('Never edit or commit website/.generated/', 'foo.zh.md projects to the root route') and commands. Every token earns its place.

5 / 5

Actionability

Guidance is fully executable: copy-paste commands (pnpm docs:dev, pnpm docs:check, pnpm run doc-sync, pnpm run lint, git diff --check), explicit per-field DocsPage guidance (source, route, label, sidebar, section, order, sourceAliases) with pairedPages()/mirroredPages() usage rules, and a concrete change-classification table covering the common cases.

5 / 5

Workflow Clarity

A clear sequence (read owning contracts → classify the change → set manifest fields → preserve link behavior → preview and validate) with explicit validation gates ('Run the focused website gate before treating the mapping as valid') and a feedback loop for error recovery ('If Markdown link checks pass but the site build reports a missing fragment, follow the verify-doc-site-fragments source and target paths'). Destructive rename/remove operations are handled atomically with docs:check rejecting stale entries.

5 / 5

Progressive Disclosure

No bundle files exist, and the ~87-line body is appropriately self-contained: all external material (docs/AGENTS.md, sibling skills dsh-doc-standards and dsh-pre-push-checks, website/docs.ts, .vitepress/config.ts, docs/i18n/README.md) is referenced via clearly signaled one-level-deep links with explicit 'read before changing' contracts, making navigation easy.

5 / 5

Total

20

/

20

Passed

Description

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

The description is exemplary: it enumerates concrete, domain-specific actions and exact commands, states an explicit 'Use when...' trigger covering publish/update/move/remove/diagnose/fix scenarios, and is tightly scoped to the documentation-site projection pipeline. It is both comprehensive and concise with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named artifacts — 'publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow' — comprehensively covering the skill's capabilities, matching the top anchor rather than leaving minor gaps.

5 / 5

Completeness

The explicit 'Use when publishing, updating, moving, or removing...' clause answers when, and the enumerated actions (edit manifest mappings, diagnose missing pages, fix projected links, run the doc-sync workflow) explicitly state what with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing ('publishing', 'moving', 'page missing from the VitePress site', 'fixing projected documentation links') is paired with the exact commands and file names users would mention (docs.ts, docs:dev, docs:check, doc-sync), giving comprehensive keyword coverage for the domain.

5 / 5

Distinctiveness Conflict Risk

Anchored to DeepSeek Harness, VitePress, website/docs.ts, and the doc-sync workflow — a clear niche with distinct triggers that would not fire for generic documentation or prose-editing skills.

5 / 5

Total

20

/

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: 9 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

river666/deepseek-harness-enterprise

Path

.claude/skills/dsh-doc-site-sync/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.