weekly-update

OpenDesign'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

56%

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

65%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 admirably lean and gives a clear slide skeleton, but it stops short of executable guidance — the output contract is a placeholder, chart construction is unspecified, and the sole external reference is a missing file. A validation/critic step would also strengthen the workflow.

Suggestions

Fix the DESIGN.md reference: either ship the design-system file in the bundle or inline the essential style tokens so step 1 is actionable.

Add a concrete HTML/CSS scaffold for the horizontal-swipe container and an inline chart approach (e.g. a specific library or SVG pattern) instead of the '<!doctype html>...' placeholder.

Append a validation step, such as a critic pass checking that every chart has a decision above it and that navigation works, before delivering the artifact.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence — 'Produce a single-file horizontal-swipe HTML deck for a weekly team update' followed by a terse slide list with no padding or explanations of known concepts.	5 / 5
Actionability	The slide-by-slide structure with item counts ('3–5 items', '1–3 items + clear ask', 'Each slide is 100vw wide') is concrete, but the output contract is a placeholder ('<!doctype html>...') and '1–2 inline charts' gives no executable technique, leaving key implementation details missing.	3 / 5
Workflow Clarity	The four-step sequence (read design system, identify squad/week/audience, build eight slides, define navigation) is clearly ordered, but there are no validation checkpoints or critic pass, and step 1 points to a DESIGN.md file that does not exist in the bundle.	3 / 5
Progressive Disclosure	Sections are short and well-organized, but the body's only external reference — 'Read DESIGN.md' — dangles: no references/, scripts/, or assets/ directories exist, so navigation to the referenced material is broken.	3 / 5
	Total	14 / 20 Passed

Description

47%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 distinct and reasonably natural-sounding but reads as a deck caption rather than a capability description: it never states what the skill actually does and provides no usage trigger guidance. Adding explicit actions and a 'Use when...' clause would substantially improve it.

Suggestions

State concrete actions up front, e.g. 'Produces a single-file HTML slide deck with headline metrics, inline charts, and a decision slide for a weekly team standup.'

Add an explicit trigger clause: 'Use when the user asks for a weekly update, metrics standup deck, KPI review, or team status slides.'

Include natural synonyms users would say (weekly update, KPI deck, status report, dashboard slides) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names a specific domain ('OpenDesign's weekly metrics standup', 'data & finance deck for ops & growth team') but contains no concrete capability actions — 'this week's numbers, the one anomaly, and the single decision it forces' describes the deck's subject matter, not what the skill does.	2 / 5
Completeness	The 'what' is vague ('Built as a decision-grade data & finance deck' describes the artifact's theme rather than the skill's function) and there is no 'when' / 'Use when...' clause at all, matching the anchor for a vague what with no when.	2 / 5
Trigger Term Quality	Natural phrases like 'weekly metrics standup', 'this week's numbers', 'anomaly', and 'data & finance deck' are present and would be said by users, but common synonyms such as 'weekly update', 'KPI', 'report', or 'dashboard' are missing.	4 / 5
Distinctiveness Conflict Risk	'OpenDesign's weekly metrics standup' establishes a clear niche with distinct framing, though generic metrics/finance vocabulary ('numbers', 'finance deck') creates minor overlap risk with other analytics or deck skills.	4 / 5
	Total	12 / 20 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: 1b47e60

Reviewed: 3 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.