html-ppt-zhangzara-biennale-yellow

A curatorial deck for a contemporary art biennale — the thesis, the rooms, the works, and the visitor journey. Built as a decision-grade design craft deck for museum board, curators.

Quality

57%

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-biennale-yellow/SKILL.md

Quality

Content

65%

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

The body is concise, well-structured, and gives concrete file-level workflow guidance with a clear output contract. It falls short on actionability (no executable code or complete example), lacks validation checkpoints in the workflow, and references bundle files that are absent from the skill.

Suggestions

Add a minimal concrete HTML snippet or a real (trimmed) slide skeleton so the Output contract is copy-paste ready rather than a `<html>...</html>` placeholder.

Insert a validation/verification step in the Workflow (e.g., open the cloned `example.html` in a browser, confirm fonts/palette and page-number labels are intact before delivering).

Ship the referenced bundle files (`example.html`, `LICENSE`, `template.json`, any `assets/` runtime) alongside SKILL.md so the signaled references resolve.

Dimension	Reasoning	Score
Conciseness	The body is lean and skill-specific — "At a glance" metadata, Best for/Avoid for, a numbered Workflow, and an Output contract — with no padding explaining concepts Claude already knows, so every section earns its place.	3 / 3
Actionability	The workflow gives concrete file-level guidance ("Clone `example.html`", "Keep the `assets/deck-stage.js`…runtime") and a concrete artifact wrapper, but offers no executable code or complete HTML example — the Output contract uses a `<html>...</html>` placeholder — and "design it from scratch" is somewhat abstract.	2 / 3
Workflow Clarity	The six workflow steps are clearly numbered and sequenced, but there are no validation or verification checkpoints (e.g., confirm the deck renders, fonts load, or page-number labels updated), so checkpoints are missing rather than explicit.	2 / 3
Progressive Disclosure	Sections are well-organized and references are one-level-deep and clearly signaled (links to `./LICENSE`, `template.json`, `assets/deck-stage.js`), but those referenced bundle files are not present in the skill bundle, so the navigation cannot actually be completed.	2 / 3
	Total	9 / 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, specific domain and audience but reads as a product description rather than a capability statement: it lacks concrete actions, an explicit "Use when…" trigger, and broad natural keyword coverage. It is distinguishable but carries overlap risk with sibling deck templates.

Suggestions

Lead with concrete action verbs the skill performs (e.g., "Builds a self-contained HTML curatorial deck… clones the template, swaps in real content, and preserves the design system").

Add an explicit trigger clause: "Use when the user wants an art-biennale or museum-programme deck, curatorial pitch, or design-conference brochure."

Include broader natural trigger terms (e.g., "html slides", "exhibition deck", "curatorial pitch") to improve keyword coverage and reduce overlap with sibling templates.

Dimension	Reasoning	Score
Specificity	The description names a concrete domain and artifact ("a curatorial deck for a contemporary art biennale — the thesis, the rooms, the works, and the visitor journey") but uses no concrete action verbs describing what the skill does, so it stops at naming the domain rather than listing specific actions.	2 / 3
Completeness	It answers "what" (a curatorial deck for an art biennale) but provides no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	It includes relevant domain keywords ("contemporary art biennale", "curatorial deck", "museum board, curators") a user might say, but offers only narrow coverage with no common variations or broader natural terms.	2 / 3
Distinctiveness Conflict Risk	The art-biennale/museum niche is fairly specific, but as one template in a family of HTML deck skills ("html-ppt-zhangzara-biennale-yellow") it could still overlap with sibling deck-template skills.	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-biennale-yellow/SKILL.md
Commit: f2760fd

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