CtrlK
BlogDocsLog inGet started
Tessl Logo

author-byline

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

64

Quality

77%

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/author-byline/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 clean, well-structured audit skill that uses progressive disclosure effectively, offloading detail to references/rule.md. The body's guidance is concrete but light on executable verification steps, which are deferred to the reference.

Suggestions

Add one or two executable verification snippets to the body (e.g. a curl/selector to confirm the byline renders in the DOM and is not client-injected after crawl), so the core check does not require opening the reference.

Include an explicit post-fix validation step in the workflow (e.g. 'Re-crawl the URL and confirm the byline is present in the rendered HTML before closing').

Trim the E-E-A-T explanatory opening sentence to assume Claude's familiarity and tighten the intro.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, with only mild over-explanation in the E-E-A-T intro sentence that Claude could be assumed to know.

4 / 5

Actionability

The Fix section gives a concrete instruction ('Add an author section... name, role, and a link to their profile') but the body lacks executable verification commands or selectors, delegating those to references/rule.md.

3 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review structure gives a clear simple-skill workflow, but there is no explicit post-fix validation checkpoint, leaving a minor gap below a 5.

4 / 5

Progressive Disclosure

A short, well-organized overview in SKILL.md with a single clearly signaled one-level-deep reference to references/rule.md (a real bundle file), making navigation easy.

5 / 5

Total

16

/

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.

A well-constructed description with an explicit trigger clause and concrete audit actions scoped to a specific SEO rule. Its main weakness is the templated prefix shared across sibling SEO skills, which creates minor conflict risk.

DimensionReasoningScore

Specificity

Names the SEO audit domain plus several specific areas ('metadata, crawlability, structured data, or indexability') and a concrete action ('Verify the rendered HTML and HTTP response'), with only minor coverage gaps.

4 / 5

Completeness

An explicit 'Use when auditing...' clause supplies concrete triggers while 'Verify the rendered HTML and HTTP response...' states the concrete actions, cleanly answering both what and when.

5 / 5

Trigger Term Quality

Includes natural SEO-audit keywords (metadata, crawlability, structured data, indexability, rendered HTML, HTTP response) a user would say, missing a few synonyms; not a 5 because no plain-language variants are present.

4 / 5

Distinctiveness Conflict Risk

The 'related to Display clear author bylines' scoping gives it a clear niche, though the templated 'auditing metadata, crawlability, structured data, or indexability' prefix overlaps with sibling frontendchecklist SEO skills.

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.

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.