moai-meta-harness

DEPRECATED — legacy 7-Phase meta-harness. Redirects to the v4 harness Builder (/moai:harness <natural-language request>) which replaces the static 7-Phase workflow with an orchestrator-direct 4-phase Builder (ANALYZE / PLAN / GENERATE / ACTIVATE) + a manifest-driven dynamic-workflow Runner. Retained as the redirect source for backward-compat invocation paths; the 7-Phase body below is preserved as historical reference, NOT for new harness creation.

Quality

55%

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/moai-meta-harness/SKILL.md

Quality

Content

46%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 a hybrid deprecation-redirect plus historical reference that is over-padded with repeated notices and meta-commentary; it offers some concrete entry commands and well-organized one-level-deep references but lacks executable workflow guidance and validation checkpoints for the active path.

Suggestions

Collapse the repeated deprecation notices (frontmatter, blockquote, @MX:NOTE comment) into a single concise redirect block to recover token budget.

Add an explicit validation/feedback checkpoint to the active v4 Builder sequence so the workflow has a verify-then-proceed gate.

Move the large 7-Phase mapping tables and historical phase summaries into a reference file, leaving SKILL.md as a lean overview + redirect.

Dimension	Reasoning	Score
Conciseness	Noticeably verbose: the deprecation notice is repeated across the frontmatter, a blockquote, and a long @MX:NOTE HTML comment, plus bilingual Korean/English prose and extensive cross-reference churn — much of it meta rather than task-essential.	2 / 5
Actionability	The active redirect path gives concrete commands ('/moai:harness <natural-language request>', '/moai:harness list\|edit\|remove <name>', '/harness:<name>') but the bulk of the body is reference tables and historical prose rather than executable guidance.	3 / 5
Workflow Clarity	A 5-step Builder sequence and a 7-Phase mapping table are present, but the active v4 path has no validation/feedback checkpoint and the only validation content lives in the explicitly-inactive historical body, leaving sequence without checkpoints.	3 / 5
Progressive Disclosure	Content is well-sectioned with one-level-deep, clearly signaled references to real files (references/seven-phase-workflow.md, references/agent-cross-references.md, references/hrn-003-hierarchical-scoring.md — all verified present); not a 5 because hierarchical-scoring.md is an unreferenced orphan and some historical material is inlined.	4 / 5
	Total	12 / 20 Passed

Description

63%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 clearly delineates a distinct deprecated-redirect niche, but it is weighed down by internal jargon and lacks an explicit 'Use when...' trigger clause, leaving the 'when' only weakly implied.

Suggestions

Add an explicit 'Use when...' trigger clause naming the backward-compat invocation paths so the 'when' is stated, not implied.

Replace internal jargon ('orchestrator-direct', 'manifest-driven dynamic-workflow Runner') with terms a user would naturally say, and add synonyms/file extensions.

Tighten the description so the deprecation/redirect intent lands in one or two sentences instead of a dense multi-clause block.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Redirects to the v4 harness Builder', 'replaces the static 7-Phase workflow with an orchestrator-direct 4-phase Builder (ANALYZE / PLAN / GENERATE / ACTIVATE) + a manifest-driven dynamic-workflow Runner', and 'Retained as the redirect source for backward-compat invocation paths' — comprehensive and concrete.	5 / 5
Completeness	Has a clear 'what' (redirect to v4 Builder, replaces 7-Phase) but the 'when' is only weakly implied via 'Retained as the redirect source for backward-compat invocation paths' with no explicit 'Use when...' trigger; per the rubric a missing explicit trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Contains relevant terms ('harness', '/moai:harness', '7-Phase workflow', 'Builder', 'Runner') but leans heavily on internal jargon ('orchestrator-direct', 'manifest-driven', 'meta-harness') and omits common natural synonyms a user would actually say.	3 / 5
Distinctiveness Conflict Risk	Clearly occupies a narrow niche as a deprecated legacy redirect with distinct triggers and minimal conflict risk; not a 5 because the v4-redirect/harness terminology still shares surface overlap with the replacement skill.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
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
Path: .claude/skills/moai-meta-harness/SKILL.md
Commit: 4100d87

Reviewed: 2 days 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.