hns-moaiadk-dev-reference

moai-adk-go local dev reference — version management/release process (sec 5), shell-script hook development (sec 7), build & dev commands (sec 10). Load only when performing these specific tasks.

Quality

75%

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-moaiadk-dev-reference/SKILL.md

Quality

Content

76%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 highly actionable, well-structured reference with copy-paste-ready code and commands across three task areas. Its main weakness is the release workflow, which lacks validation/verification checkpoints for an irreversible operation.

Suggestions

Add explicit validation steps to the Release Process, e.g. 'Verify CHANGELOG entry matches tag', 'Confirm tag pushed: git tag -l v1.0.0', and 'Smoke-test the release binary' before considering the release complete.

Trim the 'Why Shell Scripts' rationale and the bilingual intro blockquote to reduce tokens that do not aid execution.

Consider splitting the detailed release/version-sync checklist into a references file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with code blocks and bullet lists doing the heavy lifting, but sections like 'Why Shell Scripts' and the bilingual intro blockquote add mild over-explanation that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready guidance throughout — ldflags build commands, make targets, a complete hook wrapper bash script, settings.json hook config, and a numbered dev workflow with real commands.	5 / 5
Workflow Clarity	The release process and dev workflow are numbered and sequenced, but the release flow (git tag, push tag, build release) is an irreversible/batch operation with no validation or verification checkpoints, capping this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized under three clear section headers with no nested references, but at ~160 lines all material is inlined in SKILL.md with no external file split, leaving minor organization gaps for a reference skill.	4 / 5
	Total	16 / 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 well-scoped, third-person description that names the project, three concrete task areas, and an explicit load-condition. It is concise and distinct, but the 'when' guidance is slightly generic and could name concrete user trigger phrases.

Suggestions

Replace 'Load only when performing these specific tasks' with explicit trigger phrases, e.g. 'Use when releasing a version, writing a shell-script hook, or running build/dev commands for moai-adk-go'.

Add common synonyms users might say, such as 'tagging a release' or 'writing a Claude Code hook', to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete task areas — 'version management/release process', 'shell-script hook development', 'build & dev commands' — naming the domain with several specific actions, though coverage of each is at a section-label level rather than fully enumerated.	4 / 5
Completeness	Both 'what' (moai-adk-go local dev reference covering three sections) and 'when' ('Load only when performing these specific tasks') are present, but the 'when' clause is generic and refers back to the listed tasks rather than stating explicit trigger phrases.	4 / 5
Trigger Term Quality	Terms like 'release process', 'shell-script hook development', and 'build & dev commands' are natural for the target developer audience with good coverage, though a few common synonyms (e.g., 'tagging a release', 'writing a hook') are missing.	4 / 5
Distinctiveness Conflict Risk	The 'moai-adk-go' qualifier and section-specific scoping give it a clear niche, but general dev terms like 'build & dev commands' and 'version management' carry minor overlap risk with other development skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: modu-ai/moai-adk
Path: .claude/skills/hns-moaiadk-dev-reference/SKILL.md
Commit: 2213871

Reviewed: 4 hours 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.