CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

oh-my-ppt-chart

Must be read before adding or modifying Oh My PPT slide charts. Defines chart-selection rules, product-safe Chart.js usage, canvas layout constraints, axis label rules, and retry fixes.

Quality

81%

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

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.

The body is highly actionable with executable templates, concrete numbers, checklists, and a repair loop, organized into clear sections with a well-signaled one-level reference. Its weaknesses are repetition of the height-match rule across multiple sections and overlap between inline examples and the reference file.

Suggestions

State the height-calc comment / h-[Npx] match rule once (in Hard rules) and reference it elsewhere instead of repeating it in the HTML section, the example block, and the hard-rules list.

Move the bad-pattern examples and one of the duplicated complete HTML examples into references/chart.md, keeping only a minimal template inline in SKILL.md.

Define or inline the "layout width/height self-check" referenced in calculation step 10, or point to the exact section of the layout skill that specifies it, to close the workflow validation gap.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but the comment/frame height-match rule is restated at least four times (e.g. "The final number in the comment and h-[Npx] MUST match", "Do NOT write a comment that ends with one number and a frame height that uses another number", and again in Hard rules), and three near-complete HTML example blocks repeat the same template. This fits the mostly-efficient-but-could-be-tightened anchor rather than anchor 2, since the redundancy is domain-specific rule reinforcement rather than generic padding.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance: complete PPT.createChart script with DOMContentLoaded wrapper, exact height-calc comment template with the @ppt-chart-height=N marker, concrete pixel arithmetic (p-6=48, gap-6=24, 24-40px reserve), a complete working example, and a diagnostic repair checklist. This clearly matches the fully-executable anchor with common cases covered.

5 / 5

Workflow Clarity

A 9-step ordered decision checklist, a 10-step height calculation procedure, and a failure-repair sequence provide a clear sequence with most checkpoints and an error-recovery loop. It falls short of anchor 5 because step 10 references a "layout width/height self-check" that is never defined in this skill, and there is no explicit post-creation validation step.

4 / 5

Progressive Disclosure

The single reference (references/chart.md) is real, one level deep, and clearly signaled at the top with its contents enumerated (chart selection, frame height guide, category axis patterns, layout integration tips). It misses anchor 5 because ~220 lines of inlined material, including bad-pattern examples and a complete working example, overlap sections that also live in the reference file and could be split out.

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.

The description is specific, third-person, and clearly scoped to a niche domain with explicit when-guidance. Its main gaps are the missing repair trigger in the when-clause and absent common synonyms like "graph" or "data visualization".

Suggestions

Extend the when-clause to cover repair triggers, e.g. "Must be read before adding, modifying, or repairing Oh My PPT slide charts (including blank or broken chart canvases)".

Add natural synonym terms users might say, such as "graph", "data chart", or "chart animation", to broaden trigger coverage.

State the core actions performed (create, modify, repair charts) alongside the list of defined rules to strengthen action specificity.

DimensionReasoningScore

Specificity

"Defines chart-selection rules, product-safe Chart.js usage, canvas layout constraints, axis label rules, and retry fixes" lists five concrete capability areas, matching the anchor for several specific actions with minor gaps. It falls short of 5 because these are defined topic areas rather than performed actions, and repair/creation actions are only implied by "adding or modifying".

4 / 5

Completeness

Both what ("Defines chart-selection rules, ... retry fixes") and when ("Must be read before adding or modifying Oh My PPT slide charts") are explicitly present, satisfying the trigger-guidance requirement. It falls between anchors 4 and 5 rather than clearly at 5 because the when-clause omits repair scenarios even though "retry fixes" appears in the what, so the trigger guidance could be more exhaustive.

4 / 5

Trigger Term Quality

Natural trigger terms like "slide charts", "Chart.js", "axis label", and "canvas" give good keyword coverage a user would plausibly say. Missing common synonyms such as "graph", "data visualization", or "blank/broken chart" keeps it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Oh My PPT slide charts" combined with "Chart.js" establishes a clear niche with distinct triggers and minimal overlap risk with generic presentation or document skills. This clearly matches the anchor for a distinct niche rather than the mostly-distinct anchor 4.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

arcsin1/oh-my-ppt

Path

resources/skills/oh-my-ppt-chart/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.