CtrlK
BlogDocsLog inGet started
Tessl Logo

hns-oss-docs-readme-sync

README 4-file synchronization procedure for the oss-docs harness: English README.md as primary source, ko/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and locale-translator specialists for any README work.

68

Quality

83%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, well-structured procedure with executable grep verification, an explicit contract, and concrete anti-patterns. It assumes Claude's competence and provides clear validation checkpoints, scoring well across all dimensions.

DimensionReasoningScore

Conciseness

The body is lean — a compact table, numbered procedure, exact contract, and grep-based checklist — with no padding or explanation of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Guidance is concrete and copy-paste ready: exact switcher label set 'English · 한국어 · 日本語 · 中文', specific file names, and runnable grep commands such as `grep -c '^## ' README.md README.ko.md README.ja.md README.zh.md`.

3 / 3

Workflow Clarity

A clear Author → Derive → Preserve → Verify sequence is paired with an explicit section-order parity checklist run 'before returning', providing a validation checkpoint for the batch 4-file operation.

3 / 3

Progressive Disclosure

Content is self-contained with well-organized sections; the only external pointers — the SSOT report path and Skill("hns-oss-docs-verify") — are one level deep and clearly signaled, and no bundle files exist to require deeper structuring.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and clearly scoped to a narrow niche, but it lacks an explicit user-facing 'Use when...' trigger and leans on internal specialist-loading language for the 'when' half. Adding natural trigger terms would raise trigger-term quality and completeness.

Suggestions

Add an explicit 'Use when ...' clause with natural user phrasing (e.g., 'Use when syncing, translating, or redesigning the 4-locale README set') to lift completeness to 3.

Surface common user variations as trigger terms — 'README translation', 'multi-locale README sync', 'language-switcher header' — rather than only specialist-routing language.

Keep the concrete procedure list; it is the strongest part of the description.

DimensionReasoningScore

Specificity

Lists multiple concrete procedures — 'English README.md as primary source, ko/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe' — matching the anchor for naming several specific actions.

3 / 3

Completeness

The 'what' is explicit and detailed, but the 'when' is only implied via 'Loaded by ... specialists for any README work' rather than an explicit 'Use when...' trigger clause, which the guidelines say caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant terms appear (README, synchronization, translation, 4-locale) but the natural trigger phrasing a user would say is thin; 'Loaded by the content-author and locale-translator specialists' frames internal routing rather than user-facing keywords like 'README sync' or 'translate READMEs'.

2 / 3

Distinctiveness Conflict Risk

The niche is sharply scoped — 'README 4-file synchronization procedure for the oss-docs harness' — making it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
modu-ai/moai-adk
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.