CtrlK
BlogDocsLog inGet started
Tessl Logo

field-notes-editorial-template

Editorial "Field Notes" report template with soft paper background, serif hero typography, rounded pastel insight cards, and a retention chart panel. Use when users ask for a premium magazine-style business report, board memo one-pager, or elegant data storytelling layout.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a well-organized, concise overview with a clear validated workflow and properly split references. Its main weakness is actionability: concrete execution details for the custom CSS variables, count-up animation, and chart reveal are described in prose but not provided as copy-paste-ready code.

Suggestions

Add a short CSS-variable snippet (e.g. the root :root { --paper: ...; --ink: ...; } block) so the 'map palette/typography to root CSS variables' step is copy-paste executable rather than implied.

Include a minimal executable example of the count-up and chart line-reveal animations (or a pointer to where in assets/template.html they live) so the interaction steps are concrete.

Create the missing example.html referenced in the resource map and checklist, or remove the reference, so every signaled bundle path resolves.

DimensionReasoningScore

Conciseness

The body is lean (~40 lines) and directive, with no exposition of concepts Claude already knows and every line carrying actionable intent.

3 / 3

Actionability

Steps name concrete artifacts ('Copy assets/template.html to index.html', 'map palette/typography to root CSS variables') but provide no complete executable code — the output contract only shows an '<html>...</html>' placeholder, leaving the CSS-variable mapping, count-up, and chart-reveal mechanics undescribed as code.

2 / 3

Workflow Clarity

A clear six-step sequence culminates in an explicit validation gate ('Validate against references/checklist.md before emitting'), with the checklist acting as the error-catching checkpoint for the generation process.

3 / 3

Progressive Disclosure

A resource map signals one-level-deep references (assets/template.html, references/checklist.md, example.html) and the body content is appropriately split between an overview and a detailed checklist, matching the clear-overview anchor.

3 / 3

Total

11

/

12

Passed

Description

100%

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, trigger-rich, and complete, clearly communicating both what the template produces and when to invoke it. It is concise yet covers concrete visual components and natural-language triggers including non-English variants.

DimensionReasoningScore

Specificity

Enumerates multiple concrete design elements — 'soft paper background, serif hero typography, rounded pastel insight cards, and a retention chart panel' — going beyond a single named domain to several specific components.

3 / 3

Completeness

Explicitly answers both 'what' (an editorial Field Notes report template with named visual features) and 'when' via an explicit 'Use when users ask for...' clause, matching the top anchor.

3 / 3

Trigger Term Quality

The 'Use when...' clause names natural phrases users would say ('premium magazine-style business report', 'board memo one-pager', 'elegant data storytelling layout'), supplemented by a dedicated triggers list with varied phrasings.

3 / 3

Distinctiveness Conflict Risk

A highly specific visual identity (paper background, serif hero, pastel cards, retention chart) with niche editorial triggers makes it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.