CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

70

Quality

86%

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

86%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 clean, well-structured instruction skill: lean body, clear workflow with a validation checkpoint, and properly signaled references to real bundle files. Actionability and workflow steps could be sharpened with a small code/contract example for the artifact.

Suggestions

Include a minimal concrete code/contract snippet for the emitted artifact (e.g. a one-line HTML skeleton) to push actionability from instructional to fully executable.

Tighten abstract workflow steps (e.g. 'Keep interactions and motion quality') into specific, verifiable acceptance criteria so success is unambiguous.

DimensionReasoningScore

Conciseness

A lean ~47-line body that assumes Claude's competence: resource map, workflow, and output contract with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Gives concrete, executable guidance (start from assets/template.html, preserve keyboard 1/2/3 and R, emit a literal artifact block) but provides no runnable code snippets, leaving minor gaps.

4 / 5

Workflow Clarity

A clear 7-step sequence with an explicit validation checkpoint (step 7: 'Validate against references/checklist.md before emitting artifact'); a few steps remain somewhat abstract rather than fully prescriptive.

4 / 5

Progressive Disclosure

A clear overview with a resource map and well-signaled, one-level-deep references to real files (assets/template.html, references/checklist.md); content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

87%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 well-crafted, third-person description that clearly states both the capability and its trigger conditions with concrete visual and structural detail. Strong on completeness and distinctiveness; trigger-term and specificity coverage are good but could add a couple more natural phrasings.

Suggestions

Add a few more everyday user phrasings (e.g. 'quarterly business review', 'Q1/Q2/Q3/Q4 deck') to broaden trigger-term coverage.

Consider naming an output-format cue (e.g. 'self-contained HTML deck') to sharpen the what-is-emitted aspect of specificity.

DimensionReasoningScore

Specificity

Names the domain plus several concrete visual/structural actions ('heavyweight slab headlines', 'clean cream paper sections', 'structured grids', 'fast premium motion pacing'), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what (a high-impact quarterly review/roadmap deck in a defined visual language) and when (explicit 'Use when users ask for...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Good natural-term coverage with synonyms and bilingual variants ('quarterly review template', 'roadmap slide style', 'vintage business deck'), though a few common phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

A narrowly scoped visual presentation style with distinctive triggers ('blue orange presentation', 'retro quarterly review') yielding minimal overlap with other skills.

5 / 5

Total

18

/

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.

Validation15 / 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
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.