oh-my-ppt-layout

Must be read before creating, relaying out, or repairing Oh My PPT slide layouts. Defines the per-page decision path, the named layout pattern catalog, canvas budgeting, collision avoidance, chart overpack guardrails, and title readability rules.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

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

A well-structured, actionable layout skill with clear sequenced workflows and excellent progressive disclosure into three real reference files. The primary weakness is conciseness: guidance is repeated across sections and could be consolidated.

Suggestions

Consolidate the chart-height guidance that recurs in §1, §4, §5, and §10 into a single authoritative section and cross-reference it, to reduce redundancy.

Tighten §7 by merging overlapping strategies and trimming restated principles already covered in §4 and §5.

Consider extracting the repeated canvas/spacing numeric rules into a compact reference table to let the body stay lean.

Dimension	Reasoning	Score
Conciseness	Content is substantive domain guidance rather than concepts Claude already knows, but it is verbose with notable repetition — chart-height guidance recurs across §1, §4, §5, and §10, and §7 is long. Not a 3 because of redundancy and padding that could be tightened; not a 1 because it does not explain basic concepts Claude knows.	2 / 3
Actionability	Provides concrete, executable specifics: exact canvas 1600×900, pixel floors (18px body, 24px heading, 12px auxiliary), named Tailwind classes, chart height ranges (380–560/280–360/220–280px), and the @ppt-chart-height=N marker. Not a 2 because guidance is specific and copy-ready rather than pseudocode or vague direction.	3 / 3
Workflow Clarity	The §1 decision path is a numbered 0–7 sequence with an explicit validation checkpoint ("If either dimension exceeds the canvas, redesign the composition and check again"), backed by a referenced P0/P1/P2 checklist. Not a 2 because validation and feedback loops are explicit rather than missing.	3 / 3
Progressive Disclosure	The body is an overview that signals three real one-level-deep references (catalog.md, layout.md, checklist.md) with their contents named inline; no nested 2+ level reference chains exist. Not a 2 because references are clearly signaled and content is appropriately split rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

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, third-person description that names concrete capabilities and an explicit trigger condition tied to a distinct niche. Its main weakness is trigger-term quality: it relies on internal jargon and omits a natural "Use when…" phrasing.

Suggestions

Add an explicit "Use when…" clause with natural phrasing such as 'Use when creating, re-laying out, or repairing slide layouts' to lift trigger-term quality.

Translate internal jargon (e.g. 'chart overpack guardrails', 'canvas budgeting') into terms a user would actually say, like 'fitting charts and content on a slide'.

Surface common synonyms users might say (e.g. 'slide design', 'slide overflow', 'fixing broken slides') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "per-page decision path, the named layout pattern catalog, canvas budgeting, collision avoidance, chart overpack guardrails, and title readability rules" — matching the anchor for listing multiple specific concrete actions. Not a 2 because the actions are named concretely rather than covering only a domain and some actions.	3 / 3
Completeness	Answers what (decision path, catalog, budgeting, guardrails, readability rules) and when explicitly ("before creating, relaying out, or repairing Oh My PPT slide layouts") in third-person imperative voice. Not a 2 because the when is explicitly stated rather than only implied.	3 / 3
Trigger Term Quality	Includes some natural triggers ("creating, relaying out, or repairing... slide layouts") but leans on internal jargon ("canvas budgeting", "chart overpack guardrails") and offers no explicit "Use when…" clause. Not a 3 because natural-term coverage is incomplete; not a 1 because several user-facing trigger words are present.	2 / 3
Distinctiveness Conflict Risk	Tied to the specific "Oh My PPT slide layouts" niche with distinct creation/repair triggers, unlikely to fire for unrelated skills. Not a 2 because the niche and triggers are clearly distinguishable rather than merely somewhat specific.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: arcsin1/oh-my-ppt
Path: resources/skills/oh-my-ppt-layout/SKILL.md
Commit: d2046bf

Reviewed: 11 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.