CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

66%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/moai-meta-harness/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 well-structured with a clear redirect section, a legible phase-mapping workflow, explicit validation gates, and mostly well-signaled one-level-deep references. Its main weaknesses are heavy repetition of the deprecation message and verbose internal-policy commentary that inflate token cost without operational value, plus deferral of key execution detail to out-of-bundle files.

Suggestions

Consolidate the deprecation notice into a single canonical statement — it is currently repeated across the title notice, opening blockquote, @MX:NOTE comment, ATTRIBUTION block, and redirect section.

Move the long policy-supersession HTML comment (the @MX:NOTE block) into a reference file or trim it to its operative sentences; it is internal contract rationale, not reader-facing guidance.

Resolve the orphan 'references/hrn-003-hierarchical-scoring.md' — either cite it alongside hierarchical-scoring.md or remove it, since it is never referenced from the body.

DimensionReasoningScore

Conciseness

The deprecation message is restated at least five times (title notice, opening blockquote, the long @MX:NOTE HTML comment, the ATTRIBUTION block, and the 'v4 Redirect' section), and the inline policy-supersession comment is dense internal-contract rationale that adds no operational value for a reader. Not 1: the legacy body is deliberately preserved under an explicit 'HISTORICAL REFERENCE' separator and time-sensitive data (versions, 2026 dates, effectiveness figures) sits inside that marked deprecated section, which the guidelines treat as acceptable placement. Not 3: the repetition of the redirect message and the oversized inline comment are several padded sections, not just occasional tightening opportunities.

2 / 5

Actionability

There is concrete guidance — explicit commands ('/moai:harness <natural-language request>', '/moai:harness list|edit|remove <name>', '/harness:<name>'), artifact paths, the phase-mapping table, and [HARD] contracts with exact emission rules. Not 4: key operational detail is deferred to files outside this skill ('harness-builder.md', 'project/meta-harness.md' § 6.4.1, '.claude/rules/moai/…') that a reader cannot act on from the body alone, and no example of the actual emission template is inlined.

3 / 5

Workflow Clarity

The 7-phase workflow is clearly sequenced with a per-phase inputs/outputs mapping table and phase summaries, and validation is explicit: the Phase 6 Sprint Contract (4 dimensions, 0.75 pass threshold, FROZEN floor 0.60) plus the 'moai doctor harness' smoke gate with named failure conditions (empty description, dangling skills: reference, missing skills: key) forms a real checkpoint with feedback. Not 5: recovery steps after a gate failure and the actual phase-execution mechanics are referenced elsewhere rather than stated, leaving minor validation-loop gaps.

4 / 5

Progressive Disclosure

Structure is good: the body is organized into clear sections, and detail is pushed to one-level-deep reference files cited with descriptive link text ('references/seven-phase-workflow.md' cited for the phase walkthrough, 'references/agent-cross-references.md' for the agent inventory, 'references/hierarchical-scoring.md' for Phase 3b) — all three verified to exist. Not 5: 'references/hrn-003-hierarchical-scoring.md' is present in the bundle but never referenced from the body, and some dense contract material (the namespace storage tables and the supersession comment) is inlined rather than split out.

4 / 5

Total

13

/

20

Passed

Description

66%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-crafted deprecation notice that names concrete replacement machinery and a clear redirect target, but it omits explicit 'use when' trigger phrasing and never states what the underlying skill functionally does (architect/generate project-specific agent teams), leaving a user reading only the description without the full invocation picture.

Suggestions

Add an explicit trigger clause to the description, e.g. 'Fires only when a backward-compat invocation references the legacy 7-Phase workflow' — the current 'when' is only implied by 'Retained as the redirect source for backward-compat invocation paths'.

Include one phrase stating the underlying capability (e.g., 'architects and generates project-specific agent teams') so the description conveys what is being deprecated, not just that it is deprecated.

Add one or two natural synonyms users would say (e.g., 'agent team', 'harness creation') to broaden trigger coverage beyond the current 7-Phase/v4 jargon.

DimensionReasoningScore

Specificity

The description lists several concrete, named actions — 'Redirects to the v4 harness Builder (/moai:harness <natural-language request>)', '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'. Not 5: the underlying capability (architecting/generating agent teams) never appears, so coverage of what the skill actually does has a real gap. Not 3: the actions named are specific and multiple, not just 1-2 generic ones.

4 / 5

Completeness

The 'what' is clear (legacy 7-Phase meta-harness that redirects to the v4 Builder), but the 'when' is only weakly implied by 'Retained as the redirect source for backward-compat invocation paths' — there is no explicit 'Use when…' clause or equivalent in the description itself (the explicit trigger guidance lives in the separate when_to_use field). Per the guideline, a missing explicit trigger clause caps completeness at 3; not 4 because the when-guidance present is implicit rather than 'explicit but could be more specific'.

3 / 5

Trigger Term Quality

Good keyword coverage for a deprecation redirect: 'legacy 7-Phase meta-harness', 'v4 harness Builder', '/moai:harness', 'backward-compat', 'deprecated', 'harness' repeated naturally. A few natural terms a user might say are missing (e.g., 'agent team', 'meta-skill', 'project harness'), keeping it below the comprehensive-synonyms anchor of 5.

4 / 5

Distinctiveness Conflict Risk

A very specific niche is carved out: 'DEPRECATED — legacy 7-Phase meta-harness… NOT for new harness creation', clearly distinguishing it from the active v4 Builder. Not 5: it shares 'harness' creation vocabulary with the v4 Builder skill it redirects to, creating minor overlap risk between the two skills.

4 / 5

Total

15

/

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

Path

.claude/skills/moai-meta-harness/SKILL.md

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.