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

42%

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

42%

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

The content is well-structured for progressive disclosure with real, clearly-signaled reference files, but it is severely verbose — restating the deprecation repeatedly and preserving the full legacy body inline. The active v4 path is actionable but the legacy generation workflow stays abstract and lacks validation checkpoints on the active path.

Suggestions

Collapse the repeated deprecation/attribution blocks into a single concise notice and move the verbatim 7-Phase body entirely into a reference file rather than keeping it inline.

Add explicit validation checkpoints to the active v4 Builder steps (e.g., a verify step after GENERATE) so the active path matches the legacy path's gating rigor.

Tighten the abstract generation descriptions ('generates harness skeleton') into concrete, executable steps or link directly to the owning policy's step list instead of deferring vaguely.

Dimension	Reasoning	Score
Conciseness	The body is heavily padded: the deprecation notice is restated ~5 times, a long @MX:NOTE comment paragraph and repeated attribution are inline, and the entire legacy 7-Phase body is preserved verbatim alongside internal MoAI context Claude does not need.	1 / 3
Actionability	Provides concrete commands ('/moai:harness <request>', '/harness:<name>', 'moai doctor harness') and a clear artifacts/owners table, but the generation steps remain abstract ('generates harness skeleton') and defer to other policies rather than giving executable instruction.	2 / 3
Workflow Clarity	The 7-phase sequence is tabulated with inputs/outputs and a Phase 6 validation gate (pass threshold 0.75), but that workflow is marked historical/non-active while the active v4 Builder path lists 5 steps with no validation checkpoints.	2 / 3
Progressive Disclosure	Detailed material is split into real one-level-deep references (references/seven-phase-workflow.md, references/agent-cross-references.md, references/hrn-003-hierarchical-scoring.md, all present) with clear 'See ... for ...' signaling, giving easy navigation.	3 / 3
	Total	8 / 12 Passed

Description

42%

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 clearly communicates the skill's deprecated-redirect role and distinguishes it from the active v4 Builder, but relies on internal jargon rather than natural user trigger terms and lacks an explicit 'Use when...' clause. It is adequate for a redirect stub but weak as a discoverable skill description.

Suggestions

Add an explicit 'Use when...' clause stating the backward-compat invocation paths that fire this skill, so the 'when' is not merely implied.

Replace internal jargon ('7-Phase', 'manifest-driven dynamic-workflow Runner', 'backward-compat invocation paths') with natural trigger terms a user would actually say.

Lead with the skill's own concrete action (redirect) rather than describing the v4 Builder's internals, to keep specificity about what this skill does.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Redirects to the v4 harness Builder', 'replaces the static 7-Phase workflow') but the skill's own capability is singular (redirect) while the rest describes the v4 target rather than this skill's actions.	2 / 3
Completeness	States what the skill does (legacy redirect to v4 Builder) but the 'when' is only implied ('backward-compat invocation paths') with no explicit 'Use when...' trigger clause, capping completeness at 2.	2 / 3
Trigger Term Quality	Keywords are internal jargon ('7-Phase', 'manifest-driven dynamic-workflow Runner', 'backward-compat invocation paths', '/moai:harness') rather than natural terms a user would say when needing this skill.	1 / 3
Distinctiveness Conflict Risk	Clear deprecated-redirect niche with explicit 'NOT for new harness creation' disambiguation, making it unlikely to trigger for the active v4 Builder or other skills.	3 / 3
	Total	8 / 12 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: 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.