CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-harness-learner

Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.

Quality

71%

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-harness-learner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, highly actionable coordinator skill with concrete commands, a gated execute path, and clear safety boundaries. Its main flaws are heavy repetition of the AskUserQuestion boundary contract and the absence of a post-apply verification checkpoint.

Suggestions

State the orchestrator/AskUserQuestion boundary once (e.g., in 'Key constraint') and reference it from elsewhere, cutting the repeated 'Canonical contract' lines and trimming the [AUTO] annotation to a sentence.

Add a post-apply verification step, e.g., re-run 'moai harness status' after 'apply --execute' to confirm the pending-proposal count decreased, completing the feedback loop for the destructive write.

Show a small example of the emitted payload JSON in Step 3 so the tool output format is copy-paste ready rather than described field-by-field.

DimensionReasoningScore

Conciseness

The body is mostly terse (command blocks, bullet schemas), but the orchestrator/AskUserQuestion boundary is restated at least four times (intro, 'Key constraint', Step 3, the L5 table row), the 'Canonical contract: .claude/rules/.../askuser-protocol.md' pointer is repeated three times, and the long [AUTO] annotation comment adds policy meta-text. This repetition could be tightened to a single statement, matching the 'some unnecessary explanation' anchor rather than 'minor instances' of level 4.

3 / 5

Actionability

Concrete, executable commands throughout: 'moai harness status --project-root <project_root>', 'moai harness apply --execute --id <proposal-id> --project-root <project_root>', and a rollback invocation with a realistic timestamp. The payload schema is enumerated field-by-field. Minor gaps remain (the exact output format the skill should emit is described but not shown), so it sits at level 4 rather than fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

A clear five-step sequence with real checkpoints: status check first, execute path gated by an explicit --id (never inferred), the 5-Layer Safety Pipeline, and deletion confirmation on reject. It falls short of level 5 because there is no post-apply verification step (e.g., re-run 'moai harness status' to confirm the proposal cleared) for file-modifying and destructive paths.

4 / 5

Progressive Disclosure

Well-organized single-file skill: Quick Reference up front, stepwise Implementation Guide, clearly signaled one-level-deep cross-references to contract files (askuser-protocol.md, harness foundation policy). No bundle files exist; the safety-architecture table and frozen-path list are compact enough inline but are candidate material for a reference file, keeping this at level 4 rather than the ideal split of level 5.

4 / 5

Total

15

/

20

Passed

Description

62%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 solid, third-person description that answers both what and when with a clear niche. Its weaknesses are jargon-heavy trigger phrasing that users would not naturally say, and action coverage limited to two verbs.

Suggestions

Rewrite the trigger clause with concrete, natural phrases users would actually say, e.g., 'Triggers when the user runs moai harness status/apply/rollback or asks to review pending learning proposals'.

Add one or two more concrete actions to round out coverage, e.g., 'lists and rolls back learning snapshots' and 'disables harness learning', which the body already documents.

Replace or supplement abstract terms like 'learning lifecycle management' with tangible synonyms (harness auto-updates, pending proposals, rollback) to improve keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Harness learning subsystem coordinator') and two concrete actions ('Produces Tier 4 auto-update proposal payloads', 'orchestrates Apply/Rollback flows'), but coverage stops there. This matches the anchor for domain plus 1-2 concrete actions rather than the several specific actions of level 4.

3 / 5

Completeness

Both 'what' (produces Tier 4 payloads, orchestrates Apply/Rollback) and 'when' ('Triggers when harness learning proposals are pending...') are explicitly stated in third person. The when-clause is present but abstract ('learning lifecycle management is needed') rather than concrete trigger phrases, so it falls at level 4 rather than 5.

4 / 5

Trigger Term Quality

Trigger phrases like 'harness learning proposals are pending' and 'learning lifecycle management' are relevant to the niche but are internal jargon; no natural user phrasings, synonyms, or command-style keywords (e.g., 'moai harness') appear. Some relevant keywords present, but common variations are missing.

3 / 5

Distinctiveness Conflict Risk

The Tier 4 auto-update/orchestrator-bridge niche is distinct and unlikely to trigger the wrong skill. The generic tail 'learning lifecycle management is needed' leaves minor overlap risk with sibling harness skills, keeping it below the clear-niche level 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-harness-learner/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.