vocational

Vocational / technical training courses. Plans the course as a hands-on work task with an operation flow, tool and equipment state, safety boundaries and GO/STOP judgements, instead of a concept lecture. Use when the requirement names a real occupational task, a piece of equipment, a clinical or industrial procedure, or a certification skill.

Quality

88%

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

Quality

Content

86%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 tight, well-structured instruction skill: exact structural requirements, a concrete widget contract, good/bad scene-title examples, an explicit prohibited list, and a graceful fallback for non-vocational requests. The only notable gaps are the absence of a worked widgetOutline example and a final self-validation checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive throughout — structure rules with exact counts ("exactly one slide", "At least three body scenes", "at least one quiz"), a compact widget contract field list, short good/bad title examples, and a brief prohibited list. Nothing explains concepts Claude already knows and every section earns its place, matching the anchor-5 example.	5 / 5
Actionability	Guidance is highly concrete: scene-type counts, the `widgetType: "procedural-skill"` requirement, the `procedureType` enum, and an enumerated `widgetOutline` field contract (task, tools, steps, successCriteria, errorConsequences). It falls short of anchor 5 because no worked example of a `widgetOutline` JSON is given, leaving the exact shape of the renderer contract to be inferred.	4 / 5
Workflow Clarity	The course sequence is explicit (briefing slide → preparation/equipment check → step-by-step operation → verification/recording → handover/completion check) and includes an explicit decision branch ("If the requirement is not vocational ... plan an ordinary course instead"). It sits below anchor 5 because there is no validation step for the produced outline itself (e.g. confirming the three-interactive-scene and quiz requirements are met before finishing).	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are all absent) and none are needed: the body is ~60 lines of tightly organized sections (Structure, Scene naming, widget outlines, Prohibited, fallback) with no bulk reference material that belongs in a separate file, matching the simple-skill allowance for a well-organized single-file skill.	5 / 5
	Total	18 / 20 Passed

Description

87%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 description: third-person voice, explicit what and when clauses, concrete trigger phrases, and a clear niche contrasted against lecture-style courses. Keyword coverage is good but a few natural synonyms (trade, hands-on/practical training) are absent, and the capability list is one composite action rather than a fully enumerated set.

Dimension	Reasoning	Score
Specificity	The description lists several concrete planning components — "an operation flow, tool and equipment state, safety boundaries and GO/STOP judgements" — and explicitly contrasts with a concept lecture. It stops short of anchor 5 because it describes one composite capability (planning vocational courses in a hands-on mode) rather than multiple discrete, comprehensive actions.	4 / 5
Completeness	Both questions are answered explicitly: the what ("Plans the course as a hands-on work task with an operation flow, tool and equipment state, safety boundaries and GO/STOP judgements") and the when ("Use when the requirement names a real occupational task, a piece of equipment, a clinical or industrial procedure, or a certification skill") with concrete trigger phrases, matching the anchor-5 example structure exactly.	5 / 5
Trigger Term Quality	Natural trigger phrases are present: "a real occupational task", "a piece of equipment", "a clinical or industrial procedure", "a certification skill", plus "vocational / technical training" in the opening. Common synonyms a user might say (e.g. trade school, hands-on/practical training, apprenticeship) are missing, so it fits anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	It carves out a clear niche — hands-on occupational procedure training — with distinct triggers (equipment, clinical/industrial procedure, certification) and an explicit contrast against concept lectures, so overlap risk with generic course-design skills is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: THU-MAIC/OpenMAIC
Path: skills/agent-runtime/vocational/SKILL.md
Commit: 636fab0

Reviewed: 3 days 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.