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

87%

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

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-structured, actionable overview that defers detail to a real one-level reference and gives exact numeric guidance. Its main weakness is mild verbosity and redundancy (the Explain section and overlapping Check/Code Review content).

Suggestions

Tighten the 'Explain' section or merge it with the intro, since it restates social-platform cropping behavior Claude already knows.

De-duplicate the Check and Code Review sections, which repeat the same dimension/size/URL criteria.

Consider trimming the Quick Reference bullets that simply restate thresholds already detailed in the Check and Fix sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight with concrete thresholds, but the 'Explain' section restates social-platform behavior Claude already knows and Quick Reference/Check/Code Review overlap, so it is efficient with some unnecessary explanation that could be trimmed.	2 / 3
Actionability	Provides concrete, specific, copy-ready guidance: exact dimensions (1200×630, 600×315), aspect ratio 1.91:1, file-size limits (5 MB / 1 MB), JPEG 80–85%, absolute HTTPS URLs, and og:image:width/height tags.	3 / 3
Workflow Clarity	A clear Check→Flag→Fix sequence with explicit flagging conditions; the task is a non-destructive audit so the absence of a destructive-operation validation loop does not cap the score.	3 / 3
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep reference to references/rule.md (a real file) plus the source rule page, with content appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 uses proper third-person trigger phrasing and clearly answers both what and when with natural keywords and a distinct niche. Its only weakness is a somewhat narrow action list (audit, generate) rather than a fuller enumeration of capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('auditing Open Graph tags or generating og:image assets'), but the action list is limited rather than a comprehensive enumeration, matching the anchor that names a domain and some actions.	2 / 3
Completeness	An explicit 'Use when...' clause answers both what (audit/generate OG tags and assets) and when ('auditing Open Graph tags or generating og:image assets. Applies to any page that may be shared'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes natural terms users would say when needing this skill ('Open Graph tags', 'og:image', 'og:image assets', 'social networks', 'messaging platforms'), giving good coverage rather than just a few relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The og:image / Open Graph niche is distinct with specific triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	11 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/og-image-size/SKILL.md
Commit: 48405aa

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