CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

og-url-match

Use when auditing Open Graph tags or investigating why social share counts appear low. Applies to any page with both canonical-url and og:url tags.

Quality

78%

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-url-match/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 concise, well-structured single-purpose audit skill with concrete comparison criteria, an actionable fix, and clean one-level-deep progressive disclosure to references/rule.md. The main improvement is removing duplication: Check vs Code Review and the intro vs Explain cover the same ground twice.

Suggestions

Merge the 'Check' and 'Code Review' sections — both repeat the same comparison procedure; keep one with the enumerated mismatch types (protocol, www, query string, trailing slash).

Fold the opening paragraph's share-count explanation into 'Explain' to remove the second duplication.

Add a short worked example (a snippet with an og:url/canonical mismatch and the corrected tag) to make the guidance fully copy-paste concrete.

DimensionReasoningScore

Conciseness

The body is short and mostly lean, but contains clear duplication: the 'Check' and 'Code Review' sections both instruct 'Compare the og:url meta tag value with the <link rel='canonical'> href value... Flag any page where they differ', and the intro paragraph overlaps with the 'Explain' section on share counts being split across URL variants. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' — above 2 because there is no padded background instruction, below 4 because the duplicated sections should be merged.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: exact tags to inspect (<meta property='og:url'>, <link rel='canonical'>), specific mismatch dimensions ('different protocols (http vs https), www vs non-www mismatch, query string differences, trailing slash inconsistencies'), and a specific fix ('Set og:url to exactly the same absolute HTTPS URL as the canonical tag. Remove any UTM parameters, session IDs, or tracking tokens'). Below 5 only because there is no worked example of a mismatching page and its corrected output.

4 / 5

Workflow Clarity

This is a simple, single-purpose, read-only audit skill (~30 lines), so the simple-skill exception applies: the single action (compare og:url to canonical, flag differences, then fix) is unambiguous and the Check → Fix sequence is clear. No destructive or risky operation is involved, so no validation cap applies; anchor 5 for simple skills is the best fit.

5 / 5

Progressive Disclosure

The under-50-line body is well organized into Quick Reference / Check / Fix / Explain / Code Review sections, and the single external pointer is clearly signaled at the end ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`'). The referenced file exists and contains no further nested references, so references are one level deep and easy to navigate — anchor 5.

5 / 5

Total

17

/

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 niche description with explicit, natural 'Use when' triggers and third-person-appropriate phrasing. Its main weakness is that the 'what' stays at the level of 'auditing Open Graph tags' without naming the concrete compare/flag/fix operations, and the broad OG-audit trigger slightly overstates the skill's og:url-specific scope.

Suggestions

State the core action in the description, e.g. 'Compares each page's og:url meta tag against its canonical URL and flags/fixes mismatches that split social share counts.'

Narrow the lead trigger from 'auditing Open Graph tags' to 'auditing og:url or Open Graph URL tags' to reduce overlap with other og:property audits.

Add one or two common synonyms users might say, such as 'social previews' or 'SEO share-count audit', to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Use when auditing Open Graph tags or investigating why social share counts appear low" names the domain plus two concrete actions (auditing, investigating), but never states the actual operations the skill performs (comparing og:url against the canonical tag, flagging and fixing mismatches). It matches 'names domain and 1-2 concrete actions, but not comprehensive' — below 4 because it does not list several specific actions, above 2 because the actions named are concrete rather than generic.

3 / 5

Completeness

The 'when' is explicit and concrete ("Use when auditing Open Graph tags or investigating why social share counts appear low. Applies to any page with both canonical-url and og:url tags"), and a 'what' exists ("auditing Open Graph tags"), but the what stays broad — the specific compare-and-flag behavior only appears in the body. Both present with one side weaker fits anchor 4; not 5 because the what is not as explicit and concrete as the when.

4 / 5

Trigger Term Quality

Natural terms users would say are present: "Open Graph tags", "social share counts", "og:url", "canonical-url". Coverage is good and domain-specific, but common variations like "social preview", "share buttons", "SEO", or platform names (Facebook/Twitter cards) are missing, so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (og:url vs canonical tag matching) with distinct triggers like "og:url" and "canonical-url", giving low conflict risk. However, the lead trigger "auditing Open Graph tags" is broader than the skill's actual scope (other og: properties such as og:title or og:image audits), creating minor overlap risk with closely related OG/SEO skills — anchor 4.

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-url-match/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.