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

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 highly actionable, well-sequenced skill with clear progressive disclosure to a real reference file and explicit feedback loops for the fragile chart-rendering operation. Its main weakness is verbosity from restated height-calculation rules and overlapping sections.

Suggestions

Collapse the repeated height-matching constraint into a single canonical statement; the rule that the comment number and h-[Npx] must agree currently appears in three near-identical forms.

De-duplicate guidance across the '30-second decision checklist', 'How to create a chart', 'Hard rules', and 'Failure repair' sections, which restate overlapping requirements (e.g. DOMContentLoaded, plain-string labels).

Tighten the column-budget and support-budget paragraphs, which re-explain the 'columns share width, not height' rule in two consecutive sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and assumes Claude's competence (no 'what is a chart' filler), but the height-calculation constraints are restated multiple times ('The final number in the comment and h-[Npx] MUST match' appears in several near-duplicate forms) and the checklist, 'How to create', 'Hard rules', and 'Failure repair' sections overlap, so it could be tightened.	3 / 5
Actionability	Provides copy-paste-ready HTML and JavaScript (exact chart-frame markup, a complete working bar-chart example, exact API signature PPT.createChart(canvasElement, config), exact DOMContentLoaded event, and concrete bad-pattern counter-examples) covering the common cases fully.	5 / 5
Workflow Clarity	Sequences the work with an ordered 9-step decision checklist, a numbered 10-step height-calculation procedure, and an explicit failure-repair feedback loop (check event → check id → check height → check data → remove duplicate scripts) with checklists for a fragile rendering operation.	5 / 5
Progressive Disclosure	SKILL.md acts as a structured overview while the deep-dive (chart-selection examples, frame-height guide, category-axis patterns, layout integration) is clearly signaled and one level deep in references/chart.md, which exists as a real bundle file.	5 / 5
	Total	18 / 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, well-scoped description that clearly communicates both its purpose and its read-trigger, anchored to a distinct product+domain niche. It could be strengthened by converting the single 'Defines' verb into explicit actions and adding a 'Use when...' clause with concrete trigger synonyms.

Suggestions

Reframe the 'what' as explicit verbs/actions (e.g. 'Select chart types, write product-safe Chart.js code, size chart canvases, format axis labels, and repair blank canvases') to push specificity toward 5.

Add a 'Use when...' clause with concrete trigger phrases (e.g. 'Use when adding, modifying, or repairing slide charts, bar/line/pie graphs, or broken Chart.js canvases') to raise completeness and trigger-term quality.

Include common synonyms and file/extension terms users might say ('graph', 'broken chart', 'blank canvas') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates several concrete capability domains ('chart-selection rules, product-safe Chart.js usage, canvas layout constraints, axis label rules, and retry fixes'), but frames them as a single verb ('Defines') with noun objects rather than multiple distinct actions, leaving it just short of fully comprehensive verb-action coverage.	4 / 5
Completeness	Both 'what' (the rules it defines) and 'when' ('Must be read before adding or modifying Oh My PPT slide charts') are present and explicit, but the 'when' is a precondition rather than a 'Use when...' clause enumerating concrete trigger phrases, so it falls short of the highest anchor.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('adding or modifying', 'Oh My PPT slide charts', 'Chart.js'), but misses common synonyms and variations like 'graph', 'bar/pie chart', 'broken/blank chart', or 'axis labels'.	4 / 5
Distinctiveness Conflict Risk	The product-scoped 'Oh My PPT' combined with the chart-specific 'Chart.js' domain carves a clear niche with distinct triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	17 / 20 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-chart/SKILL.md
Commit: 6d1b08b

Reviewed: 1 day 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.