CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vertical-9-16-layout-skill

Must be read before creating, relaying out, or repairing 9:16 vertical Oh My PPT pages. Defines mobile-story layout, top/middle/bottom zone planning, vertical flow patterns, height budgeting, readable chart/list composition, plus catalog and checklist references for 900x1600 canvases.

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

86%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-structured instruction-only skill with highly concrete, executable design tokens and a clear preflight-to-repair workflow backed by real one-level-deep references. Minor gains available from deduplicating the composition guidance and tightening the verbose repair paragraph.

Suggestions

Deduplicate the composition starting point: state the 2-3 module / 4-5 list-row starting point once (Canvas Grammar) and have Preflight item 3 reference it, trimming several lines.

Tighten the bolded density-resolution paragraph in "Repair And Self-check" into a compact numbered priority list to cut repetition and token cost.

Add one explicit post-write validation checkpoint in the body (e.g., "after writing, verify total height budget stays within canvas before running the checklist") so the validation loop is inline rather than fully delegated to references/checklist.md.

DimensionReasoningScore

Conciseness

Efficient, project-specific guidance (px floors, density markers, zone rules) that assumes Claude's competence and avoids generic explanations, but the composition starting point is stated twice (Preflight item 3/5 and the Canvas Grammar bullet) and the bolded density-resolution paragraph in Repair could be tightened.

4 / 5

Actionability

Fully concrete, copy-paste-ready guidance: exact px values ("at least 32px", "43px", "21px"), exact class/style tokens ("flex flex-col", "flex-1", "data-ppt-density=\"high\"", "@ppt-chart-height=N" aligned with "h-[Npx]"), numeric budget ranges (e.g., "180-360px" hook zone), and a pattern lookup table.

5 / 5

Workflow Clarity

Clear sequencing (numbered Preflight, numbered Height Budget calculation, prioritized density-resolution ladder) with a delivery checklist reference and if-then repair loops, but the inline validation checkpoints are heuristic cues ("if the page feels top-heavy") and the concrete pass/fail checks are delegated to the external checklist rather than stated as explicit checkpoints in the flow.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with deep details correctly split into two one-level-deep references ("references/catalog.md - named vertical story patterns", "references/checklist.md - P0/P1/P2 structural self-check"), both real files, clearly listed up front and referenced again at point of use (Pattern Quick Lookup, Repair).

5 / 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, niche-specific description that explicitly covers both what the skill provides and when to use it, with concrete capability keywords. Minor deductions for the "relaying out" typo and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("top/middle/bottom zone planning", "vertical flow patterns", "height budgeting", "readable chart/list composition") plus concrete actions ("creating, relaying out, or repairing"), but "Defines..." phrasing is more a content inventory than action statements, and "relaying out" is a typo that muddies one action.

4 / 5

Completeness

Explicitly answers both: what ("Defines mobile-story layout, top/middle/bottom zone planning, vertical flow patterns, height budgeting, readable chart/list composition") and when ("Must be read before creating, relaying out, or repairing 9:16 vertical Oh My PPT pages") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("9:16", "vertical", "PPT pages", "900x1600", "layout", "mobile-story"), but common synonyms like "portrait", "phone-screen", or "story slide" are missing.

4 / 5

Distinctiveness Conflict Risk

"9:16 vertical Oh My PPT pages" and "900x1600 canvases" carve out a clear niche with distinct triggers; minimal overlap risk with general presentation or layout skills.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

arcsin1/oh-my-ppt

Path

resources/skills/vertical-9-16-layout-skill/SKILL.md

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.