CtrlK
BlogDocsLog inGet started
Tessl Logo

slide-authoring

Technical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette/visual direction, assets, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides/<id>/`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like "edit slide", "tweak this page", "fix the layout", "change the palette", "reveal one by one", "add a transition", "morph transition", "investigate the slide framework", "how do slides work here".

74

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality technical reference: executable templates, explicit validation checkpoints, and clean one-level-deep reference navigation. The only weakness is conciseness — the body is long and a few explanatory passages could be trimmed without losing clarity.

Suggestions

Tighten the 'Repeated elements: component, not map' section: the rationale after the two code blocks ('The inspector edits source JSX in place…') repeats the problem statement and could be cut to one sentence.

Consider compressing 'Runtime behavior you get for free' to a single line or moving it to a reference, since most items (home page listing, arrow-key nav, hot reload) are standard behavior Claude can infer.

The vertical-budget worked example is justified, but the surrounding prose ('This is the #1 cause of broken slides — assume you will overflow unless you've checked') could be trimmed to the rule plus the table.

DimensionReasoningScore

Conciseness

Mostly efficient and largely free of general-concept padding, but at ~350 lines some rationale runs longer than needed (e.g. the multi-paragraph 'component, not map' justification and the 'Runtime behavior you get for free' list) and could be tightened, matching the 'mostly efficient but could be tightened' anchor rather than the lean top anchor.

2 / 3

Actionability

Provides copy-paste-ready executable artifacts — a full starter template, the file contract TSX, type-scale/spacing tables, a grep location command, and a worked vertical-budget arithmetic table — fully concrete and executable.

3 / 3

Workflow Clarity

Multi-step operations are clearly sequenced with explicit validation checkpoints, notably a 15-item 'Self-review before finishing' checklist and a 'run node -e … and paste the exact output' gate before writing the file, plus the vertical-budget verify-before-write rule.

3 / 3

Progressive Disclosure

Serves as a clear overview with a well-signaled, one-level-deep 'Primitive references' table mapping each primitive to a real references/*.md file (all 7 verified to exist) with 'Read before' guidance; detail is appropriately pushed into those files rather than nested deeper.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities, gives explicit when-to-use guidance with natural trigger phrases, and carves out a distinct niche with explicit boundary-setting against sibling skills. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names concrete, specific actions/topics — 'file contract, 1920×1080 canvas, type scale, layout, palette/visual direction, assets, stepped reveals, page transitions, and morph transitions' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (technical reference for writing/editing open-slide pages) and 'when' ('Consult this whenever you are about to write or modify any file under slides/<id>/…' plus a Triggers clause), matching the top anchor.

3 / 3

Trigger Term Quality

Provides natural phrases users would say — 'edit slide', 'tweak this page', 'fix the layout', 'change the palette', 'reveal one by one', 'add a transition', 'morph transition' — giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (open-slide pages under slides/<id>/) with slide-specific triggers and explicit disambiguation from create-slide, apply-comments, and current-slide, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
1weiho/open-slide
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.