CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

moai-ref-cross-model-audit

Cross-model audit convergence reference for the plan-auditor and sync-auditor agents. Documents how to invoke the `audit_multi` MCP tool to fan a code review out across the Claude subscription, codex, and GLM (z.ai) backends, converge their independent verdicts, and fold the resulting per-backend verdicts + disagreement flag into the audit output. The single skill both audit entry points load — no duplication.

Quality

78%

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-ref-cross-model-audit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

An exceptionally actionable, well-sequenced operational reference with explicit validation checkpoints and error-recovery loops. Its weaknesses are token efficiency (a load-bearing invariant repeated across four sections) and the absence of any progressive disclosure despite substantial specialized sub-topics that could live in reference files.

Suggestions

State the explicitly-configured-required-gate-unmet rule once (in Convergence policy) and reference it from Fail-open identity and Cross-references instead of restating it each time.

Move the delta-review mechanics, the closure-second-review contract block, and the audit-receipts detail into a references/ file, keeping SKILL.md to the core invocation, convergence, and verdict-folding flow.

Trim the second JSON example to only the fields that differ from the first (carried_legs, error_class, fail_open_backends) and show one filled claude_verdict object to make the invoke snippets fully copy-paste ready.

DimensionReasoningScore

Conciseness

Dense with non-obvious domain rules, but the required-gate-unmet invariant is restated roughly four times (Convergence policy, Fail-open identity, Cross-references, Checking the result), and the second full JSON output example largely duplicates the first — more than the 'minor instances' of the 4 anchor.

3 / 5

Actionability

Concrete throughout — exact tool name, full parameter table, copy-paste commands ('moai verify audit-plan --project-root <toplevel> --result-file <that path>') and the exact AUDIT-VERDICT line format. Minor gaps keep it below 5: the invoke snippets use unfilled placeholders (<your verdict>, <one-line>) with no worked claude_verdict example, and the digest members are listed in prose without a sample JSON object.

4 / 5

Workflow Clarity

Clear sequencing via the path-selection decision table, an explicit 3-step validation procedure against the plan, and genuine feedback loops for error recovery (rerun_legs for inconclusive legs, FAIL → repair → delta re-audit chain) plus a 5-case verdict-folding table — matches the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist and all ~370 lines are inline; specialized branches a typical invocation does not need (delta review, the closure-second-review contract block, audit receipts) are inlined rather than split into reference files. Section headers are good, but content that should be separate is inline, matching anchor 3 rather than 4.

3 / 5

Total

15

/

20

Passed

Description

75%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 highly specific, distinctive description that clearly states what the skill does and for which agents. Its main weakness is that the description field alone lacks an explicit 'Use when...' trigger clause — that guidance exists only in the separate when_to_use frontmatter field, capping completeness.

Suggestions

Fold a condensed trigger clause into the description field itself (e.g., 'Use when the audit plan reports a cross-model backend or the auditor needs a cross-backend second opinion') so the description is self-sufficient when when_to_use is not surfaced.

Add natural synonym variations such as 'multi-model review' or 'cross-backend audit' to broaden trigger-term coverage beyond the current terminology.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named backends — 'invoke the `audit_multi` MCP tool', 'fan a code review out across the Claude subscription, codex, and GLM (z.ai) backends', 'converge their independent verdicts', 'fold the resulting per-backend verdicts + disagreement flag into the audit output' — comprehensive for its domain, matching the 5 anchor rather than 4.

5 / 5

Completeness

The 'what' is explicit and detailed, but the description field contains no 'Use when...' clause — the closest is 'The single skill both audit entry points load', a load fact rather than trigger conditions (the real conditions live in the separate when_to_use field). Per the rubric cap, a missing use-when clause limits completeness to anchor 3.

3 / 5

Trigger Term Quality

Good domain-natural keywords ('cross-model audit convergence', 'code review', 'verdicts', 'disagreement flag'), but the description field itself carries no synonym variations such as 'multi-model review', 'second opinion', or 'cross-backend', so it falls short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Names its niche precisely — 'plan-auditor and sync-auditor agents', the `audit_multi` MCP tool, 'GLM (z.ai) backends' — leaving minimal overlap risk with any other skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

modu-ai/moai-adk

Path

.claude/skills/moai-ref-cross-model-audit/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.