html-ppt-zhangzara-studio

A photography studio's portfolio-and-rate deck — the signature work, the process, and the packages that win the brief. Built as a decision-grade design craft deck for prospective clients.

Quality

65%

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-zhangzara-studio/SKILL.md

Quality

Content

80%

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

A lean, actionable, well-structured template skill: concise sections, concrete workflow steps, and an explicit output contract. Its weak spots are the absence of any validation/verification checkpoint in the workflow and references to bundle files that are not actually present.

Suggestions

Add a verification step to the workflow (e.g., open the emitted HTML to confirm the keyboard navigation handler and decorative system render intact before delivering).

Ship the referenced bundle files (`example.html`, `template.json`, `LICENSE`, and any `assets/deck-stage.js`) so the signaled links resolve, or remove references to files that are not vendored.

Make the output contract explicit about which slide layouts the demo ships (referenced as "12 slides in demo") so duplication in step 4 is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned with no concept-explanation padding (no "what is HTML" filler); lines like "Black canvas with electric-yellow type; high-voltage design studio aesthetic" and "Mixing layouts across templates breaks the system; stay inside this one" each earn their place, matching the lean anchor 3.	3 / 3
Actionability	Concrete, specific guidance throughout — "Clone `example.html`", "Replace placeholder content", "duplicate an existing slide of the most appropriate layout", "design it from scratch using the same fonts, palette, decorative vocabulary" — plus an explicit output contract with an `<artifact>` example; for an instruction-only skill this is fully actionable.	3 / 3
Workflow Clarity	The Workflow is a clear numbered sequence (steps 1–6) but contains no validation or verification checkpoint (e.g., confirm the deck renders or the runtime handler is intact), matching "steps listed but validation gaps; checkpoints missing or implicit."	2 / 3
Progressive Disclosure	Sections are well-organized and references are signaled one level deep via markdown links, but the referenced files (`./LICENSE`, `template.json`, `example.html`, `assets/deck-stage.js`) are absent from the bundle, so the signaled navigation does not actually resolve.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 clear niche and the deck's content components but is noun-heavy and lacks explicit "Use when..." trigger guidance. It sits at the midpoint across all dimensions: specific enough to be useful, not distinctive or trigger-complete enough to score high.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., "Use when building a photography or creative-studio portfolio, rate card, or pitch deck in HTML").

Lead with concrete actions Claude takes (e.g., "Builds, layouts, and writes a studio portfolio-and-rate deck...") rather than only describing the artifact.

Add common natural variations users would say ("rate card", "price sheet", "creative deck", "HTML slides") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete content components — "portfolio-and-rate deck", "the signature work, the process, and the packages" — but uses noun phrases describing the artifact rather than listing multiple concrete actions Claude performs, so it does not reach the verb-driven anchor 3.	2 / 3
Completeness	It clearly answers "what" (a portfolio-and-rate deck built for prospective clients) but provides no "Use when..." clause or equivalent trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Contains some natural niche terms ("portfolio", "rate deck", "design craft", "studio", "prospective clients") but lacks common variations and there is no explicit trigger phrasing, matching "some relevant keywords but missing common variations."	2 / 3
Distinctiveness Conflict Risk	The "photography studio's portfolio-and-rate deck" niche is fairly specific, but the broader framing ("design craft deck", "decision-grade") could overlap with other design/deck skills, matching "somewhat specific but could still overlap."	2 / 3
	Total	8 / 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: 1 missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/html-ppt-zhangzara-studio/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.