CtrlK
BlogDocsLog inGet started
Tessl Logo

html-ppt-zhangzara-vellum

A humanities lecture: how Renaissance linear perspective reshaped early cartography — sources, argument, and evidence. Built as a decision-grade academic research deck for faculty, graduate seminar.

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-vellum/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, well-structured, and highly actionable for a template/slide skill, with a tight workflow and exact output contract. The two gaps are the absence of an explicit verification checkpoint in the workflow and references to bundle files that are not actually shipped.

Suggestions

Add an explicit validation checkpoint to the workflow, e.g. 'Verify every placeholder is replaced and the deck renders in a browser before emitting the <artifact>', with a fix-and-retry loop.

Ship the referenced bundle files (example.html, LICENSE, template.json, and assets/) alongside SKILL.md so the signaled one-level-deep references actually resolve.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows; every section ('At a glance', 'Best for', 'Avoid for', the 6-step workflow, output contract) earns its place.

3 / 3

Actionability

Concrete, executable guidance throughout — clone example.html, replace placeholders, preserve the design system, duplicate layouts for length, and an exact <artifact> output-contract format — copy-ready for a template skill.

3 / 3

Workflow Clarity

The 6-step workflow is clearly sequenced, but there is no explicit validation/verification checkpoint, which the score-3 anchor requires even for non-destructive generation tasks.

2 / 3

Progressive Disclosure

References are well-signaled and one level deep (./LICENSE, template.json, example.html), but none of those bundle files exist in the skill, so the signaled navigation is effectively 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 clearly identifies a niche (academic/humanities research deck) but reads as a topic statement rather than a capability+trigger statement, with no explicit 'Use when' guidance. It is middling across all dimensions and would benefit from leading with concrete actions and an explicit trigger clause.

Suggestions

Add an explicit 'Use when…' trigger clause, e.g. 'Use when creating an academic research deck, humanities lecture slides, or a scholarly review deck for faculty or graduate-seminar audiences', to raise completeness and trigger-term quality.

Lead with concrete capability actions (e.g. 'Builds decision-grade academic research slide decks: structures sources, argument, and evidence into a navigable HTML lecture') instead of opening with a single example topic.

Generalize the example-specific framing ('Renaissance linear perspective reshaped early cartography') into the skill's general purpose to improve distinctiveness from sibling template skills.

DimensionReasoningScore

Specificity

Names the domain ('academic research deck', 'humanities lecture') but states no concrete capability verbs — actions are only implied via 'deck', so it lands at 'names domain and some actions' rather than listing multiple concrete actions.

2 / 3

Completeness

It conveys a 'what' (a decision-grade academic research deck) but provides no explicit 'when should Claude use it' trigger clause, which the guidelines cap at 2.

2 / 3

Trigger Term Quality

Contains niche terms like 'humanities lecture' and 'academic research deck' but offers no 'Use when…' phrasing and narrow coverage, missing common variations users would actually say.

2 / 3

Distinctiveness Conflict Risk

The niche framing is somewhat distinctive, but it is heavily tied to a single example topic and the broad term 'research' could overlap with sibling deck-template skills.

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.