CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

author-expertise

Use when auditing metadata, crawlability, structured data, or indexability related to Highlight author credentials and expertise. Verify the rendered HTML and HTTP response rather than relying only on source files.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The content is a well-organized, appropriately brief overview for a simple audit-and-fix skill: a clear Check/Fix/Explain/Code Review sequence, concrete instructions, and a correctly structured pointer to a single reference file for implementation detail. The main improvements are trimming the E-E-A-T background sentence and adding an explicit post-fix re-verification step.

Suggestions

Trim or remove the E-E-A-T background introduction, since it explains concepts Claude already knows and adds tokens without new guidance.

Add an explicit re-check step after the Fix section (e.g., "After applying the fix, re-run the Check on the rendered page to confirm the violation is resolved") to close the validation loop.

Inline one brief concrete example of compliant author-bio markup or structured data (or name the exact schema.org type to look for) so the Check step is verifiable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is lean and section-driven, with only minor trimmable over-explanation: the intro sentence "Demonstrating the expertise of the content creator is a core component of E-E-A-T, helping both users and search engines trust the accuracy of your information" is background Claude already knows, and expanding "YMYL (Your Money Your Life)" is redundant. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

As an instruction-only skill, its guidance is concrete and specific: "Include a short bio for each author highlighting their relevant qualifications", "Link to the author's social profiles or professional websites (e.g., LinkedIn)", "Flag exact routes or templates where search-facing output violates the rule", with implementation detail appropriately deferred to references/rule.md. Minor gaps (no inline example of compliant bio or structured-data markup, no concrete verification commands) keep it below the fully copy-paste-ready bar of anchor 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure plus a Quick Reference checklist gives a clear sequence with most checkpoints present. An explicit re-verify step after applying the Fix (a feedback loop confirming the violation is resolved) is missing, which fits 'clear sequence with most checkpoints present; minor validation gaps' rather than anchor 5's explicit validation steps and error-recovery loops.

4 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that clearly signals a single one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a real file containing no nested references. Content is appropriately split between the overview body and the detailed reference, matching the anchor for a clear overview with well-signaled one-level-deep references.

5 / 5

Total

17

/

20

Passed

Description

83%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.

The description is strong: it pairs an explicit, specific 'Use when' trigger clause with concrete verification actions and domain-appropriate trigger terms. Its only weaknesses are a few missing natural synonyms (e.g., author bio, E-E-A-T, schema markup) and some generic audit terms that could overlap with sibling SEO skills.

DimensionReasoningScore

Specificity

The description lists several specific actions and audit targets ("auditing metadata, crawlability, structured data, or indexability" and "Verify the rendered HTML and HTTP response rather than relying only on source files"), matching the anchor for several specific actions with minor gaps in coverage. It falls short of anchor 5 because it does not comprehensively cover the full task surface (e.g., fixing or reporting findings, bio markup specifics), and it exceeds anchor 3's '1-2 concrete actions' level.

4 / 5

Completeness

It explicitly answers both what and when: the trigger clause "Use when auditing metadata, crawlability, structured data, or indexability related to Highlight author credentials and expertise" gives concrete trigger phrases, and the what is concretely stated as "Verify the rendered HTML and HTTP response rather than relying only on source files". This matches the anchor-5 good-example structure; anchor 4 is ruled out because the 'when' is explicit and specific rather than improvable.

5 / 5

Trigger Term Quality

Natural terms are well covered ("auditing", "metadata", "crawlability", "structured data", "indexability", "author credentials", "rendered HTML", "HTTP response") and users in this domain would naturally say them. A few natural variants are missing (e.g., "author bio", "E-E-A-T", "schema markup", "rich results"), so it fits 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (author credentials and expertise auditing) with distinct triggers such as "author credentials and expertise" and "rendered HTML and HTTP response", keeping conflict risk low. However, leading terms like "metadata", "structured data", and "indexability" overlap with closely related sibling SEO audit skills, so it fits 'mostly distinct; minor overlap risk' rather than anchor 5's minimal conflict risk.

4 / 5

Total

17

/

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/author-expertise/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.