Content Writer
ViryaZheng/recomby-geo
Write SEO-optimized blog posts, landing pages, and long-form page copy following Google's E-E-A-T and Helpful Content guidelines.
A skill your agent uses when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.
Install H1
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist h1 --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/h1 .claude/skills/h1 && rm -rf skills-srcUse ~/.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/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .claude/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist h1 --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/h1 .agents/skills/h1 && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .agents/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist h1 --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/h1 .cursor/skills/h1 && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .cursor/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/h1--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist h1 --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/h1 .gemini/skills/h1 && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .gemini/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist h1Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/h1 .github/skills/h1 && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .github/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill h1 -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist h1 --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/h1 .opencode/skills/h1 && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "h1" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/h1 into .opencode/skills/h1/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "h1", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
h1- GitHub stars
- 74k
- Token cost
- ~734 tokens
- SKILL.md length
- 403 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 a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.
- Works in 6 steps: Ensure every page template outputs… → The H1 text should describe the page's… → Include the primary target keyword… → …
- Auditing a pages heading structure
- 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
What it does
H1 is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.
Its SKILL.md is about 730 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 Frontend & Design, covering On-page SEO, Landing pages and Blog and article writing. 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 a pages heading structure
- Generating H1 text for landing pages
- Reviewing a CMS template that may produce empty
- Missing H1 elements
Example prompts
- “/h1”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Ensure every page template outputs exactly one .
- The H1 text should describe the page's specific topic, not just the site name.
- Include the primary target keyword naturally in the H1 — do not force it awkwardly.
- If the page has multiple sections with separate H1 candidates, choose one main topic and demote others to H2.
- Verify the H1 is visible in the rendered DOM (not hidden via CSS display:none or visibility:hidden).
- In Next.js/React: ensure the H1 is in the page component, not in the shared layout.
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
H1 loads about 734 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 403 words of instructions outside code blocks.
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). 403 words, ~734 tokens.
Download SKILL.mdSave it as
.claude/skills/h1/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- h1
- description
- Use when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/h1
Use a single descriptive H1
The H1 is the most prominent heading on a page and a strong on-page ranking signal. Google uses it to understand the page's primary topic. Missing, duplicate, or keyword-free H1 tags reduce topical clarity, hurting rankings for the page's target terms.
Quick Reference
- Each page should have exactly one
<h1>tag that describes the page's primary topic with relevant keywords - The H1 does not need to be identical to the
<title>tag, but they should be topically consistent - Empty
<h1>tags, multiple<h1>tags on one page, or H1s containing only the brand name are all issues to fix
Check
Parse the rendered DOM of each page. Count all <h1> elements. Flag: (1) Pages with zero <h1> tags. (2) Pages with more than one <h1> tag. (3) <h1> elements whose text content is empty or contains only whitespace. (4) <h1> elements that contain only the brand name with no page-specific topic. (5) <h1> text that does not reflect the page's primary content topic.
Fix
- Ensure every page template outputs exactly one
<h1>. - The H1 text should describe the page's specific topic, not just the site name.
- Include the primary target keyword naturally in the H1 — do not force it awkwardly.
- If the page has multiple sections with separate H1 candidates, choose one main topic and demote others to H2.
- Verify the H1 is visible in the rendered DOM (not hidden via CSS
display:noneorvisibility:hidden). - In Next.js/React: ensure the H1 is in the page component, not in the shared layout.
Before:
<h1>Acme Corp</h1>(brand only) After:<h1>Project Management Software for Enterprise Teams</h1>
Show full SKILL.md (130 more words)Show less
Explain
Google's John Mueller has confirmed that H1 tags help Google understand page structure. While H1 is not the strongest ranking factor in isolation, it contributes to on-page topical relevance signals. Multiple H1 tags on one page dilute the primary topic signal; a missing H1 leaves a structural gap that reduces confidence in what the page is about.
Code Review
Query the DOM for all <h1> elements. Assert exactly one exists per page. Check that innerText.trim() is non-empty. Compare H1 text to the page <title> — they should share core topic keywords. Flag if H1 is inside a <header> element shared across all pages (often the site logo alt text) rather than specific to the page content.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/h1
© 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/h1 of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
H1 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| H1 this skillthedaviddias/Front-End-Checklist | 74k | — | ~734 | Automated safety check: Pass | MIT | |
| Content WriterViryaZheng/recomby-geo | 458 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Content Writeraaron-he-zhu/aaron-marketing-skills | 2.9k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Landing Page Generatorbuildfastwithai/gen-ai-experiments | 785 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Skill FinderAffitor/affiliate-skills | 701 | — | ~2.1k | Automated safety check: Pass | MIT | |
| SEO Content Writerthatrebeccarae/claude-marketing | 161 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Content Writer
aaron-he-zhu/aaron-marketing-skills
A skill your agent uses when the user asks to "write SEO content", "draft a blog post / landing page", "update outdated content", or "fix traffic/ranking decay"; two modes — new drafts pages with…
Landing Page Generator
buildfastwithai/gen-ai-experiments
Builds a single self-contained HTML landing page from a template with copy frameworks, four themes and SEO meta, then runs bundled audit scripts for conversion and speed.
Skill Finder
Affitor/affiliate-skills
Find the right Affitor skill for your goal. An agent skill from Affitor/affiliate-skills.
SEO Content Writer
thatrebeccarae/claude-marketing
SEO-optimized content creation with brand voice analysis and platform-specific frameworks.
Blog System Design
swyxio/skills
Design, build, or revise a technical blog as a product system.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent 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.
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.
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.
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.
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).
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.
Related
Categories
Questions about H1
What does H1 do?
A skill your agent uses when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements. H1 is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing a page's heading structure, generating H1 text for landing pages or blog posts, or reviewing a CMS template that may produce empty or missing H1 elements.
When should I use H1?
H1 fits situations like: auditing a pages heading structure; generating H1 text for landing pages; reviewing a CMS template that may produce empty; missing H1 elements.
How do I install H1 in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill h1 -a claude-code`. Or copy the skill folder (skills/h1 in thedaviddias/Front-End-Checklist) into .claude/skills/h1 in your project. Claude Code loads it when a task matches its description.
How do I install H1 in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill h1 -a codex`. Or copy the skill folder (skills/h1 in thedaviddias/Front-End-Checklist) into .agents/skills/h1 in your project. Codex loads it when a task matches its description.
Can I use H1 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 h1 -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/h1, .gemini/skills/h1, .github/skills/h1 and .opencode/skills/h1 in your project.
What does H1 need to run?
SKILL.md names no scripts, command-line tools or credentials: H1 is instructions for the agent only.
Does H1 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 H1 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 H1 use?
H1 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 H1 use?
About 734 tokens (SKILL.md is roughly 2.9k 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 1.2k tokens, read only when the agent opens those files.
What are the alternatives to H1?
Skills that share tags, products or a category with H1: Content Writer (ViryaZheng/recomby-geo, 458 stars), Content Writer (aaron-he-zhu/aaron-marketing-skills, 2.9k stars), Landing Page Generator (buildfastwithai/gen-ai-experiments, 785 stars) and Skill Finder (Affitor/affiliate-skills, 701 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains H1?
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.