CtrlK
BlogDocsLog inGet started
Tessl Logo

standard-4-3-layout-skill

Must be read before creating, relaying out, or repairing standard 4:3 Oh My PPT pages. Defines square-ish presentation layout, two-zone and 2x2 structures, chart/table budgeting, column discipline, plus catalog and checklist references for 1600x1200 canvases.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/skills/standard-4-3-layout-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-organized, actionable layout spec that assumes Claude's competence and delegates detail to verified one-level references. It is one step short of top marks because repair lacks an explicit validate-retry loop and the overview/catalog boundary has minor overlap.

Suggestions

Add an explicit feedback loop to the Repair section: after applying a fix, re-run references/checklist.md and iterate until P0 items pass, mirroring the validate-fix-retry pattern.

Tighten the prefatory lines ('This skill is the layout source of truth...square-ish') to avoid restating the square-ish framing already in the frontmatter.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's knowledge; only minor padding such as restating the 'square-ish' framing twice and the prefatory 'This skill is the layout source of truth' could be trimmed.

4 / 5

Actionability

Concrete and executable throughout — exact px floors (24/21/32/16), Tailwind class mappings, an explicit budget arithmetic sequence, and a pattern lookup table — with only minor gaps (no literal HTML snippet, but the spec is instruction-oriented so code absence is not penalized).

4 / 5

Workflow Clarity

The Preflight sequence and Height/Width Budget steps are clearly ordered, and the Repair section plus checklist reference provide checkpoints, but there is no explicit validate-then-retry feedback loop for repair iterations.

4 / 5

Progressive Disclosure

Good one-level-deep structure: body stays an overview and clearly signals two real reference files (catalog.md, checklist.md), both verified to exist; minor gap is that pattern quick-lookup and catalog entries overlap rather than being cleanly partitioned.

4 / 5

Total

16

/

20

Passed

Description

78%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 specific, domain-anchored description with clear trigger framing and low conflict risk. It loses a point on completeness for the imperative phrasing instead of a natural 'Use when' clause and on trigger coverage for missing common synonyms like 'slides' or 'presentation'.

Suggestions

Replace the imperative 'Must be read before...' with a natural 'Use when creating, relaying out, or repairing standard 4:3 presentation slides' clause to satisfy the trigger completeness anchor.

Add common-synonym keywords a user would actually say — 'presentation', 'slides', 'talk-track slides' — so the description surfaces for natural phrasings.

DimensionReasoningScore

Specificity

Lists several specific concrete actions ('creating, relaying out, or repairing', 'chart/table budgeting, column discipline') plus catalog/checklist references, with minor coverage gaps around styling.

4 / 5

Completeness

Has a clear 'what' (defines layout, structures, budgeting) and a trigger condition ('Must be read before creating, relaying out, or repairing...'), but the 'when' is phrased as an imperative rather than a natural 'Use when' clause.

4 / 5

Trigger Term Quality

Strong natural terms ('4:3 pages', '1600x1200', 'standard 4:3') but missing common synonyms a user might say like 'presentation', 'slides', or 'PowerPoint'.

4 / 5

Distinctiveness Conflict Risk

The 4:3 / 1600x1200 / Oh My PPT niche is clearly distinct with specific triggers, so it is unlikely to fire for the wrong skill.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
arcsin1/oh-my-ppt
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.