HTML Metadata Fixer
ibelick/ui-skills
Audits and fixes page titles, meta descriptions, canonical URLs, Open Graph and Twitter cards, favicons, JSON-LD and robots directives.
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.
$ npx skills add thedaviddias/Front-End-Checklist --skill faq -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist faq --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/faq .claude/skills/faq && 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 "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .claude/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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/faqType 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 faq -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist faq --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/faq .agents/skills/faq && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .agents/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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 faq -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist faq --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/faq .cursor/skills/faq && 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 "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .cursor/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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/faq--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 faq -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist faq --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/faq .gemini/skills/faq && 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 "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .gemini/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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 faqInstalls 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 faq -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/faq .github/skills/faq && 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 "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .github/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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 faq -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 faq --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/faq .opencode/skills/faq && 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 "faq" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/faq into .opencode/skills/faq/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "faq", 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.
faqAdds, 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.
The skill covers FAQPage structured data: a JSON-LD script with a mainEntity array of Question objects, each holding the question text as name and an acceptedAnswer of type Answer with a text property. It applies only to pages whose question-and-answer content is visible to visitors.
It works in several modes. Check inspects each FAQ page for the script block, the array and the answer fields. Fix finds the FAQ sections, writes the JSON-LD into the head or body and runs it through Google's Rich Results Test. Explain describes why mismatched markup is ignored and may draw a manual action, and Code Review parses every ld+json block and compares each marked-up question with one visible on the page. Longer implementation notes sit in references/rule.md.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
schema.orgAlso links to:
search.google.comfrontendchecklist.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
FAQPage Schema Markup loads about 774 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 319 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.
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.
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 319 words, ~774 tokens.
.claude/skills/faq/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Valid FAQPage structured data can generate rich results in Google Search, displaying expandable question-and-answer pairs directly in the SERP. This increases click-through rate and SERP real estate without requiring a higher ranking position.
FAQPage JSON-LD with mainEntity question/answer pairs to pages that contain FAQ sectionsQuestion must include acceptedAnswer with an Answer type containing the text propertyCheck pages that contain FAQ or Q&A sections. For each: (1) Is there a <script type="application/ld+json"> block with "@type": "FAQPage"? (2) Does it include a mainEntity array of Question objects? (3) Does each Question have a name (the question text) and an acceptedAnswer with "@type": "Answer" and a text property? (4) Does the schema content match what is visible on the page?
<head> or <body>:{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How do I reset my password?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Click 'Forgot password' on the login page and enter your email address. You will receive a reset link within 5 minutes."
}
}
]
}FAQPage structured data enables Google to display expandable Q&A pairs directly in search results as a rich result. This increases the page's visible footprint in the SERP and can improve click-through rate. Invalid or mismatched schema (questions in markup not visible on page) will cause Google to ignore it and may trigger a manual action.
Parse all <script type="application/ld+json"> blocks. Find any with "@type": "FAQPage". Validate that mainEntity is an array, each item has "@type": "Question", name is a non-empty string, and acceptedAnswer is an object with "@type": "Answer" and a non-empty text. Cross-reference each question in the schema against visible question elements on the page.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/faq
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in skills/faq of thedaviddias/Front-End-Checklist.
Open the folder on GitHubat commit e8d14d0
FAQPage Schema Markup 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 |
|---|---|---|---|---|---|---|
| FAQPage Schema Markup this skillthedaviddias/Front-End-Checklist | 74k | — | ~774 | Automated safety check: Pass | MIT | |
| HTML Metadata Fixeribelick/ui-skills | 9.6k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Roier SEOdavila7/claude-code-templates | 33k | — | ~2.7k | Automated safety check: Pass | MIT | |
| SEO Validatesoftspark/ai-toolkit | 179 | — | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Site ArchitectureAvdLee/RocketSimApp | 805 | 11 repos | ~3.3k | Automated safety check: Pass | Custom licence | |
| SEO Optimizerailabs-393/ai-labs-claude-skills | 455 | 1 repos | ~3.2k | Automated safety check: Pass | MIT |
ibelick/ui-skills
Audits and fixes page titles, meta descriptions, canonical URLs, Open Graph and Twitter cards, favicons, JSON-LD and robots directives.
davila7/claude-code-templates
Technical SEO auditor and fixer. An agent skill from davila7/claude-code-templates.
softspark/ai-toolkit
SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.
AvdLee/RocketSimApp
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
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.
ever-works/ever-works
Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.
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.
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.
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.
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).
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.
thedaviddias/Front-End-Checklist
Finds two or three well-maintained npm packages for a Front-End Checklist rule, checks download and release thresholds, and adds them to the rule's frontmatter.
Categories
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. The skill covers FAQPage structured data: a JSON-LD script with a mainEntity array of Question objects, each holding the question text as name and an acceptedAnswer of type Answer with a text property. It applies only to pages whose question-and-answer content is visible to visitors.
FAQPage Schema Markup fits situations like: adding an FAQ section to a landing page or blog post; generating FAQPage JSON-LD from Q&A content already on a page; validating structured data on pages with FAQ sections; reviewing templates for markup that does not match visible content.
Run `npx skills add thedaviddias/Front-End-Checklist --skill faq -a claude-code`. Or copy the skill folder (skills/faq in thedaviddias/Front-End-Checklist) into .claude/skills/faq in your project. Claude Code loads it when a task matches its description.
Run `npx skills add thedaviddias/Front-End-Checklist --skill faq -a codex`. Or copy the skill folder (skills/faq in thedaviddias/Front-End-Checklist) into .agents/skills/faq in your project. Codex loads it when a task matches its description.
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 faq -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/faq, .gemini/skills/faq, .github/skills/faq and .opencode/skills/faq in your project.
SKILL.md names no scripts, command-line tools or credentials: FAQPage Schema Markup is instructions for the agent only.
SKILL.md names 3 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: search.google.com and frontendchecklist.io. This is read from the text; nothing was executed.
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.
FAQPage Schema Markup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 774 tokens (SKILL.md is roughly 3.1k 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.
Skills that share tags, products or a category with FAQPage Schema Markup: HTML Metadata Fixer (ibelick/ui-skills, 9.6k stars), Roier SEO (davila7/claude-code-templates, 33k stars), SEO Validate (softspark/ai-toolkit, 179 stars) and Site Architecture (AvdLee/RocketSimApp, 805 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.