CtrlK
BlogDocsLog inGet started
Tessl Logo

social-profiles

Use when applies to business websites, personal brand sites, and publisher sites. Use when setting up Organization schema or auditing E-E-A-T signals for sites in competitive or YMYL categories.

63

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/social-profiles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and token-efficient with excellent progressive disclosure, pointing cleanly to a real reference file. Its gaps are actionability and workflow clarity: no executable code in the body and no explicit validation checkpoint for verifying the schema output.

Suggestions

Include a minimal copy-paste-ready Organization JSON-LD snippet with a sameAs array directly in the body so the core action is executable without opening the reference.

Add an explicit validation checkpoint, e.g. "Validate with Google's Rich Results Test before deploying" as a final Fix/Verify step.

State how to confirm profile links resolve to active official accounts (e.g. check for non-404, recent activity) to close the verification gap noted in the Check section.

DimensionReasoningScore

Conciseness

The body is lean — a one-line intro, four Quick Reference bullets, and short Check/Fix/Explain/Code Review sections — with no padding about what schema or E-E-A-T is, matching the every-token-earns-its-place anchor at 3 rather than the could-be-tightened anchor at 2.

3 / 3

Actionability

Guidance names concrete specifics ("Organization / Person schema with a sameAs array containing ... LinkedIn, Twitter/X, Facebook") but the body itself contains no executable code, deferring all examples to references/rule.md, which fits the some-concrete-guidance-but-incomplete anchor at 2 rather than copy-paste-ready at 3.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review structure gives a clear sequence, but there is no explicit validation checkpoint (e.g. run a structured-data validator), so it matches the steps-present-but-checkpoints-implicit anchor at 2 rather than the explicit-validation anchor at 3.

2 / 3

Progressive Disclosure

The body is a concise overview with well-organized sections and a single clearly signaled one-level-deep pointer — "see references/rule.md" (a file that exists) — matching the clear-overview-with-one-level-references anchor at 3.

3 / 3

Total

10

/

12

Passed

Description

77%

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 has explicit Use-when triggers and concrete actions, giving it strong completeness and specificity. Its main weakness is that it never mentions the skill's actual subject — social profiles / sameAs — which weakens trigger-term coverage and distinctiveness.

Suggestions

Add the skill's core subject to the description, e.g. "Link the site to its official social profiles via sameAs schema" so the most natural trigger terms appear.

Include user-natural terms like "social media profiles," "sameAs," and "Organization / Person structured data" to improve trigger coverage beyond SEO jargon (E-E-A-T, YMYL).

Tighten the two consecutive "Use when" clauses into one to reduce redundancy while keeping the explicit trigger.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "setting up Organization schema" and "auditing E-E-A-T signals" — alongside concrete domains (business websites, personal brand sites, publisher sites, YMYL categories), matching the multi-action anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly answers both what (set up Organization schema, audit E-E-A-T signals) and when via two explicit "Use when ..." trigger clauses, satisfying the anchor-3 requirement rather than the when-implied anchor at 2.

3 / 3

Trigger Term Quality

Contains relevant terms ("Organization schema", "E-E-A-T signals", "YMYL") but omits the most natural trigger a user would say — "social profiles" / "social media" / "sameAs" — leaving common variations missing, which fits the anchor-2 example over the full-coverage anchor at 3.

2 / 3

Distinctiveness Conflict Risk

The schema/E-E-A-T niche is specific but the description never names "social profiles," so it reads like a generic SEO/schema skill that could overlap with sibling SEO rules, fitting the could-still-overlap anchor at 2 rather than the clear-distinct-niche anchor at 3.

2 / 3

Total

10

/

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.