CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-obsidian-claude-gradient

OpenDesign's enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan. Built as a decision-grade AI literacy deck for leadership, IT, security.

55

Quality

69%

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-obsidian-claude-gradient/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is a focused, competent entry-point card: it states when to pick the template, hands off authoring rules to the master skill, and documents a genuinely non-obvious runtime pitfall with two concrete remediation recipes. Main gaps are the missing explicit validation step after the asset-URL rewrite and references that point outside the skill's own bundle.

Suggestions

Add a validation checkpoint after Recipe A/B — e.g., 'After rewriting/including the four files, open index.html and confirm arrow-key navigation and the theme toggle (T) work before shipping' — turning the failure-mode warning into a feedback loop.

Include a short literal before/after example of one rewritten tag (e.g., `<link rel="stylesheet" href="../../../assets/base.css">` → `<link rel="stylesheet" href="assets/base.css">`) so the rewrite is copy-paste unambiguous.

Trim the explanatory clause about navigation being dead ('…meaning the deck never activates and slide navigation is dead') since the 404 consequence is already clear.

DimensionReasoningScore

Conciseness

The body is a lean pointer-card that adds only non-obvious knowledge (template location, the parent-relative URL 404 trap, speaker-note placement); the explanation of why navigation would be dead is slightly over-explained and could be trimmed one clause.

4 / 5

Actionability

Highly concrete guidance — exact source folders and files to copy, the four exact `<link>`/`<script>` tags to rewrite, exact project-local destination paths, and the theme-swapping mechanism — though a literal before/after HTML snippet of the rewritten tags would make it copy-paste ready.

4 / 5

Workflow Clarity

A clearly sequenced 1–6 workflow with an explicit failure-mode warning and a closing guardrail ('do not ship the upstream ../../../assets/... URLs verbatim'), but it lacks an explicit post-copy validation step (e.g., open the deck and confirm navigation/toggle works) that would catch a botched URL rewrite.

4 / 5

Progressive Disclosure

The skill is a thin, well-signaled entry card pointing one level deep to the master skill and the full-decks catalog, which is exactly the right shape; however, all referenced paths (../html-ppt/…, design-templates/html-ppt/…) live outside the skill's own directory and no bundle files ship with this card, a minor organization gap against the 'clear overview with one-level-deep references' anchor.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 communicates a clear, niche deliverable with concrete content topics, but reads more like a deck synopsis than a capability statement: it names no distinct skill actions and gives no 'Use when…' trigger guidance, so a user searching for slide/presentation help may not find it. Trigger coverage omits common synonyms like slides, presentation, or PowerPoint.

Suggestions

Add an explicit 'Use when…' clause (e.g., 'Use when the user asks for an enterprise AI-adoption brief, decision deck, or AI literacy presentation for leadership/IT/security').

State the skill's concrete actions — e.g., 'Writes and produces a decision-grade AI literacy deck from the obsidian-claude-gradient HTML slide template: slide plan, slides, speaker notes, and critic pass' — instead of describing the example deck's subject matter.

Add natural synonyms users would say ('slides', 'presentation', 'deck', 'brief') to the trigger keywords so the description surfaces for those phrasings.

DimensionReasoningScore

Specificity

Names the domain and one concrete deliverable action ("Built as a decision-grade AI literacy deck") plus concrete content areas ("risk controls, the ROI, and the rollout plan"), but does not list multiple distinct capability actions, so it sits at the 'domain + 1-2 actions' anchor rather than the comprehensive one above.

3 / 5

Completeness

The 'what' is clear (a decision-grade AI literacy deck covering local-first agents, risk controls, ROI, and rollout plan), but there is no 'Use when…' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Relevant keywords are present ("AI literacy deck", "ROI", "rollout plan", "risk controls", "leadership, IT, security"), but common variations and synonyms a user would naturally say — "slides", "presentation", "PowerPoint", "deck" variants — are missing, matching the 'missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

It carves out a fairly distinct niche (an enterprise AI-adoption decision brief aimed at leadership/IT/security), but broadly applicable terms like "AI literacy deck" and "AI" leave minor overlap risk with sibling deck-authoring skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

13

/

20

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.

Validation — 13 / 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: 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-obsidian-claude-gradient/SKILL.md

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.