Agent skill

Author Byline

by thedaviddias in thedaviddias/Front-End-Checklist

A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines.

MITAuto-check passedMarketing & SEO

Install Author Byline

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill author-byline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist author-byline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/author-byline .claude/skills/author-byline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
author-byline
GitHub stars
74k
Token cost
~409 tokens
SKILL.md length
170 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines.

  • Auditing metadata
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Structured data

What it does

Author Byline is an agent skill from thedaviddias/Front-End-Checklist. 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.

Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).

It sits in Marketing & SEO, covering Technical SEO and Schema markup. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.

When your agent uses it

  • Auditing metadata
  • Structured data
  • Indexability related to Display clear author bylines

Example prompts

  • “/author-byline”

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Author Byline loads about 409 tokens when it runs, and up to ~962 if it reads all its reference files. Until then it costs about 54 tokens; SKILL.md has 170 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~409
With references · SKILL.md plus every file in references/, read only if the agent opens them
~962

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 170 words, ~409 tokens.

Download SKILL.mdSave it as .claude/skills/author-byline/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
author-byline
description
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.
metadata.category
seo
metadata.priority
medium
metadata.difficulty
beginner
metadata.estimatedTime
5
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/seo/author-byline

Display clear author bylines

A visible author byline is a critical E-E-A-T signal, helping users and search engines identify the person responsible for the content and their level of expertise.

Quick Reference

  • Ensure every article has a visible author name prominently displayed
  • Link the author's name to a detailed bio page to establish expertise
  • Include the author's credentials or professional role near their name

Check

Verify that all articles and blog posts have a clearly visible author byline.

Fix

Add an author section to the article header that includes the author's name, role, and a link to their profile.

Explain

Explain why author transparency is a key factor in Google's Quality Rater Guidelines and how it affects trust.

Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Display clear author bylines. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/author-byline

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/author-byline of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

Author Byline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Author Byline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Author Byline this skillthedaviddias/Front-End-Checklist74k—~409Automated safety check: PassMIT
GEO-First SEO Audit Toolzubair-trabzada/geo-seo-claude11k—~2.8kAutomated safety check: NotesMIT
SEO Optimizerailabs-393/ai-labs-claude-skills4551 repos~3.2kAutomated safety check: PassMIT
SEO and GEO Auditdageno-agents/seo-geo-audit176—~2kAutomated safety check: PassMIT
SEO Setupalisamadiii/Portfolio180—~1.7kAutomated safety check: PassNone
SEOever-works/ever-works16210 repos~2.9kAutomated safety check: PassMIT

Similar skills

  • GEO-First SEO Audit Tool

    zubair-trabzada/geo-seo-claude

    Audits a website for AI search visibility across ChatGPT, Claude, Perplexity and Google AI Overviews while checking traditional SEO, schema and E-E-A-T content quality.

    11k GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check: notes
  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    455 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • SEO and GEO Audit

    dageno-agents/seo-geo-audit

    Runs one prioritized audit that combines technical SEO, content quality, trust signals, entity clarity and AI search readiness for a page, site or domain.

    176 GitHub stars~2k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed
  • SEO Setup

    alisamadiii/Portfolio

    Full SEO/metadata setup and audit for client websites (Astro, Next.js, any static site).

    180 GitHub stars~1.7k tokensUpdated 4 days ago
    Marketing & SEOAuto-check passed
  • SEO

    ever-works/ever-works

    Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.

    162 GitHub starsUsed in 10 repos~2.9k tokens
    Marketing & SEOAuto-check passed
  • Universal SEO Analysis

    AgriciDaniel/claude-seo

    Hub for site-wide SEO work: audits, technical checks, schema, content quality, local, hreflang and AI-search readiness, run through slash commands.

    19k GitHub stars~4.9k tokensUpdated 6 days ago
    Marketing & SEOAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 5 days ago
    Auto-check passed
  • FAQPage Schema Markup

    thedaviddias/Front-End-Checklist

    Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

    74k GitHub stars~774 tokensUpdated 5 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 5 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 5 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 5 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 5 days ago
    Auto-check passed

Categories

Questions about Author Byline

What does Author Byline do?

A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines. Author Byline is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing metadata, crawlability, structured data, or indexability related to Display clear author bylines.

When should I use Author Byline?

Author Byline fits situations like: auditing metadata; structured data; indexability related to Display clear author bylines.

How do I install Author Byline in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill author-byline -a claude-code`. Or copy the skill folder (skills/author-byline in thedaviddias/Front-End-Checklist) into .claude/skills/author-byline in your project. Claude Code loads it when a task matches its description.

How do I install Author Byline in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill author-byline -a codex`. Or copy the skill folder (skills/author-byline in thedaviddias/Front-End-Checklist) into .agents/skills/author-byline in your project. Codex loads it when a task matches its description.

Can I use Author Byline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill author-byline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/author-byline, .gemini/skills/author-byline, .github/skills/author-byline and .opencode/skills/author-byline in your project.

What does Author Byline need to run?

SKILL.md names no scripts, command-line tools or credentials: Author Byline is instructions for the agent only.

Does Author Byline access the network?

SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.

Is Author Byline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Author Byline use?

Author Byline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Author Byline use?

About 409 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 553 tokens, read only when the agent opens those files.

What are the alternatives to Author Byline?

Skills that share tags, products or a category with Author Byline: GEO-First SEO Audit Tool (zubair-trabzada/geo-seo-claude, 11k stars), SEO Optimizer (ailabs-393/ai-labs-claude-skills, 455 stars), SEO and GEO Audit (dageno-agents/seo-geo-audit, 176 stars) and SEO Setup (alisamadiii/Portfolio, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Author Byline?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.