CtrlK
BlogDocsLog inGet started
Tessl Logo

html-ppt-obsidian-claude-gradient

Open Design'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.

53

Quality

61%

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

72%

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

The content is a well-structured, actionable entry point with concrete file paths and a clear authoring sequence, and it practices good progressive disclosure by deferring detail to the master skill. Its main gaps are minor verbosity in the asset-path rationale and the absence of an explicit 'verify the deck runs' validation step.

Suggestions

Add a final validation step (e.g., open index.html and confirm slide navigation/keyboard runtime works) after the asset-path rewrite, turning the workflow into a validate-then-proceed loop.

Trim the explanatory rationale in step 3 to the essential gotcha and the two recipes; drop phrases like 'meaning the deck never activates and slide navigation is dead'.

Consider a short copy-paste snippet showing the rewritten <link>/<script> tags so the asset fix is unambiguous on first read.

DimensionReasoningScore

Conciseness

The body is mostly efficient with specific paths and steps, but the Recipe A/B explanation of the parent-relative URL problem ('sits three folders deep', 'the deck never activates and slide navigation is dead') pads the rationale beyond what Claude needs.

2 / 3

Actionability

Guidance is concrete and executable: exact paths to copy, the body class to keep, which link/script tags to rewrite, theme swapping via '<link id="theme-link">', and where speaker notes belong.

3 / 3

Workflow Clarity

A clear numbered sequence (read master skill, copy template, bring runtime, pick theme, replace content, add notes) is present, but there is no explicit validation checkpoint to confirm the deck actually activates and navigates after the asset-path rewrite.

2 / 3

Progressive Disclosure

The body is a focused entry-point overview that cleanly points one level deep to the master skill, the full-decks catalog, and the template folder, with well-organized sections and no nested-reference walls.

3 / 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 clear, domain-specific subject and audience but reads as a content summary rather than a capability statement, and it omits any explicit 'Use when...' trigger guidance. Scores are uniformly mid-range because it answers 'what' while leaving 'when' only implied.

Suggestions

Add an explicit 'Use when...' trigger clause naming the natural situations a user would describe (e.g., 'Use when leadership asks for an enterprise AI adoption or rollout brief, or when you need a decision-grade AI literacy deck').

Reframe around concrete actions Claude performs ('Builds', 'Drafts', 'Structures ... into slides') rather than describing the deck's subject matter.

Tighten trigger coverage with common user phrasings like 'AI rollout plan', 'AI ROI brief', or 'AI adoption proposal for executives'.

DimensionReasoningScore

Specificity

The description names a clear domain ('enterprise AI-adoption brief: local-first agents at work, the risk controls, the ROI, and the rollout plan') but describes the deck's subject matter rather than listing concrete actions Claude performs, so it is not fully comprehensive.

2 / 3

Completeness

It answers 'what' (a decision-grade AI literacy deck for leadership, IT, security) but has no explicit 'Use when...' trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Relevant terms like 'enterprise AI-adoption brief', 'AI literacy deck', and 'leadership, IT, security' are present, but coverage of natural phrasings a user would say is partial and lacks common variations.

2 / 3

Distinctiveness Conflict Risk

The niche (enterprise AI-adoption brief for leadership/IT/security) is fairly specific, but broad tokens like 'AI', 'copilot', and 'deck' could still overlap with similar AI or presentation 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: 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
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.