pptx-import

会话里有上传的 .pptx，且用户要把这份幻灯片填进一节已建的课（先 create_stage 建课，再 import_pptx 把页面追加进这节课堂，保留原版排版；课堂标题以 create_stage 为准，PPT 不接管）。随后逐页检查（有 render_scene_preview 就渲染看）并修 bad case，理解整课之后才写旁白/spotlight，最后 TTS。仅在用户要求时插入 quiz 或 interactive。不要重新规划整课。

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The body is a well-structured, highly actionable orchestration guide with clear sequencing, feedback loops, and validation checkpoints. It is efficient though slightly repetitive, and well-organized with only minor progressive-disclosure gaps.

Suggestions

Consolidate the repeated 'do not replan / do not generate_scene on imported slides' guidance into one Hard rule and reference it, to reduce redundancy.

Consider extracting the bad-case repair table into a reference file (e.g. references/repairs.md) and signaling it from Step 3c, deepening progressive disclosure.

Add a one-line example request shape for import_pptx and patch_stage set to lift actionability from strong to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Dense and operational, assuming Claude knows the domain; minor repetition (the 'do not replan'/'do not generate_scene on imported slides' rule recurs several times) could be trimmed without losing clarity.	4 / 5
Actionability	Names specific tools with concrete parameters and paths (read_stage at path:/scenes/<order\|id>, patch_stage set on /content/canvas/.../left, edit_deck retitle/insert/delete, detail:"tree"/"source") plus a problem→tool→path bad-case table; minor gaps in exact request payloads.	4 / 5
Workflow Clarity	A clearly sequenced 6-step process with an explicit 'do not rearrange' order, sub-steps 3a/3b/3c, explicit feedback loops (look→edit→look, 'at most two extra previews per page'), validation checkpoints (audioId check, render to verify), and a Closing checklist plus Hard rules.	5 / 5
Progressive Disclosure	Well-organized into headed sections with one well-signaled one-level reference to the pro-editing skill via <available_skills>; no bundle files exist to split, though the bad-case table and Step 6 quiz procedure could arguably be extracted.	4 / 5
	Total	17 / 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.

The description is specific and distinctive, naming concrete import/inspect/narrate/TTS actions in a clear niche. It is capped on completeness because it lacks an explicit 'Use when…' trigger clause, relying on implied timing instead.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to import an uploaded .pptx into an already-created class while keeping the original layout.'

Lead with a natural user-spoken trigger phrase (e.g. '导入PPT成课') before the workflow detail so the 'when' is immediate.

Trim the embedded workflow detail (create_stage→import_pptx ordering) from the description; it belongs in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'create_stage 建课', 'import_pptx 把页面追加', '逐页检查…并修 bad case', '写旁白/spotlight', '最后 TTS', '插入 quiz 或 interactive' — giving comprehensive coverage of the import workflow.	5 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when…' trigger clause; the 'when' is only weakly implied via '会话里有上传的 .pptx，且用户要把这份幻灯片填进一节已建的课', which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural domain terms appear (上传的 .pptx, 幻灯片/PPT/.pptx, quiz, interactive, TTS, 旁白/spotlight) with useful synonyms, but phrasing is workflow-internal rather than pure user-spoken triggers and a few common variations are missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche — importing an uploaded .pptx into a created stage while preserving layout and explicitly not replanning — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 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/pptx-import/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.