frame-data-chart-nyt

NYT-newsroom typography, staggered reveal animation, and editorial-grade charts (line, bar, or range band).

Quality

61%

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 ./skills/frame-data-chart-nyt/SKILL.md

Quality

Content

72%

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

The body is an efficient, well-structured design spec that assumes competence and avoids concept padding. Its main weakness is the absence of a complete, executable HTML/SVG code template to anchor the otherwise precise specifications.

Suggestions

Include one short, complete inline SVG/HTML code skeleton (within the stated ~80-line budget) so the specs are immediately actionable rather than descriptive.

Frame the build as an explicit ordered workflow (e.g. 1. parse data → 2. pick chart type → 3. build SVG → 4. add staggered animation → 5. verify prefers-reduced-motion) with a quick self-check step.

Add a one-line verification cue for the data-handling branch (CSV/JSON direct draw vs. 'schematic' estimation) so the user can confirm the right path was taken.

Dimension	Reasoning	Score
Conciseness	The body is a dense, lean specification (colors, sizes, font choices, animation timings) with no padding or explanation of concepts Claude already knows; every line earns its place.	3 / 3
Actionability	It gives precise concrete specs (e.g. accent red #a91d1d, 5.6vw title, '<text class="annot">2024 · 412M</text>') but provides no complete, executable SVG/HTML code block — only the recommendation to hand-write under 80 lines — so guidance is concrete but not copy-paste ready.	2 / 3
Workflow Clarity	The layout is sectioned and the visual/animation ordering is implicit, but it is presented as a reference spec rather than a sequenced build workflow with validation checkpoints, leaving the sequence present but checkpoints implicit.	2 / 3
Progressive Disclosure	At ~23 lines with clear section headers (画布/布局/设计细节) and no need for external references (no references/scripts/assets bundle exists), the single self-contained file is well-organized, satisfying the simple-skill allowance for a top score.	3 / 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 is specific about the visual signature it produces but reads as a feature list rather than action-oriented guidance, and it omits any explicit "Use when..." trigger clause. This leaves all dimensions at the mid level.

Suggestions

Add a 'Use when...' clause with natural triggers, e.g. 'Use when the user wants an NYT-style editorial data chart or video frame from CSV/JSON data or a one-line conclusion.'

Reframe feature nouns as concrete actions, e.g. 'Turn data (CSV/JSON or a conclusion) into a single NYT-newsroom data chart frame with line, bar, or range-band visuals and a staggered reveal animation.'

Include a few common natural phrasings users would actually say (e.g. 'NYT-style chart', 'editorial data viz', 'data chart video frame') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names concrete features like "editorial-grade charts (line, bar, or range band)" and "staggered reveal animation", but the description lists noun-like components rather than multiple concrete actions/verbs, so it names domain and features but is not comprehensive on actions.	2 / 3
Completeness	It clearly answers what the skill produces, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Relevant terms users might say are present ("NYT", "charts", "line, bar, or range band"), but phrases like "NYT-newsroom typography" and "staggered reveal animation" lean jargon-heavy and common variations (e.g. "data viz", "NYT-style chart") are missing.	2 / 3
Distinctiveness Conflict Risk	The NYT editorial-chart niche is fairly specific, but without explicit trigger language and given the apparent catalog of sibling frame skills, it could still overlap with similar chart/frame skills.	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: skills/frame-data-chart-nyt/SKILL.md
Commit: f2760fd

Reviewed: about 14 hours 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.