CtrlK
BlogDocsLog inGet started
Tessl Logo

hns-moaiadk-patterns

moai-adk-go domain-patterns reference for the 4 harness specialists (cli-template-specialist, quality-specialist, workflow-specialist, hook-ci-specialist). Covers the CLI/template/config/hook/spec subsystem architecture, key source paths, the Pipeline specialist delegation map, the Template-First build cycle, the namespace separation contract, and common add-a-template / add-a-hook / add-an-agent / add-a-SPEC workflows. Loaded by the specialists when working on moai-adk-go's own Go codebase and templates.

66

Quality

80%

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

82%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 tight, actionable reference skill body with concrete commands, clear workflows, and explicit validation gates. The main improvement area is making failure-handling feedback loops explicit in the build/test workflows.

DimensionReasoningScore

Conciseness

Dense reference content with tables, paths, and commands that assumes Claude's competence and avoids basic-concept padding; the long SPEC step-7 parenthetical about the retired mx_commit_sha/§E.5 step could be trimmed.

4 / 5

Actionability

Workflows give concrete, copy-paste-ready commands and paths (make build, moai update, go test ./internal/template/... -run TestTemplateNeutralityAudit, moai hook <event>, ./moai init /tmp/test-project) covering the common add-template/hook/agent/SPEC cases.

5 / 5

Workflow Clarity

Multi-step workflows are clearly sequenced with validation checkpoints (neutrality audit, plan-auditor gate, human approval gate, sync-auditor 4-dimension gate), but explicit fix-and-retry feedback loops on failure are not always stated.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a one-level-deep Cross-References block pointing to external rule/spec files; no bundle files exist to split further, and structure is good with minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

78%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 clearly identifies both what the skill covers and when it loads, with strong distinctiveness. It falls just short of top marks on trigger phrasing and an explicit 'Use when...' trigger clause.

DimensionReasoningScore

Specificity

The description names multiple concrete covered areas (CLI/template/config/hook/spec subsystem architecture, source paths, delegation map, Template-First build cycle, namespace contract, add-a-template/hook/agent/SPEC workflows), giving broad coverage with only minor gaps.

4 / 5

Completeness

It states a clear 'what' ('Covers...') and an explicit 'when' ('Loaded by the specialists when working on moai-adk-go's own Go codebase and templates'), satisfying both halves, though the 'when' lacks crisp concrete trigger phrases that would lift it to 5.

4 / 5

Trigger Term Quality

Natural workflow phrases like 'add-a-template', 'add-a-hook', 'add-an-agent', and 'add-a-SPEC' appear alongside domain terms; jargon-heavy, but that vocabulary is the natural trigger language for this niche, with a few common variations missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to moai-adk-go's four harness specialists with highly specific internal references, giving it a clear niche and minimal risk of triggering for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

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.