hns-oss-docs-i18n-rules

HARD i18n rules digest for the oss-docs harness specialists working on moai-adk-go README 4-locale set and the docs-site (adk.mo.ai.kr). Covers the canonical-locale chains, the 4-locale same-PR obligation, Mermaid TD-only, the no-emoji + icon-shortcode rule, emphasis-marker spacing, the URL blacklist, version SSOT, vercel.json redirect pattern, and the immutable Vercel binding. Loaded FIRST by every oss-docs specialist before any edit.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/hns-oss-docs-i18n-rules/SKILL.md

Quality

Content

87%

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

A tight, highly actionable rules digest with excellent conciseness and concrete patterns, plus clean one-level-deep reference to its SSOT. The only gap is workflow clarity: verification is referenced rather than presented as an inline validate→fix→retry loop.

Suggestions

Inline a short verification loop (run the hns-oss-docs-verify checks → fix any locale-parity/blacklist/Mermaid violations → re-run until clean) so the workflow has explicit checkpoints.

Add a one-line pre-edit checklist that specialists run before committing (canonical-only authoring, all 4 locales present, adk.mo.ai.kr-only URLs, no LR/RL diagrams).

Dimension	Reasoning	Score
Conciseness	A lean rules digest with no padding or explanation of concepts Claude already knows (e.g., "Author in the canonical locale only; derive the rest"; "Allowed: flowchart TD, graph TB. Forbidden: LR / RL directions"); stale/time-sensitive items are isolated in a Known-Stale section, so every token earns its place.	3 / 3
Actionability	Gives concrete, copy-paste-ready patterns for an instruction-only skill: exact shortcode syntax with variant list, correct/wrong emphasis-marker examples, enumerated URL-blacklist entries, and vercel.json redirect patterns with locale regex ("/:locale(ko\|en\|ja\|zh)/old-path → /:locale/new-path").	3 / 3
Workflow Clarity	Rules are well organized into numbered sections with named checks (the locale-parity FAIL threshold, a referenced Skill("hns-oss-docs-verify")), but there is no in-body multi-step sequence with explicit validate→fix→retry checkpoints; verification is delegated out rather than presented as an inline feedback loop.	2 / 3
Progressive Disclosure	Acts as a clearly signaled working digest pointing one level deep to the SSOT ("SSOT: .moai/docs/docs-site-i18n-rules.md") with well-organized numbered sections; no bundle files exist to evaluate, and the digest/SSOT split is an appropriate content split.	3 / 3
	Total	11 / 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.

A highly specific, distinctive rules digest, but it leans on project-internal jargon and lacks an explicit user-facing "Use when..." trigger, capping completeness and trigger-term quality at 2. Voice is correctly third person.

Suggestions

Add an explicit trigger clause, e.g. "Use when editing oss-docs READMEs or docs-site pages, or when the user asks to translate/derive locale content for adk.mo.ai.kr."

Soften project jargon with a couple of natural user terms ("internationalization", "locale translation", "README localization") to improve trigger-term coverage.

Lead with the one-line purpose before the rule enumeration so the "what" is graspable before the detail.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete rules ("canonical-locale chains, the 4-locale same-PR obligation, Mermaid TD-only, the no-emoji + icon-shortcode rule, emphasis-marker spacing, the URL blacklist, version SSOT, vercel.json redirect pattern, and the immutable Vercel binding"), matching the score-3 anchor for specific concrete actions.	3 / 3
Completeness	The "what" is explicit (a rules digest covering named i18n rules), but there is no explicit "Use when..." trigger; the only timing cue is the operational "Loaded FIRST by every oss-docs specialist before any edit", which is only an implied when — capping completeness at 2 per the missing-trigger guidance.	2 / 3
Trigger Term Quality	Contains some relevant real terms ("i18n", "README", "4-locale", "Mermaid") but is dominated by project-internal jargon ("oss-docs harness specialists", "moai-adk-go README 4-locale set") a user would not naturally say; not score 3 because coverage of natural user terms is incomplete, not score 1 because genuine keywords are present.	2 / 3
Distinctiveness Conflict Risk	Targets a sharply defined niche (oss-docs i18n rules for moai-adk-go / adk.mo.ai.kr) with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: modu-ai/moai-adk
Path: .claude/skills/hns-oss-docs-i18n-rules/SKILL.md
Commit: 05117b6

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.