CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

html-ppt-retro-quarterly-review

Retro Quarterly Review presentation template in a bold blue + orange editorial language. Use when users ask for a high-impact quarterly review / roadmap deck with heavyweight slab headlines, clean cream paper sections, structured grids, and fast premium motion pacing (3 slides, each hold under 3s in video mode).

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

A well-organized, token-efficient template skill body with a concrete workflow and a real validation checklist. The consistent 4s trace to three fixable gaps: a missing example.html, no error-recovery loop after validation, and no surfaced CSS variable names for token mapping.

Suggestions

Create the referenced `example.html` or remove it from the resource map and the frontmatter `outputs.secondary` list so all listed files exist.

Add an explicit feedback loop after step 7 (e.g., "If any P0 item fails, fix the template and re-run the checklist before emitting the artifact").

List the key CSS variable names from template.html (colors, fonts) next to step 1 so token-change requests can be mapped without opening the file first.

DimensionReasoningScore

Conciseness

Lean and efficient: a 7-step workflow, a resource map, and an output contract with zero padding and no explanation of concepts Claude already knows. Every section earns its tokens.

5 / 5

Actionability

Mostly executable: "Start from `assets/template.html`; do not rebuild from scratch", concrete interaction specs ("keyboard `1/2/3` quick jump", "`R` restart"), and an exact artifact wrapper. Falls short of anchor 5 because the artifact block is a `<html>...</html>` skeleton and the token-mapping step ("map any requested token changes into CSS variables") surfaces no variable names, forcing a detour into the template to act.

4 / 5

Workflow Clarity

A clear 7-step sequence ending in an explicit validation checkpoint ("Validate against `references/checklist.md`", a real P0/P1/P2 checklist). Not anchor 5 because there is no feedback loop — no instruction to fix and re-validate when a checklist item fails.

4 / 5

Progressive Disclosure

Good structure: a resource map plus one-level-deep references (assets/template.html and references/checklist.md, both present on disk). Not anchor 5 because the resource map and frontmatter secondary outputs list a root-level `example.html` that does not exist in the bundle, a dead navigation entry.

4 / 5

Total

17

/

20

Passed

Description

95%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.

A strong description: explicit what-and-when structure, rich natural trigger synonyms including a second language, and a well-differentiated niche. The only gap is that capabilities are expressed as visual attributes rather than concrete actions.

Suggestions

Lead with an explicit action verb (e.g., "Generates a three-slide retro quarterly review deck…") so the capability reads as an action, not just a feature list.

Mention adaptation of user copy/data into the template, since the body supports it but the description only covers generation.

DimensionReasoningScore

Specificity

The description names the domain and lists several concrete, verifiable attributes ("heavyweight slab headlines", "clean cream paper sections", "structured grids", "3 slides, each hold under 3s in video mode"). It stops short of anchor 5 because it frames features rather than explicit actions (no create/adapt/edit verbs), and exceeds anchor 3's '1-2 concrete actions' bar.

4 / 5

Completeness

It explicitly answers both: what ("Retro Quarterly Review presentation template in a bold blue + orange editorial language") and when ("Use when users ask for a high-impact quarterly review / roadmap deck"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms — "retro quarterly review", "quarterly review template", "roadmap slide style", "blue orange presentation", "vintage business deck" — plus Chinese-language variants ("季度复盘复古风", "蓝橙复古汇报模板"), matching a user's natural phrasing for this skill.

5 / 5

Distinctiveness Conflict Risk

A clearly pinned niche — retro-styled blue/orange quarterly-review video deck — with distinct trigger vocabulary, so overlap risk with generic presentation skills is minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

nexu-io/open-design

Path

skills/html-ppt-retro-quarterly-review/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.