CtrlK
BlogDocsLog inGet started
Tessl Logo

hns-oss-docs-readme-sync

README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/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.

67

Quality

81%

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

93%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 body is lean, concrete, and well-structured with copy-paste-ready verification commands and a clear procedure. The only gap is the absence of an explicit error-recovery feedback loop for the batch 4-file operation, which holds workflow clarity at 4.

Suggestions

Add an explicit feedback loop after the parity checklist (e.g. 'If any grep shows a mismatch, re-author the section in README.ko.md, re-derive the affected locale, and re-run the checklist').

Make step 4's validation self-contained rather than deferring to 'below' by naming the checklist as the gate before returning.

DimensionReasoningScore

Conciseness

The ~88-line body is lean and dense, explaining no common concepts (what a README or markdown is) and keeping every section operational; padding is negligible.

5 / 5

Actionability

Provides copy-paste-ready grep commands with exact patterns, an exact label set, a verbatim-preservation list, and a concrete anti-patterns table covering the common cases.

5 / 5

Workflow Clarity

A clear numbered procedure with an explicit 'Verify parity ... before returning' checkpoint and a full checklist, but the batch/parallel 4-file operation is missing an explicit error-recovery feedback loop (re-author ko and re-derive if counts differ).

4 / 5

Progressive Disclosure

A self-contained, well-organized overview with no nested references; the single Skill(...) pointer and the history-only report path are one-level-deep and clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

70%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 specific and distinctive, naming concrete mechanisms and a clear niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness at 3 despite a strong 'what'.

Suggestions

Add an explicit 'Use when ...' trigger clause naming natural user phrases (e.g. 'Use when syncing, translating, or localizing the README set across ko/en/ja/zh').

Frame capabilities as verbs rather than nouns (e.g. 'Authors changes in README.ko.md, derives en/ja/zh, verifies parity') to strengthen the specificity of actions.

Include common synonyms/file extensions (localization, i18n, .md) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete mechanisms (ko-as-primary authoring, en/ja/zh derivation, shared switcher header contract, section-order parity checklist, manual verification recipe), with only minor gaps since actions are framed as nouns rather than verbs.

4 / 5

Completeness

A clear and detailed 'what' is present, but 'when' is only weakly implied via 'Loaded by the content-author and locale-translator specialists for any README work' with no explicit 'Use when...' clause, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good natural keyword coverage (README, README.ko.md, Korean, en/ja/zh, translation) but missing common synonyms like localization/i18n and an explicit trigger clause.

4 / 5

Distinctiveness Conflict Risk

A sharply defined niche (4-file ko-canonical README sync with the oss-docs harness and a named header contract) gives distinct triggers and minimal conflict risk.

5 / 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

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.