CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pro-editing

Professional editing of a course that already exists. Use when the user wants to revise, improve, restructure or polish pages the course already has — fix a page, tune a layout, repair a quiz, reword narration, reorder the deck, or raise the quality of the whole course. Not for building a new course from scratch.

Quality

93%

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

92%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 operationally excellent skill body: exact tool semantics, pointer-level paths, a decision matrix mapping user intent to operation, explicit error-recovery loops and a closing validation checklist. Its only weakness is mild redundancy — the read-before-write discipline and preview budget are each repeated across sections and could be consolidated.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific facts Claude could not know (exact JSON pointer paths, `detail:"source"` pagination at 12,000 characters, `add_element` inserting at `afterId` or `index`) with essentially no general-knowledge padding. It edges below the top anchor because the read-fresh-before-write discipline is restated across "Read before every change", "Read fresh, then write" and the closing pass, and the preview budget appears in both "Look → edit → look, on a budget" and "Budget".

4 / 5

Actionability

Guidance is fully executable: concrete tool calls with exact parameters (`read_stage path:/scenes/<order|id>` with `detail:"source"`, `str_replace` on decoded field values), exact pointer paths (`/content/canvas/elements/N/content`, `/actions/N/text`, `/content/questions/...`), and an intent-to-operation matrix covering the common edit cases. Per the rubric's instruction-skill note, absence of code blocks is not penalized when the guidance is this concrete.

5 / 5

Workflow Clarity

The sequence is coherent and complete: enter with `list_scenes`, `read_stage` before every write, the smallest-operation matrix, budgeted `render_scene_preview` verification, `generate_tts` after speech rewording, and a numbered consistency-pass checklist. Explicit feedback loops for this destructive, shared-editing context are present — "A rejected patch changed nothing... Re-read and resubmit; never force" and anchor-rejection recovery via the returned diagnostic.

5 / 5

Progressive Disclosure

No bundle files exist to organize; the deep reference material is correctly deferred to named sibling skills with explicit load conditions — "load `slide-craft`" for the design law and "that is `slide-dsl`" for field semantics — one level deep and clearly signaled. The body keeps only the operational core, well-sectioned with headers, a decision matrix and checklists for easy navigation.

5 / 5

Total

19

/

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 description: it states what the skill does with a comprehensive list of concrete editing actions, gives an explicit "Use when" trigger clause with natural user phrasings, and closes with a clear negative boundary against building a new course. The only gap is a few natural trigger synonyms (update, change, modify) that users might say.

DimensionReasoningScore

Specificity

The description lists multiple distinct concrete actions — "fix a page, tune a layout, repair a quiz, reword narration, reorder the deck" — covering text, layout, quiz, narration and deck structure across the editing domain. Only "raise the quality of the whole course" is generic; the action coverage still matches the comprehensive anchor rather than the minor-gaps anchor one level below.

5 / 5

Completeness

Both questions are answered explicitly: "Professional editing of a course that already exists" plus the action list states what, and "Use when the user wants to revise, improve, restructure or polish pages the course already has" states when with concrete trigger phrases. The negative boundary "Not for building a new course from scratch" makes the scope even more explicit than the anchor-5 example.

5 / 5

Trigger Term Quality

Natural phrases users would say are present — "revise", "improve", "polish", "fix a page", "reword narration", "reorder the deck", plus "editing" itself. However common variations like "update", "change" or "modify" a course/page are absent, so coverage is good but not the comprehensive synonym coverage of the top anchor.

4 / 5

Distinctiveness Conflict Risk

The persisted-course framing ("editing of a course that already exists", "pages the course already has") and the explicit exclusion "Not for building a new course from scratch" carve a clear niche separate from any course-creation skill. Trigger terms (fix a page, repair a quiz, reorder the deck) are specific to this niche, giving minimal conflict risk.

5 / 5

Total

19

/

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

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/pro-editing/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.