CtrlK
BlogDocsLog inGet started
Tessl Logo

share-buttons

Use when applies to blog posts, news articles, tutorials, and other long-form content. Less relevant for product pages, service pages, or home pages. Use when optimizing content distribution.

60

Quality

71%

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/share-buttons/SKILL.md
SKILL.md
Quality
Evals
Security

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-organized, concise overview with a clear check-fix-review workflow and a properly signaled one-level reference to the implementation details. Its main weakness is that the actionable share-URL templates live only in the reference rather than being inline in the Fix section.

DimensionReasoningScore

Conciseness

The body is lean (~30 lines) with tight bullets in Quick Reference and short Check/Fix/Explain/Code Review sections; it assumes Claude's competence and does not pad with background Claude already knows, with every section earning its place.

3 / 3

Actionability

The Fix section gives specific direction ("construct share URLs", "Use `window.location.href`", "Include `og:title` and `og:image`") but the executable detail — the actual platform share URL schemes — is deferred to references/rule.md rather than shown inline, so it is not copy-paste ready within the body.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear, and verification is explicit throughout ("Verify they use the correct share URL format", "Verify no heavy third-party share scripts are loaded", "describe how to verify the final page output"), which is appropriate for this simple single-purpose skill.

3 / 3

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep reference ("see `references/rule.md`"), and that reference file exists and holds the detailed code and platform guide, so content is appropriately split with easy navigation.

3 / 3

Total

11

/

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 gives strong, well-scoped trigger guidance for when to use the skill but fails to state what the skill actually does — share buttons and social sharing are never mentioned. It is functional but incomplete as a capability statement.

Suggestions

Lead with the concrete capability, e.g. "Adds social share buttons (X, LinkedIn, Facebook, WhatsApp) to article and blog post pages using privacy-friendly share URLs."

Include the natural trigger terms "share buttons" and "social sharing" that a user would actually say when they need this skill.

Merge the two "Use when..." clauses into one explicit trigger to remove the awkward "Use when applies to" phrasing.

DimensionReasoningScore

Specificity

It names the domain ("long-form content", "blog posts, news articles, tutorials") and a vague action ("optimizing content distribution"), but never states the concrete capability (adding share buttons), so it stops at naming a domain with a weak implied action rather than listing specific actions.

2 / 3

Completeness

The "when" is explicit and even repeated ("Use when applies to...", "Use when optimizing..."), but the "what" is only weakly implied — the description never says the skill adds share buttons, so it does not clearly answer both what and when.

2 / 3

Trigger Term Quality

Natural content-type keywords ("blog posts", "news articles", "tutorials") are present, but the core share-related terms a user would actually say ("share buttons", "social sharing") are entirely missing, and "optimizing content distribution" reads as jargon.

2 / 3

Distinctiveness Conflict Risk

The content-type scoping ("blog posts, news articles, tutorials, and other long-form content") plus the explicit negative scoping ("Less relevant for product pages, service pages, or home pages") carves a clear niche and reduces overlap with other SEO skills.

3 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.