weekly-update

Open Design's weekly metrics standup: this week's numbers, the one anomaly, and the single decision it forces. Built as a decision-grade data & finance deck for ops & growth team.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-templates/weekly-update/SKILL.md

Quality

Content

77%

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

The body is concise and well-sequenced, giving a clear slide-by-slide plan and an output contract. Its main weaknesses are the lack of an executable HTML example and a dangling DESIGN.md reference that no bundle file backs up.

Suggestions

Include a minimal executable HTML skeleton demonstrating the 100vw-per-slide horizontal-swipe structure and arrow-key navigation, so the deck is copy-paste ready rather than described.

Resolve the DESIGN.md reference: either bundle it under references/ and link it ([DESIGN.md](references/DESIGN.md)), or inline the essential design-system guidance (colors, typography, layout) directly in the body.

Specify how the '1–2 inline charts' should be rendered (e.g. inline SVG or a named charting snippet) so that step is actionable rather than left open.

Dimension	Reasoning	Score
Conciseness	The ~25-line body is lean and assumes Claude's competence — 'Produce a single-file horizontal-swipe HTML deck for a weekly team update' then straight into the slide structure — with no padding or re-explanation of concepts Claude already knows, matching the score-3 'lean and efficient' anchor.	3 / 3
Actionability	The slide list gives concrete constraints (3–5 items, owner avatars, 1–2 inline charts) and an output-contract artifact wrapper, but there is no executable HTML template or example showing how to actually build the horizontal-swipe deck, leaving it at 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	The workflow is a clearly numbered sequence (read design system → identify context → build slides → navigation) with an unambiguous single deliverable; no validation checkpoint is required because deck creation is non-destructive, so it satisfies the clear-sequence anchor.	3 / 3
Progressive Disclosure	Sections are short and well-organized, but step 1 references a DESIGN.md that is not present in the skill's bundle (references/, scripts/, assets/ are all absent) and is not linked, so a referenced path is broken and navigation is incomplete.	2 / 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, specific niche (a weekly metrics standup deck) in third person, but it lacks an explicit 'Use when…' trigger clause and only partially covers natural keyword variations. It is competent but not exemplary, scoring at the midpoint across all dimensions.

Suggestions

Add an explicit 'Use when…' clause naming the situations that should trigger this skill (e.g. 'Use when the user asks for a weekly metrics standup, KPI review, or team update deck').

Expand trigger coverage with common user terms — KPI, dashboard, metrics review, weekly report — so the description matches how users actually phrase the request.

Lead with the concrete actions the skill performs (e.g. 'Produces a single-file HTML deck with cover, headline, shipping/in-flight/blocked slides, and inline metric charts') before describing the deck's purpose.

Dimension	Reasoning	Score
Specificity	Names the domain ('data & finance deck') and deck contents ('this week's numbers, the one anomaly, and the single decision it forces'), but describes a single deliverable rather than listing multiple concrete actions the skill performs, so it falls short of the score-3 anchor.	2 / 3
Completeness	It states what the deck is ('Built as a decision-grade data & finance deck for ops & growth team') but provides no 'Use when…' clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('weekly metrics standup', 'data & finance deck', 'ops & growth team') but misses common variations a user might actually say (KPI, dashboard, report), matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The 'weekly metrics standup' framing is a reasonably clear niche, but it could still overlap with generic deck/slide-creation skills and the 'Open Design' org-specific phrasing blurs the trigger, landing at 'somewhat specific but could overlap'.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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: design-templates/weekly-update/SKILL.md
Commit: f2760fd

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.