html-ppt-graphify-dark-graph

Open Design's feature business case for the plugin marketplace: the user pain, options, tradeoffs, and the measure of success. Built as a decision-grade product management deck for PM, eng, design, leadership.

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./design-templates/html-ppt-graphify-dark-graph/SKILL.md

Quality

Content

72%

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

The content is highly actionable with concrete copy-and-rewrite recipes and well-organized one-level-deep references, but it pads some explanations and lacks an explicit verification step for the fragile asset-URL fix. Tightening prose and adding a deck-loads validation checkpoint would raise the weaker dimensions.

Suggestions

Trim explanatory padding like 'meaning the deck never activates and slide navigation is dead' and 'Yields a single self-contained index.html' to keep every token load-bearing.

Add an explicit verification checkpoint after the URL rewrite, e.g., 'Open index.html and confirm slide navigation (arrows/space) works before shipping' — this is a fragile operation that warrants a validate-then-proceed loop.

Optional: collapse Recipe A and B into a tighter 'copy+rewrite (preferred) or inline' pair to reduce token weight while preserving both options.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and procedural, but includes explanatory padding such as 'meaning the deck never activates and slide navigation is dead' and 'Yields a single self-contained index.html' that could be trimmed without losing guidance.	2 / 3
Actionability	It gives concrete file paths, exact copy commands, and two copy-paste-ready recipes that rewrite specific <link>/<script> tags from '../../../assets/...' to project-local paths — fully executable guidance.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced and surface the 404 pitfall, but for a fragile HTML-asset operation there is no explicit validation checkpoint (e.g., verifying the deck loads and navigation works), which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The ~50-line body is well-organized into focused sections with clearly signaled one-level-deep pointers to the master skill (../html-ppt/SKILL.md, ../html-ppt/references/full-decks.md); no local bundle files exist to complicate navigation.	3 / 3
	Total	10 / 12 Passed

Description

60%

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 conveys a specific PM-deck purpose with concrete content elements, but omits an explicit 'Use when...' trigger clause and relies on somewhat domain-heavy language. Adding natural user-spoken triggers would lift the weaker dimensions.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when writing a feature business case, product ROI argument, or feature proposal deck').

Add common natural trigger variations a user would actually say, such as 'business case', 'feature proposal', 'go/no-go decision', rather than only 'decision-grade product management deck'.

State the when-context explicitly (e.g., 'Use when a PM needs a decision-grade deck to align PM, eng, design, and leadership on a feature investment') to improve completeness and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names multiple concrete content elements — 'the user pain, options, tradeoffs, and the measure of success' — and a specific deck audience, matching the anchor for listing several specific concrete actions rather than a vague domain.	3 / 3
Completeness	It clearly states what the skill produces, but provides no explicit 'Use when...' trigger clause, so the 'when' is only implied — capping completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Relevant PM terms like 'feature business case' and 'plugin marketplace' appear, but phrasing leans toward domain jargon ('decision-grade product management deck') and misses common natural variations a user would say.	2 / 3
Distinctiveness Conflict Risk	The plugin-marketplace business-case niche is somewhat specific, but without explicit distinct triggers it could still overlap with generic PM or presentation skills.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 suspicious	Warning
referenced_paths_exist	Referenced path issues: 5 missing, 2 deeper-than-1-level	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-graphify-dark-graph/SKILL.md
Commit: f2760fd

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