CtrlK
BlogDocsLog inGet started
Tessl Logo

openmaic

OpenMAIC assistant for setting up, generating, and extending OpenMAIC. Use when the user wants to use OpenMAIC, generate a multi-agent interactive classroom, or build on / extend / customize OpenMAIC and its @openmaic/* SDK (secondary development, 二开) — covers Live Demo or local setup, startup modes, provider keys, classroom generation, and secondary development (forking, providers/storage/themes, routes, or the renderer/editor).

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 confirmation-heavy SOP with clear phased sequencing, strong validation checkpoints, and good progressive disclosure through real reference files. Minor redundancy on the API-key rules and a second level of reference nesting on the extend path keep it just short of top marks.

Suggestions

Collapse the three near-duplicate Core Rules about API keys ('do not ask for keys in chat', 'prefer editing config files themselves', 'do not offer to write keys') into a single boundary statement to tighten conciseness.

Consider inlining a one-line teaser of each startup mode or provider path in SKILL.md so the body is actionable without always loading a reference, or accept the navigational style explicitly.

For the extend path, surface extend-cookbook.md and extend-sdk.md as named sub-routes directly from SKILL.md's Phase 0 to avoid the 2-level hop through extend.md.

DimensionReasoningScore

Conciseness

Mostly lean and efficient with no explanations of concepts Claude already knows, but the API-key handling theme is restated across three near-duplicate Core Rules ('Do not default to asking the user to paste API keys', 'Prefer guiding the user to edit local config files themselves', 'Do not offer to write API keys into config files').

4 / 5

Actionability

Provides concrete routing ('Load [references/clone.md]'), a specific config path ('~/.openclaw/openclaw.json'), and a concrete health check ('GET {url}/api/health'); most executable code/commands are delegated to references, which is appropriate but leaves the body itself more navigational than hands-on.

4 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with explicit validation checkpoints (health check before generation, confirm before state-changing actions) and feedback loops ('If generation later fails due to provider/model/auth issues, return to this phase').

5 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled one-level-deep markdown links to six real reference files; the extend path nests a second level (extend.md → extend-cookbook.md / extend-sdk.md), which is well-signaled but introduces 2-level reference nesting.

4 / 5

Total

17

/

20

Passed

Description

92%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 strong, specific description that clearly states capabilities and explicit trigger conditions with good synonym coverage. It is comprehensive on what and when, and highly distinct from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'setting up, generating, and extending OpenMAIC', 'classroom generation', 'forking, providers/storage/themes, routes, or the renderer/editor' — with comprehensive coverage of the skill's scope.

5 / 5

Completeness

Explicitly answers both 'what' (setting up, generating, extending OpenMAIC, covering setup/startup/keys/secondary development) and 'when' ('Use when the user wants to use OpenMAIC, generate a multi-agent interactive classroom, or build on / extend / customize OpenMAIC').

5 / 5

Trigger Term Quality

Good keyword coverage including synonyms ('build on / extend / customize', 'secondary development', '二开', 'SDK', 'forking') and the natural phrase 'generate a multi-agent interactive classroom', though triggers are largely anchored to the proper noun OpenMAIC.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche defined by the OpenMAIC product name and the @openmaic/* SDK with distinct triggers; minimal conflict risk since a user mentioning OpenMAIC or 二开 unambiguously intends this skill.

5 / 5

Total

19

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
THU-MAIC/OpenMAIC
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.