CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-knowledge-arch-blueprint

OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.

56

Quality

70%

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-knowledge-arch-blueprint/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable entry-point card: exact paths, two explicit asset-migration recipes, and clear sequencing. Its weaknesses are minor — a missing validation step after the URL rewrite, slight over-explanation of the 404 gotcha, and references that resolve to sibling-tree paths outside this bundle.

DimensionReasoningScore

Conciseness

The card is lean and every step earns its place, but the asset-URL gotcha is slightly over-explained ('meaning the deck never activates and slide navigation is dead') — anchor 4 ('efficient; minor instances of over-explanation that could be trimmed') rather than 5.

4 / 5

Actionability

Guidance is fully concrete and copy-paste-ready for an instruction-only skill: exact source paths ('design-templates/html-ppt/assets/fonts.css'), exact rewrite targets ('../../../assets/...' to 'assets/fonts.css' etc.), the theme mechanism ('<link id="theme-link">'), and notes placement ('<aside class="notes">'). Not anchor 4 because there are no material gaps in the common-case workflow.

5 / 5

Workflow Clarity

Six well-sequenced numbered steps cover reading the master skill, copying the template, fixing assets, theming, content replacement, and speaker notes, but there is no explicit validation checkpoint (e.g., confirming runtime.js resolves after the URL rewrite) — anchor 4 ('clear sequence with most checkpoints present; minor validation gaps') rather than 5.

4 / 5

Progressive Disclosure

The card is a proper thin overview that defers detail one level deep to the master skill ('All authoring rules live in .../html-ppt/SKILL.md') and the full-decks catalog, but those references point outside this skill's directory and no bundle files ship here, so navigation cannot be fully resolved within the bundle — anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

48%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 distinctive and topically concrete but reads as a content synopsis of the deck rather than a capability statement for the skill. It lacks any 'Use when...' trigger clause and any explicit action verbs, which caps both completeness and specificity. Natural synonyms like 'postmortem' or 'slides' would improve trigger coverage.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user asks for an incident-retro/postmortem learning deck or a decision-grade product management presentation') to lift completeness past the cap of 3.

State the skill's actions in third person (e.g., 'Builds an HTML slide deck...') instead of only describing the deck's subject matter, to raise specificity.

Include natural trigger synonyms such as 'postmortem', 'incident review', 'slides', and 'presentation' alongside 'incident retro' and 'deck' for better keyword coverage.

DimensionReasoningScore

Specificity

The description gives concrete subject matter ("the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups") but states no skill actions — it describes the deck's content rather than what the skill does, matching anchor 2 ('names the domain but actions are minimal or generic') rather than anchor 3, which requires 1-2 concrete actions.

2 / 5

Completeness

The 'what' is clear ("Built as a decision-grade product management deck for engineering, SRE, leadership") but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "incident retro", "product management deck", and "SRE, leadership" are natural, but common user variations such as "postmortem", "incident review", "presentation", or "slides" are missing — anchor 3 ('some relevant keywords but missing common variations or synonyms').

3 / 5

Distinctiveness Conflict Risk

The hyper-specific subject ("OpenDesign's incident retro: the daemon-restart data bug") gives a clear niche with minimal conflict risk, though it overlaps slightly with sibling deck-template skills in the same product-management family — anchor 4 ('mostly distinct; minor overlap risk with closely related skills').

4 / 5

Total

12

/

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-knowledge-arch-blueprint/SKILL.md

Revision

78d5637

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill