CtrlK
BlogDocsLog inGet started
Tessl Logo

square-1-1-layout-skill

Must be read before creating, relaying out, or repairing 1:1 square Oh My PPT pages. Defines square-card layout, centered focal hierarchy, quadrant and orbit structures, balanced margins, data-card budgeting, plus catalog and checklist references for 1200x1200 canvases.

75

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

100%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, token-efficient layout skill that provides concrete specs and a clear preflight-to-delivery workflow with an explicit self-check checkpoint. Detail is correctly offloaded to two real one-level-deep reference files, making navigation easy.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: it assumes Claude knows HTML/Tailwind and gives only earned, domain-specific guidance (e.g. concrete px floors and Tailwind class equivalents) without padding or explaining basic concepts.

3 / 3

Actionability

Highly concrete, executable guidance for an instruction-only skill — specific px floors (24px body, 32px headings, 16px auxiliary), exact Tailwind classes, budget numbers (64-112px padding, 40-96px bottom band), and named patterns to apply.

3 / 3

Workflow Clarity

Clear sequenced process — Preflight (7 steps) → Canvas Grammar → Pattern lookup → Square Budget (6 steps) → Repair/self-check — with an explicit validation checkpoint ('Before delivery, run references/checklist.md') and condition→fix feedback loops in the Repair section.

3 / 3

Progressive Disclosure

Body is a tight overview that delegates detail to two real, one-level-deep, well-signaled references — references/catalog.md (pattern recipes) and references/checklist.md (P0/P1/P2 self-check) — both confirmed to exist, with content appropriately split rather than inlined.

3 / 3

Total

12

/

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 description that names concrete capabilities and an explicit use trigger for a well-scoped niche. Its main weakness is trigger-term naturalness: the product jargon ('Oh My PPT', 'relaying out') is less likely to match a user's plain phrasing.

Suggestions

Add plain-language trigger variants a user would actually say (e.g. 'Use when making a square (1:1) slide or page, or fixing an off-balance square card') alongside the product terms.

Soften or gloss 'relaying out' — it is unusual phrasing; 're-laying out' or 'rebuilding the layout' reads more naturally.

Keep the concise capability list but consider pairing 'Oh My PPT' with the generic term ('square presentation pages') so the trigger matches users who don't name the product.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Defines square-card layout, centered focal hierarchy, quadrant and orbit structures, balanced margins, data-card budgeting' — matching the anchor for several specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers what ('Defines square-card layout, centered focal hierarchy...') and provides equivalent explicit trigger guidance ('Must be read before creating, relaying out, or repairing 1:1 square Oh My PPT pages'), satisfying the 'Use when...' requirement rather than capping at 2.

3 / 3

Trigger Term Quality

Contains relevant domain keywords ('1:1 square Oh My PPT pages', 'square-card layout', '1200x1200 canvases', 'creating, relaying out, or repairing') but the phrasing is product-jargon heavy ('Oh My PPT', 'relaying out') and misses plain common variations a user might say like 'square slide' or 'make a square page'.

2 / 3

Distinctiveness Conflict Risk

A clear narrow niche — 1:1 square PPT pages on 1200x1200 canvases — with distinct triggers unlikely to fire for non-square or non-PPT skills.

3 / 3

Total

11

/

12

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.