CtrlK
BlogDocsLog inGet started
Tessl Logo

editorial-tech

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

52

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/editorial-tech/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

The body is well-structured and rich in design vocabulary with strong organization, but it repeats key motifs across sections, leaves the Workflow section empty, and offers no concrete implementation artifacts to lift it from descriptive to fully actionable.

Suggestions

Remove the empty "## Workflow" header or fill it with an explicit sequenced process (e.g., 1. establish grid, 2. place media bands, 3. layer mono labels, 4. apply restrained accent).

De-duplicate "asymmetrical grids," "cinematic media bands," and "accent restraint" so each motif is stated once in its most relevant section rather than restated across three sections.

Add concrete implementation reference points such as a sample font pairing, a spacing/border-radius scale, accent-color usage rules, or a minimal Tailwind/CSS snippet to make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean bullet-form guidance that avoids explaining concepts Claude already knows, but it repeats the same motifs (asymmetrical grids, cinematic media bands, accent restraint) across Visual target, Implementation guidance, and Recommended patterns, and leaves an empty "## Workflow" header that wastes tokens.

2 / 3

Actionability

It gives specific, recognizable design directives (thin strokes, gradient-border shells, mono labels, offset alignment) but stops at the vocabulary level with no concrete implementation artifacts such as font pairings, a spacing scale, accent-color rules, or a sample CSS/Tailwind snippet.

2 / 3

Workflow Clarity

The "## Workflow" section is empty, and although Scope/Visual target/Implementation guidance convey intent, there is no explicit sequenced process or checkpoints; for a style-direction skill this is acceptable but the blank workflow header signals an unfilled gap.

2 / 3

Progressive Disclosure

The ~50-line body is organized into clear, well-labeled sections (Use When, Scope, Visual target, Implementation guidance, Recommended patterns, Tuning knobs, Avoid) with no need for external references, matching the simple-skill allowance for a top score on organization alone.

3 / 3

Total

9

/

12

Passed

Description

57%

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 paints a vivid, distinctive design niche but stops short of being a complete trigger: it states what well yet omits any explicit when-to-use guidance and relies on a single verb rather than enumerated actions.

Suggestions

Append an explicit "Use when..." trigger clause, e.g. "Use when designing landing pages, marketing sites, or product interfaces that should feel like a premium editorial spread merged with a high-end tech product."

Lead with concrete action verbs (e.g., "Design and style layouts using...") so the description lists discrete capabilities, not just visual elements.

Add common user-facing trigger terms such as "landing page," "marketing site," "design system," or "brand style" for broader natural-keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("editorial magazine composition with precision product-tech detailing") and several concrete visual elements (asymmetrical grids, cinematic media bands, mono utility labels, restrained accent color), but uses a single verb ("Blend") rather than enumerating multiple discrete actions, so it falls short of the top anchor.

2 / 3

Completeness

It clearly states what the skill does but contains no "Use when..." clause or equivalent explicit trigger guidance; per the guidelines, a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some natural designer-facing terms ("editorial," "magazine," "product-tech," "grid," "accent color") but misses common variations a user might say such as "landing page," "marketing site," or "design system," so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The editorial-meets-product-tech niche with this specific visual vocabulary (cinematic media bands, mono utility labels, restrained accent) is a clear, recognizable design lane unlikely to trigger for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.