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.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/_official/examples/html-ppt-obsidian-claude-gradient/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured entry-point card: a clear six-step authoring workflow with copy-paste-ready paths and a valuable, concrete treatment of the shared-asset relocation pitfall. Its main weaknesses are mild redundancy in the asset-rewrite recipes and the absence of any validation step to confirm the relocated assets actually load.

DimensionReasoningScore

Conciseness

The body is directive throughout with no explanations of concepts Claude already knows, but step 3 restates the four asset file paths and their rewritten targets twice, and filler like "Default tokens look fine" could be trimmed — anchor 4 rather than 5.

4 / 5

Actionability

Guidance is concrete and executable — exact template paths, the four asset files to copy, the exact `../../../assets/...` → `assets/...` rewrites, the theme mechanism, and the notes markup. Minor gap: no code block showing the final rewritten `<link>`/`<script>` tags, and core authoring rules are deferred to the master skill.

4 / 5

Workflow Clarity

Six numbered steps in a clear, correct sequence with no destructive or batch operations (so no cap applies), but there is no explicit validation checkpoint after the fragile asset-rewrite step — e.g., verifying the copied deck's navigation actually works — leaving it at anchor 4.

4 / 5

Progressive Disclosure

The card is a model entry point: a concise overview with well-signaled, one-level-deep references (the master SKILL.md, the full-decks catalog, the template folder, themes/*.css) and detail appropriately delegated to those targets; no bundle files exist that should have been referenced instead.

5 / 5

Total

17

/

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 is specific about the deck's subject matter and audience, but reads as a content summary rather than a capability statement: it never states what the skill does and provides no "use when" trigger guidance. Trigger keywords cover the niche but miss common presentation synonyms like "slides" or "presentation".

Suggestions

Rewrite the description to lead with a third-person action verb, e.g., "Creates an enterprise AI-adoption brief as a decision-grade HTML slide deck covering local-first agents, risk controls, ROI, and the rollout plan for leadership, IT, and security audiences."

Add an explicit trigger clause such as "Use when the user asks for an AI adoption brief, AI literacy deck, or executive rollout presentation for enterprise AI initiatives."

Include natural synonym keywords users would actually say — "slides", "presentation", "executive briefing" — to broaden trigger coverage without adding vagueness.

DimensionReasoningScore

Specificity

The description concretely names the subject matter ("local-first agents at work, the risk controls, the ROI, and the rollout plan") and the deliverable ("decision-grade AI literacy deck"), but contains no action verb stating what the skill does — the capability is only implied by "Built as a... deck".

3 / 5

Completeness

The "what" is clear (a decision-grade AI literacy deck on enterprise AI adoption for leadership, IT, security), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "AI-adoption brief", "AI literacy deck", "rollout", and "ROI" match the niche, but common natural variations users would say — "slides", "presentation", "PowerPoint", or file extensions — are missing.

3 / 5

Distinctiveness Conflict Risk

The subject is pinned to one specific brief (OpenDesign's enterprise AI adoption) with named audiences, giving a clear niche with only minor overlap risk against sibling deck or ai-literacy template cards — not fully minimal, so not a 5.

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

plugins/_official/examples/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.