CtrlK
BlogDocsLog inGet started
Tessl Logo

html-ppt-zhangzara-scatterbrain

A design-school graduation project: a civic wayfinding system for a transit hub — the brief, the process, and the outcome. Built as a decision-grade coursework defense deck for crit panel, faculty.

56

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./design-templates/html-ppt-zhangzara-scatterbrain/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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 and highly actionable with a clean, sequenced workflow and a concrete output contract. Its main weaknesses are the absence of validation checkpoints in the workflow and references to bundle files that do not actually ship with the skill.

Suggestions

Add a lightweight validation/verification checkpoint to the workflow, e.g. 'Open `example.html` in a browser to confirm rendering before delivering' or a final critic pass step.

Ship the referenced files (`example.html`, `template.json`, `LICENSE`, and `assets/deck-stage.js`) or remove the references so navigation is not broken.

DimensionReasoningScore

Conciseness

The body is lean and well-organized ('At a glance' bullets, tight 'Best for'/'Avoid for', numbered workflow) with no padding or explanations of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Steps are concrete and executable: 'Clone `example.html` into the user's workspace', 'duplicate an existing slide of the most appropriate layout', 'drop slides from the bottom. Update page-number labels', plus a copy-paste `<artifact>` output contract.

3 / 3

Workflow Clarity

The six workflow steps are clearly sequenced, but there are no validation checkpoints or feedback loops, which matches the 'steps listed but checkpoints missing' anchor rather than the top level.

2 / 3

Progressive Disclosure

Sections are well-organized and references are clearly signaled at one level, but the body points to `./LICENSE`, `template.json`, `example.html`, and `assets/deck-stage.js`, none of which are present in the bundle, so navigation is partly broken.

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 vivid, well-scoped subject and deliverable, but reads more as a topic statement than an action/trigger description. It lacks an explicit 'Use when' clause and concrete action verbs, which keeps it at the mid-level across dimensions.

Suggestions

Lead with concrete verbs the skill performs, e.g. 'Generates a self-contained HTML graduation-defense deck... clone, populate, and present.'

Add an explicit 'Use when' clause naming natural triggers like 'graduation design project', 'capstone defense', 'portfolio review', or 'coursework presentation'.

Include common user-facing variations ('capstone defense', 'senior project', 'portfolio deck') to improve trigger-term coverage and distinctiveness from sibling deck skills.

DimensionReasoningScore

Specificity

Quotes like 'a civic wayfinding system for a transit hub' and 'decision-grade coursework defense deck' name a concrete domain and deliverable, but the skill's concrete actions (generate slides, assemble an HTML deck) are only implied, not enumerated.

2 / 3

Completeness

It clearly answers 'what' (a defense deck about a wayfinding project) but has no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

'graduation project', 'coursework defense deck', 'crit panel, faculty' are relevant natural terms for the niche, but common variations a user might actually say (e.g. 'capstone defense', 'portfolio', 'design presentation') are missing.

2 / 3

Distinctiveness Conflict Risk

The subject is a specific design-school niche, but as one of several HTML deck template skills it could still overlap with sibling presentation skills, so it is only somewhat distinctive.

2 / 3

Total

8

/

12

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.