CtrlK
BlogDocsLog inGet started
Tessl Logo

page-clone

Building one page that looks like a page the course already has — copy the model page with `duplicate_scene`, then rewrite the copy's words with one `patch_stage` op per content slot. Use when a new page has to inherit an existing page's design, whether the model page came from an imported deck or the course wrote it earlier. Not for revising a page that is already the page you want (that is `pro-editing`), and not for the course-level work of cataloguing layouts and assigning one per outline entry (that is `style-clone`).

71

Quality

89%

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

88%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 high-quality, actionable body: concrete tool calls and paths, an explicit validated workflow, and clean deferral to sibling skills for deeper detail. Marginal gains remain in trimming rationale prose and possibly externalizing the decision table.

DimensionReasoningScore

Conciseness

Dense, operational prose that assumes competence and never explains basic concepts; a few rationale passages ("Three properties make this safe to lean on") and the large decision table could be trimmed slightly, keeping it just below a 5.

4 / 5

Actionability

Provides exact tool signatures (`duplicate_scene({ templateSceneId, targetOrder, title })`), exact patch paths (`/content/canvas/elements/N/content`), and a 12-row decision table mapping each need to a specific call — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

A clear 6-step numbered sequence with explicit validation (the `detail:"text"` sweep in step 5 and the "Always run the text sweep" hard rule), feedback loops for residue repair, and a Hard rules checklist — validation is present so no destructive-cap applies.

5 / 5

Progressive Disclosure

Well-sectioned single file with a "Where this sits" block that clearly signals one-level references to sibling skills ("Load it when..."); not a 5 because the bundle is monolithic with a dense inline table rather than split across referenced files.

4 / 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, specific description that states what the skill does, when to use it, and where its boundaries are against neighboring skills. The only soft spot is trigger-term breadth, which leans on the title for synonyms like "clone".

DimensionReasoningScore

Specificity

Names two concrete, tool-backed actions — "copy the model page with `duplicate_scene`" and "rewrite the copy's words with one `patch_stage` op per content slot" — which fully cover the clone task; not a 5 because the list of distinct actions is short rather than comprehensive.

4 / 5

Completeness

Explicitly answers both halves — the "what" (copy with `duplicate_scene`, rewrite words with `patch_stage` per slot) and the "when" ("Use when a new page has to inherit an existing page's design") — with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural phrases like "looks like a page the course already has", "copy the model page", and "inherit an existing page's design" map to what a user would say; not a 5 because synonyms such as "clone" or "duplicate a slide" appear only via the title, not the body.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche and explicitly disambiguates from siblings ("Not for revising a page... that is `pro-editing`", "not for the course-level work... that is `style-clone`"), giving minimal conflict risk.

5 / 5

Total

18

/

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