editorial-tech

Blend editorial magazine composition with precision product-tech detailing using asymmetrical grids, cinematic media bands, mono utility labels, and restrained accent color.

Quality

65%

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 ./agent-skills/web-design/editorial-tech/SKILL.md

Quality

Content

72%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 content is a well-structured, concise, and actionable style-direction reference that needs no external bundle files. Its main weakness is the empty '## Workflow' heading, which promises a process that is not delivered and leaves workflow clarity implicit.

Suggestions

Remove the empty '## Workflow' heading or replace it with a short explicit sequence (e.g. 1. Define grid/columns 2. Set type hierarchy 3. Place cinematic media bands 4. Add technical markers 5. Apply restrained accent).

Tighten the overlap between 'Visual target' and 'Implementation guidance' so each bullet earns its place without restating the other.

Optionally specify a couple of concrete defaults (e.g. an accent derivation rule or a mono-label format) to push actionability from concrete directives to copy-paste-ready spec.

Dimension	Reasoning	Score
Conciseness	The body is lean, directive, and free of padding or basic-concept explanations, with only minor redundancy across 'Visual target', 'Implementation guidance', and 'Recommended patterns' and an empty '## Workflow' heading that could be trimmed.	4 / 5
Actionability	Concrete, specific guidance is given throughout ('Favor multi-column layouts, offset alignment, and editorial cropping', 'Use one display-oriented type treatment... then support it with clean sans-serif or mono utility text'), with specific recommended patterns covering nav, hero, modules, containers, and CTAs.	4 / 5
Workflow Clarity	The '## Workflow' section is empty and no explicit step sequence or validation checkpoints are provided; the section order (Scope -> Visual target -> Implementation -> Patterns -> Tuning -> Avoid) gives only an implicit flow.	3 / 5
Progressive Disclosure	The skill is a self-contained style direction under ~50 lines with no need for external references, and it is well-organized into clearly labeled sections, satisfying the simple-skill exception.	5 / 5
	Total	16 / 20 Passed

Description

58%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 specific and visually concrete about the editorial-tech aesthetic, but it omits any explicit 'when to use it' trigger guidance and relies on designer jargon over natural user keywords. Adding a 'Use when...' clause with common phrasings would materially raise completeness and trigger quality.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when designing premium editorial-style layouts, magazine-tech interfaces, or asymmetrical product marketing pages.'

Add user-friendly synonyms (e.g. 'magazine layout', 'editorial design', 'tech product UI') alongside the current designer terminology.

Restate capability in third-person voice (e.g. 'Blends editorial magazine composition...') to match the rubric's voice expectation.

Dimension	Reasoning	Score
Specificity	Lists several concrete ingredients ('asymmetrical grids, cinematic media bands, mono utility labels, and restrained accent color') rather than vague abstractions, though these are stylistic descriptors rather than enumerated actions, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (an editorial-tech style direction), but there is no 'Use when...' clause or equivalent trigger guidance in the description itself, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Relevant design keywords are present ('editorial magazine composition', 'product-tech detailing') but they lean toward designer jargon and miss natural user phrases and synonyms a non-specialist would actually say.	3 / 5
Distinctiveness Conflict Risk	It carves a fairly distinct niche (editorial magazine merged with high-end tech UI) with only minor overlap risk against other generic design/style skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: MengTo/Skills
Path: agent-skills/web-design/editorial-tech/SKILL.md
Commit: 4c716b5

Reviewed: 1 day 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.