CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

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 lean, well-structured single-purpose skill body with excellent progressive disclosure — the body stays an overview and correctly defers code examples and verification detail to a real, one-level-deep reference file. The main gaps are in actionability: the body's check/fix instructions are specific enough but lack any inline executable detail, and the verification procedure is named but not described.

Suggestions

Inline one minimal concrete check or snippet in the body — e.g., a compact byline HTML pattern or the specific things to inspect in the rendered page (visible name, rel="author" link, role/credentials) — so the Check section is actionable without opening the reference.

State the verification method briefly in the body (e.g., 'Fetch the rendered page (not the source template) and confirm the byline appears in the response HTML and any author structured data is valid'), instead of only 'describe how to verify the final page output'.

Add an explicit post-fix re-check step to close the feedback loop (fix → re-fetch rendered page → confirm byline present), which would lift workflow clarity from good to fully checkpointed.

DimensionReasoningScore

Conciseness

The body is short and directive with no padding: Quick Reference bullets, one-sentence Check/Fix/Explain sections, and a pointer to the reference file. It is not a 5 because the opening line ("A visible author byline is a critical E-E-A-T signal, helping users and search engines identify the person responsible...") explains background Claude largely already knows and could be trimmed.

4 / 5

Actionability

The Fix section is reasonably concrete ("Add an author section to the article header that includes the author's name, role, and a link to their profile") and the Quick Reference lists three specific requirements, but the body contains no executable example or concrete verification procedure — the HTML markup and detailed verification steps live entirely in references/rule.md, and 'describe how to verify the final page output' stops short of saying how. This matches 'some concrete guidance but incomplete; missing key details' rather than 'mostly executable' (4).

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent sequence for this single-purpose audit skill, and verification is explicitly instructed ("Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output"), so it exceeds the 'checkpoints missing or implicit' anchor (3). It is not a 5 because the verification method is delegated rather than stated and there is no re-check-after-fix loop.

4 / 5

Progressive Disclosure

The ~30-line body is a genuine overview: quick reference, the core check/fix/explain flow, and a clearly signaled one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — to a file that actually exists and holds the HTML example and verification detail. Content is appropriately split between overview body and reference, matching the 'clear overview with well-signaled one-level-deep references' anchor exactly.

5 / 5

Total

16

/

20

Passed

Description

66%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 competent description with an explicit 'Use when' trigger clause, third-person-style concrete actions, and a genuinely useful differentiator (verify rendered output, not source files). Its weaknesses are a two-verb capability statement that undersells the skill's full scope and a boilerplate opening that raises collision risk with sibling SEO-rule skills.

Suggestions

Lead with the skill's full capability set (e.g., 'Checks article templates for visible author bylines, flags missing byline markup in rendered HTML, and fixes the article header') so the 'what' is concrete and comprehensive, then keep the existing 'Use when' clause.

Replace the generic opening 'auditing metadata, crawlability, structured data, or indexability' with byline-specific triggers (e.g., 'Use when auditing SEO, E-E-A-T signals, or author attribution on article pages') to reduce overlap with sibling SEO-rule skills that share the same boilerplate.

Add natural synonyms users would say, such as 'SEO', 'author attribution', or 'bio page', to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description names its domain ("auditing metadata, crawlability, structured data, or indexability") and two concrete action types (audit, "Verify the rendered HTML and HTTP response rather than relying only on source files"), which matches the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because the audit objects are variations of a single verb rather than several distinct actions, and coverage of the skill's full behavior (check, fix, explain) is incomplete.

3 / 5

Completeness

Both parts are explicit: the 'when' is stated directly ("Use when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines") and the 'what' is stated as "Verify the rendered HTML and HTTP response rather than relying only on source files". It is not a 5 because the 'what' covers only the verification method rather than the full capability set (check, fix, explain), so it is narrower than the model 5-answer.

4 / 5

Trigger Term Quality

Natural trigger terms are present and domain-appropriate: "auditing", "metadata", "crawlability", "structured data", "indexability", "rendered HTML", "HTTP response", "author bylines". It is not a 5 because common user phrasings like "SEO", "search engines", or "byline" variants beyond the exact rule name are missing.

4 / 5

Distinctiveness Conflict Risk

The trailing clause "related to Display clear author bylines" carves out a niche, but the leading boilerplate ("Use when auditing metadata, crawlability, structured data, or indexability") is generic SEO-audit language that would equally trigger sibling SEO-rule skills in this family, so overlap with closely related skills is real. It is not a 4 because the differentiator is only the rule name appended at the end of otherwise shared phrasing.

3 / 5

Total

14

/

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-byline/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.