Render
LeoYeAI/openclaw-master-skills
Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy).
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
MITAuto-check passed
Install Html5 Semantic Elements
$ npx skills add thedaviddias/Front-End-Checklist --skill html5-semantic-elements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist html5-semantic-elements --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/html5-semantic-elements .claude/skills/html5-semantic-elements && 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 "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .claude/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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/html5-semantic-elementsType 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 html5-semantic-elements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist html5-semantic-elements --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/html5-semantic-elements .agents/skills/html5-semantic-elements && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .agents/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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 html5-semantic-elements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist html5-semantic-elements --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/html5-semantic-elements .cursor/skills/html5-semantic-elements && 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 "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .cursor/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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/html5-semantic-elements--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 html5-semantic-elements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist html5-semantic-elements --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/html5-semantic-elements .gemini/skills/html5-semantic-elements && 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 "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .gemini/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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 html5-semantic-elementsInstalls 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 html5-semantic-elements -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/html5-semantic-elements .github/skills/html5-semantic-elements && 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 "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .github/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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 html5-semantic-elements -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 html5-semantic-elements --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/html5-semantic-elements .opencode/skills/html5-semantic-elements && 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 "html5-semantic-elements" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/html5-semantic-elements into .opencode/skills/html5-semantic-elements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "html5-semantic-elements", 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
html5-semantic-elements- GitHub stars
- 74k
- Token cost
- ~449 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 reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
- Reviewing templates
- 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
- Shared components related to Use semantic HTML elements
What it does
Html5 Semantic Elements is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements. Validate the final browser-facing markup, not just the source framework abstraction.
Its SKILL.md is about 450 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`).
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
- Reviewing templates
- Shared components related to Use semantic HTML elements
Example prompts
- “/html5-semantic-elements”
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
Html5 Semantic Elements loads about 449 tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 170 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). 170 words, ~449 tokens.
Download SKILL.mdSave it as
.claude/skills/html5-semantic-elements/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- html5-semantic-elements
- description
- Use when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements. Validate the final browser-facing markup, not just the source framework abstraction.
- metadata.category
- html
- metadata.priority
- high
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 15
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/html/html5-semantic-elements
Use semantic HTML elements
Screen readers use semantic elements to navigate pages—users can jump directly to <main> content or <nav>. Search engines also use semantics to understand content hierarchy.
Quick Reference
- Use
<header>,<main>,<footer>for page structure - Use
<article>for self-contained content,<section>for grouped content - Use
<nav>for navigation,<aside>for related/sidebar content - Only one
<main>per page, but multiple<header>/<footer>allowed
Check
Review this HTML structure to ensure it uses appropriate semantic elements like header, main, section, article, aside, and footer instead of generic div elements.
Fix
Replace generic div elements with semantic HTML5 elements that accurately describe the content structure and purpose.
Explain
Explain how semantic HTML elements improve accessibility, SEO, and code maintainability by providing meaningful structure to web content.
Code Review
Review templates, server-rendered HTML, and shared components that output markup related to Use semantic HTML elements. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/html/html5-semantic-elements
© 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/html5-semantic-elements of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Html5 Semantic Elements 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 |
|---|---|---|---|---|---|---|
| Html5 Semantic Elements this skillthedaviddias/Front-End-Checklist | 74k | — | ~449 | Automated safety check: Pass | MIT | |
| RenderLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Scaffold Elementremotion-dev/remotion | 62k | — | ~202 | Automated safety check: Pass | Custom licence | |
| Semantic Versioningsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Markdown Renderingsickn33/agentic-awesome-skills | 47k | 1 repos | ~751 | Automated safety check: Pass | MIT | |
| Semantic Kernelgithub/awesome-copilot | 40k | 2 repos | ~756 | Automated safety check: Pass | MIT |
Similar skills
- Official
Scaffold Element
remotion-dev/remotion
Scaffold a new Remotion Element for development in the docs Remotion Studio.
Semantic Versioning
sickn33/agentic-awesome-skills
Automate versioning and changelog generation using semantic versioning principles.
Markdown Rendering
sickn33/agentic-awesome-skills
Open Markdown reliably in cmux panes and recover from blank rendered surfaces.
- Official
Semantic Kernel
github/awesome-copilot
Create, update, refactor, explain, or review Semantic Kernel solutions using shared guidance plus language-specific references for .NET and Python.
Render
Anil-matcha/awesome-muse-connectors
Inspect Render services and deploys: list services, list recent deploys.
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.
Questions about Html5 Semantic Elements
What does Html5 Semantic Elements do?
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements. Html5 Semantic Elements is an agent skill from thedaviddias/Front-End-Checklist. Use when reviewing templates, rendered HTML, or shared components related to Use semantic HTML elements.
When should I use Html5 Semantic Elements?
Html5 Semantic Elements fits situations like: reviewing templates; shared components related to Use semantic HTML elements.
How do I install Html5 Semantic Elements in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill html5-semantic-elements -a claude-code`. Or copy the skill folder (skills/html5-semantic-elements in thedaviddias/Front-End-Checklist) into .claude/skills/html5-semantic-elements in your project. Claude Code loads it when a task matches its description.
How do I install Html5 Semantic Elements in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill html5-semantic-elements -a codex`. Or copy the skill folder (skills/html5-semantic-elements in thedaviddias/Front-End-Checklist) into .agents/skills/html5-semantic-elements in your project. Codex loads it when a task matches its description.
Can I use Html5 Semantic Elements 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 html5-semantic-elements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/html5-semantic-elements, .gemini/skills/html5-semantic-elements, .github/skills/html5-semantic-elements and .opencode/skills/html5-semantic-elements in your project.
What does Html5 Semantic Elements need to run?
SKILL.md names no scripts, command-line tools or credentials: Html5 Semantic Elements is instructions for the agent only.
Does Html5 Semantic Elements 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 Html5 Semantic Elements 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 Html5 Semantic Elements use?
Html5 Semantic Elements 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 Html5 Semantic Elements use?
About 449 tokens (SKILL.md is roughly 1.8k 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 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Html5 Semantic Elements?
Skills that share tags, products or a category with Html5 Semantic Elements: Render (LeoYeAI/openclaw-master-skills, 2.2k stars), Scaffold Element (remotion-dev/remotion, 62k stars), Semantic Versioning (sickn33/agentic-awesome-skills, 47k stars) and Markdown Rendering (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Html5 Semantic Elements?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,388 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.