Azure Search Documents TS
microsoft/skills
Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents).
A skill your agent uses when auditing content pages for AI discoverability.
Install LLM Parsability
$ npx skills add thedaviddias/Front-End-Checklist --skill llm-parsability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist llm-parsability --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/llm-parsability .claude/skills/llm-parsability && 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 "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .claude/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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/llm-parsabilityType 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 llm-parsability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist llm-parsability --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/llm-parsability .agents/skills/llm-parsability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .agents/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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 llm-parsability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist llm-parsability --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/llm-parsability .cursor/skills/llm-parsability && 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 "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .cursor/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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/llm-parsability--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 llm-parsability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist llm-parsability --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/llm-parsability .gemini/skills/llm-parsability && 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 "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .gemini/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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 llm-parsabilityInstalls 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 llm-parsability -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/llm-parsability .github/skills/llm-parsability && 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 "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .github/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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 llm-parsability -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 llm-parsability --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/llm-parsability .opencode/skills/llm-parsability && 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 "llm-parsability" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/llm-parsability into .opencode/skills/llm-parsability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "llm-parsability", 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
llm-parsability- GitHub stars
- 74k
- Token cost
- ~687 tokens
- SKILL.md length
- 314 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 content pages for AI discoverability.
- Auditing content pages for AI discoverability
- 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
- Tasks that involve Knowledge bases
What it does
LLM Parsability is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing content pages for AI discoverability. Applies to any informational page intended to appear in AI-generated answers, search snippets, or knowledge base extraction.
Its SKILL.md is about 690 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 Knowledge Management, covering Knowledge bases. It works with JavaScript. 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 content pages for AI discoverability
- Tasks that involve Knowledge bases
Example prompts
- “/llm-parsability”
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
LLM Parsability loads about 687 tokens when it runs, and up to ~2.1k if it reads all its reference files. Until then it costs about 49 tokens; SKILL.md has 314 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). 314 words, ~687 tokens.
Download SKILL.mdSave it as
.claude/skills/llm-parsability/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- llm-parsability
- description
- Use when auditing content pages for AI discoverability. Applies to any informational page intended to appear in AI-generated answers, search snippets, or knowledge base extraction.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 15
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/llm-parsability
Make content easy for LLMs to parse
AI assistants and answer engines (including Google's AI Overviews) extract and cite content from web pages—pages with clear structure and explicit context are more likely to be accurately cited and surfaced in AI-generated responses.
Quick Reference
- Use semantic HTML headings, paragraphs, and lists — LLMs prefer structured markup
- Avoid content locked behind JavaScript rendering or requiring user interaction
- Write clear, self-contained sections that make sense out of full-page context
- Structured data (JSON-LD) provides machine-readable context alongside human-readable text
Check
Evaluate whether the page content is parseable by an LLM. Check: (1) Is content in semantic HTML tags (<h1>–<h6>, <p>, <ul>, <ol>, <table>)? (2) Is key content accessible without JavaScript? (3) Are section headings descriptive enough to stand alone? (4) Does the page have JSON-LD structured data? (5) Are there FAQ sections or explicit Q&A patterns that match common search queries?
Fix
Restructure content into explicit HTML sections with descriptive headings. Replace JavaScript-rendered content with server-side rendered HTML. Add JSON-LD schema (Article, FAQPage, HowTo) to annotate the content type. Write headings and lead sentences that work as standalone answers—assume the reader only sees one paragraph.
Explain
Large language models and answer engines process web content by extracting text from HTML. Pages that use semantic markup, clear headings, and server-rendered content are parsed more accurately than JavaScript-heavy or visually-structured pages. As AI-generated answers increasingly cite specific web sources, well-structured content is more likely to be accurately quoted and linked.
Code Review
Check the page's rendered HTML for: (1) proper heading hierarchy (h1→h2→h3), (2) content wrapped in semantic elements (<article>, <section>, <main>), (3) key content visible in initial HTML response (not injected by JS), (4) presence of FAQPage, HowTo, or Article JSON-LD schema, (5) absence of content hidden behind modals, tabs, or accordions that require JS interaction.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/llm-parsability
© 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/llm-parsability of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
LLM Parsability 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 |
|---|---|---|---|---|---|---|
| LLM Parsability this skillthedaviddias/Front-End-Checklist | 74k | — | ~687 | Automated safety check: Pass | MIT | |
| Azure Search Documents TSmicrosoft/skills | 3.1k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 | |
| Knowledge Searchdataelement/bisheng | 12k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence | |
| Find And Citeoutline/outline | 41k | — | ~537 | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
Knowledge Search
dataelement/bisheng
Search the user's knowledge bases and knowledge spaces (企业知识库检索).
Capture Conversation
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Find And Cite
outline/outline
Answer questions from the Outline knowledge base with quotes and links to the source documents; use when the user asks what the team knows, documented, or decided about a topic.
Xhs Virtual Product
chenjin-cmd/xhs-virtual-product
This skill helps plan, select, produce, and market Xiaohongshu (RED) virtual/digital products — templates, knowledge bases, test tools, study materials.
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
Works with
Categories
Questions about LLM Parsability
What does LLM Parsability do?
A skill your agent uses when auditing content pages for AI discoverability. LLM Parsability is an agent skill from thedaviddias/Front-End-Checklist. Use when auditing content pages for AI discoverability.
When should I use LLM Parsability?
LLM Parsability fits situations like: auditing content pages for AI discoverability; tasks that involve Knowledge bases.
How do I install LLM Parsability in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill llm-parsability -a claude-code`. Or copy the skill folder (skills/llm-parsability in thedaviddias/Front-End-Checklist) into .claude/skills/llm-parsability in your project. Claude Code loads it when a task matches its description.
How do I install LLM Parsability in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill llm-parsability -a codex`. Or copy the skill folder (skills/llm-parsability in thedaviddias/Front-End-Checklist) into .agents/skills/llm-parsability in your project. Codex loads it when a task matches its description.
Can I use LLM Parsability 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 llm-parsability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/llm-parsability, .gemini/skills/llm-parsability, .github/skills/llm-parsability and .opencode/skills/llm-parsability in your project.
What does LLM Parsability need to run?
SKILL.md names no scripts, command-line tools or credentials: LLM Parsability is instructions for the agent only.
Does LLM Parsability 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 LLM Parsability 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 LLM Parsability use?
LLM Parsability 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 LLM Parsability use?
About 687 tokens (SKILL.md is roughly 2.7k 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.4k tokens, read only when the agent opens those files.
What are the alternatives to LLM Parsability?
Skills that share tags, products or a category with LLM Parsability: Azure Search Documents TS (microsoft/skills, 3.1k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars), Knowledge Search (dataelement/bisheng, 12k stars) and Capture Conversation (outline/outline, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains LLM Parsability?
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.