CtrlK
BlogDocsLog inGet started
Tessl Logo

dsh-config-sync

把 DSH(DeepSeek Harness)的用户配置(~/.dsh 下的 AGENTS.md、settings.yaml 及可选 profiles/预设)打包成脱敏骨架并在设备间安全同步恢复,提供只读审计、显式应用与 SHA-256 校验,绝不携带凭据和运行态。用于复现 DSH 环境、跨设备迁移偏好与模型路由配置。

59

Quality

69%

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 ./skills/dsh-config-sync/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 well-structured, validation-aware operational skill body with clear export/restore workflows and security boundaries. Its main weaknesses are that the bundled script is never referenced with executable commands and the reference file is not explicitly linked, weakening actionability and progressive disclosure.

Suggestions

Reference the bundled tool explicitly — e.g. show `python scripts/sync_dsh_config.py export --with-optional --template` and the restore/check invocations — so the body is copy-paste actionable rather than procedural description.

Link references/manifest.md from the 纳入与排除清单 / 安全边界 sections and move the duplicated include/exclude table out of the body to avoid divergence.

Add an explicit fix-and-retry step to restore (on post-apply SHA mismatch: report, re-apply from known-good archive, re-check) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and operational — tables and numbered steps with no padding about what DSH or SHA-256 is — but the 纳入/排除 table is duplicated between the body and references/manifest.md, a minor trim opportunity.

4 / 5

Actionability

Process steps are concrete about which paths to include/exclude and what manifest.json must contain, but the body never invokes the bundled script (scripts/sync_dsh_config.py) and gives no executable commands, leaving a key execution detail missing.

3 / 5

Workflow Clarity

Export (7 steps) and restore (4 steps) are clearly sequenced with explicit validation checkpoints — sensitive-scan FAIL-and-stop in export, read-only check before apply, and post-apply SHA-256 re-check — but no explicit fix-and-retry loop on SHA mismatch keeps it below the top anchor.

4 / 5

Progressive Disclosure

The body is well-sectioned, but bundle files are not clearly signaled: references/manifest.md is not linked (and its include/exclude rules are inlined instead), and scripts/sync_dsh_config.py is never referenced, so navigation to the bundle is implicit.

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, well-scoped description that states concrete actions and explicit use cases with appropriate third-person voice. It is strong across all dimensions but sits just below the top anchor because trigger phrasing is scenario-based and lacks synonyms/extensions.

DimensionReasoningScore

Specificity

Names the DSH-config domain and several concrete actions — '打包成脱敏骨架', '安全同步恢复', '只读审计', '显式应用', 'SHA-256 校验' — but a few are slightly conceptual (e.g. '脱敏骨架') rather than crisp verbs, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

Answers both 'what' (打包/同步/校验 actions) and 'when' via explicit '用于复现 DSH 环境、跨设备迁移偏好与模型路由配置', satisfying the equivalent-trigger-guidance bar; the 'when' is scenario-based rather than natural user phrasing, so it stops short of the fully-explicit anchor.

4 / 5

Trigger Term Quality

Includes natural terms a DSH user would say — 'DSH 配置', '同步', '跨设备迁移', '偏好', '模型路由' — with good coverage, but lacks common synonyms and file extensions (e.g. .yaml, settings) that would reach the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (DSH harness user-config sync) with specific exclusions ('绝不携带凭据和运行态'), giving mostly distinct triggers; minor overlap risk remains with generic config-sync skills since the description alone does not name the environment-bootstrap boundary.

4 / 5

Total

16

/

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.

Validation15 / 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
ooooooooooooooooooop/agent-tools
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.