open-graph-creator
Open Graph Creator - Auto-activating skill for Frontend Development. Triggers on: open graph creator, open graph creator Part of the Frontend Development skill category.
36
3%
Does it follow best practices?
Impact
97%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/open-graph-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, essentially just restating the skill name with no substantive information about capabilities or usage triggers. It reads like auto-generated boilerplate rather than a crafted description. It would be nearly impossible for Claude to reliably select this skill from a pool of alternatives based on this description alone.
Suggestions
Add specific concrete actions such as 'Generates Open Graph meta tags (og:title, og:description, og:image), creates social media preview cards, and configures link sharing metadata for web pages.'
Add an explicit 'Use when...' clause with natural trigger terms like 'Use when the user mentions og tags, social media previews, link previews, sharing metadata, og:image, or wants to control how links appear on Facebook/Twitter/LinkedIn.'
Remove the redundant duplicate trigger term 'open graph creator, open graph creator' and replace with diverse natural language variations users would actually say.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Open Graph Creator', 'Frontend Development') but describes no concrete actions. There are no specific capabilities listed such as generating meta tags, creating preview images, or configuring OG properties. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. There is no explicit 'Use when...' clause. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'open graph creator' repeated twice. Missing natural variations users would say like 'og tags', 'social media preview', 'meta tags', 'link preview', 'og:image', 'open graph meta', or 'social sharing'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Open Graph Creator' is somewhat specific to a niche (OG meta tags/previews), which provides some distinctiveness. However, the vague 'Frontend Development' category label could cause overlap with other frontend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template/placeholder with no actual content about Open Graph tags or metadata creation. It contains only generic boilerplate descriptions that could apply to any skill topic, providing zero value to Claude for performing Open Graph-related tasks. The entire file needs to be rewritten with actual technical content.
Suggestions
Replace the boilerplate with actual Open Graph meta tag examples, including required tags (og:title, og:type, og:image, og:url) with executable HTML snippets.
Add a concrete workflow for creating Open Graph tags: inspect page content → generate appropriate meta tags → validate with og:debugger or similar tools → output final HTML.
Include specific code examples for framework integrations (React Helmet, Vue Meta, Next.js Head) since the skill claims to cover React and Vue.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable content like tag specifications, image size requirements, and common patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content, code, or specific guidance about Open Graph tags/metadata. Every token is wasted on boilerplate. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No code examples, no Open Graph meta tag formats, no HTML snippets, no specific commands or patterns. The content only describes what it could do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The phrase 'step-by-step guidance' is mentioned but never delivered. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to external files, no structured sections with real content, and no navigation to deeper materials. The sections that exist contain no substantive information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.