CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

og-image-size

Use when auditing Open Graph tags or generating og:image assets. Applies to any page that may be shared on social networks or messaging platforms.

Quality

75%

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 ./skills/og-image-size/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A compact, well-sectioned audit rule with concrete numeric criteria, an explicit check/fix workflow, and exemplary progressive disclosure to a single verified reference file. Its weakness is redundancy: the same flag criteria appear in three sections and the Explain section covers platform behavior Claude already knows.

Suggestions

Merge the "Check" and "Code Review" sections into one checklist to eliminate the duplicated flag criteria (dimensions, aspect ratio, file size, URL, width/height tags) currently repeated in Quick Reference as well.

Trim or cut the "Explain" section, since how social platforms use og:image and crop wrongly sized images is knowledge Claude already has; keep only the rule-specific thresholds.

DimensionReasoningScore

Conciseness

The "Explain" section restates platform behavior Claude already knows ("Social platforms use og:image to construct the visual card shown when a URL is shared"), and the flag criteria are repeated across "Quick Reference", "Check", and "Code Review". It is mostly efficient given the short length, so above 2, but the duplication and known-concept explanation could be trimmed, so below 4.

3 / 5

Actionability

Concrete thresholds throughout: "1200×630 pixels (1.91:1 aspect ratio)", "under 5 MB", "Export as JPEG at 80–85% quality", "og:image:width and og:image:height tags". As an instruction-only skill the guidance is actionable and specific, but no copy-paste commands or examples appear in the body itself, keeping it below 5.

4 / 5

Workflow Clarity

The Check → Fix sequence carries explicit flag conditions ("Flag if width < 1200px, height < 630px, aspect ratio differs significantly from 1.91:1, or file size exceeds 5 MB"). Not 5 because "Check" and "Code Review" are two overlapping checklists rather than one unambiguous sequence, and there is no post-fix verification step.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md". The referenced file exists and contains only external links, with no nested file references.

5 / 5

Total

16

/

20

Passed

Description

70%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.

A solid description with a clear domain, two concrete actions, an explicit "Use when" trigger, and good natural keywords. Its main weakness is limited action coverage and missing common synonyms for social previews and link cards.

Suggestions

Add one or two more concrete actions to the description, e.g. resizing images to platform-recommended dimensions or validating og:image:width/og:image:height tags, to raise specificity.

Include natural synonyms users would say, such as "social preview", "share card", or "link preview", to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"auditing Open Graph tags or generating og:image assets" names the domain plus exactly two concrete actions, matching the 1-2-concrete-actions anchor. It is not 4 because no additional specific actions are explicitly stated, and not 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

Both what ("auditing Open Graph tags or generating og:image assets") and when ("Use when auditing...; Applies to any page that may be shared on social networks or messaging platforms") are explicitly present, clearing the missing-trigger cap. Not 5 because the trigger phrases could be more concrete, e.g. naming what the user would mention (og:image, social previews).

4 / 5

Trigger Term Quality

"Open Graph tags", "og:image", "social networks", and "messaging platforms" are natural phrases a user would say. It falls short of 5 because common synonyms like "social preview", "share card", or "link preview" are missing.

4 / 5

Distinctiveness Conflict Risk

Open Graph / og:image is a clear niche with distinct triggers and minimal conflict risk. Not 5 because "generating og:image assets" slightly overlaps with general image-generation or asset-creation skills.

4 / 5

Total

15

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/og-image-size/SKILL.md

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.