Core Web Vitals
theopenco/llmgateway
Diagnose and improve Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift in this repository's Next.js App Router frontends.
Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience.
Install Algo SEO Technical
$ npx skills add asgard-ai-platform/skills --skill algo-seo-technical -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install asgard-ai-platform/skills algo-seo-technical --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/asgard-ai-platform/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/algo-seo-technical .claude/skills/algo-seo-technical && 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 "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .claude/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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/asgard-ai-platform/skills/tree/main/algo-seo-technicalType 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 asgard-ai-platform/skills --skill algo-seo-technical -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install asgard-ai-platform/skills algo-seo-technical --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/algo-seo-technical .agents/skills/algo-seo-technical && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .agents/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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 asgard-ai-platform/skills --skill algo-seo-technical -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install asgard-ai-platform/skills algo-seo-technical --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/algo-seo-technical .cursor/skills/algo-seo-technical && 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 "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .cursor/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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/asgard-ai-platform/skills.git --path algo-seo-technical--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 asgard-ai-platform/skills --skill algo-seo-technical -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install asgard-ai-platform/skills algo-seo-technical --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/algo-seo-technical .gemini/skills/algo-seo-technical && 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 "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .gemini/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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 asgard-ai-platform/skills algo-seo-technicalInstalls 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 asgard-ai-platform/skills --skill algo-seo-technical -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/algo-seo-technical .github/skills/algo-seo-technical && 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 "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .github/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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 asgard-ai-platform/skills --skill algo-seo-technical -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install asgard-ai-platform/skills algo-seo-technical --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/asgard-ai-platform/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/algo-seo-technical .opencode/skills/algo-seo-technical && 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 "algo-seo-technical" agent skill from https://github.com/asgard-ai-platform/skills/tree/main/algo-seo-technical into .opencode/skills/algo-seo-technical/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "algo-seo-technical", 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
algo-seo-technical- GitHub stars
- 242
- Token cost
- ~1k tokens
- SKILL.md length
- 433 words
- Files
- 4 (incl. references)
- Skills in repo
- 207
- Repo updated
- First seen
- Licence
- MIT
At a glance
Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience.
- Works in 4 steps: Input Validation → Core Algorithm → Verification → …
- The user needs to diagnose page speed issues
- SKILL.md covers Overview, When to Use, Algorithm and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Algo SEO Technical is an agent skill from asgard-ai-platform/skills. Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience. Use this skill when the user needs to diagnose page speed issues, improve Largest Contentful Paint, reduce layout shift, or pass Google's page experience signals — even if they say 'my site is slow', 'Core Web Vitals failing', or 'page speed optimization'.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `examples/sample_scenario.md`, `references/crux-monitoring.md` and `references/optimization-techniques.md`).
It sits in Frontend & Design, covering Web performance. It works with Contentful. The repository describes itself as: 301 open-source coding agent skills across 22 domains — methodology, judgment & gotchas packaged as Claude Agent Skills for the Asgard AI Platform. The licence is MIT.
When your agent uses it
- The user needs to diagnose page speed issues
- Improve Largest Contentful Paint
- Reduce layout shift
- Pass Googles page experience signals — even if they say my site is slow
Example prompts
- “s page experience signals — even if they say”
- “Core Web Vitals failing”
- “page speed optimization”
- “/algo-seo-technical”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4e7f4f8. 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 (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Algo SEO Technical loads about 1k tokens when it runs, and up to ~7.2k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 433 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 asgard-ai-platform/skills at commit 4e7f4f8, republished under its MIT licence (© asgard-ai-platform). 433 words, ~1,042 tokens.
Download SKILL.mdSave it as
.claude/skills/algo-seo-technical/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- algo-seo-technical
- description
- Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience. Use this skill when the user needs to diagnose page speed issues, improve Largest Contentful Paint, reduce layout shift, or pass Google's page experience signals — even if they say 'my site is slow', 'Core Web Vitals failing', or 'page speed optimization'.
- metadata.category
- WP-35 SEO 演算法
- metadata.tags
- seo, core-web-vitals, performance, page-speed
Core Web Vitals Optimization
Overview
Core Web Vitals are Google's page experience metrics: LCP (loading), INP (interactivity), and CLS (visual stability). Measured on real user data (CrUX). Pass thresholds: LCP < 2.5s, INP < 200ms, CLS < 0.1.
When to Use
Trigger conditions:
- Diagnosing why a site fails Core Web Vitals assessment
- Optimizing page load performance for SEO
- Reducing layout shift or improving interactivity
When NOT to use:
- When the issue is content relevance, not speed (use content SEO)
- When analyzing link authority (use PageRank / backlink analysis)
Algorithm
IRON LAW: CrUX Field Data Is the Source of Truth
Lab scores (Lighthouse) that pass can still FAIL in the field.
Google ranks based on REAL USER data (75th percentile):
- LCP < 2.5s (Good), 2.5-4.0s (Needs Improvement), > 4.0s (Poor)
- INP < 200ms (Good), 200-500ms (Needs Improvement), > 500ms (Poor)
- CLS < 0.1 (Good), 0.1-0.25 (Needs Improvement), > 0.25 (Poor)Phase 1: Input Validation
Collect field data from CrUX API or Search Console. Run Lighthouse for lab baseline. Identify which metrics fail. Gate: Have both field and lab data; failing metrics identified.
Phase 2: Core Algorithm
LCP fixes: 1. Optimize largest element (hero image/text). 2. Preload critical resources. 3. Reduce server response time (TTFB). 4. Eliminate render-blocking resources.
INP fixes: 1. Break long tasks (> 50ms) into smaller chunks. 2. Reduce JavaScript execution time. 3. Use requestIdleCallback for non-critical work. 4. Minimize main thread blocking.
CLS fixes: 1. Set explicit dimensions on images/videos. 2. Reserve space for ads/embeds. 3. Avoid inserting content above existing content. 4. Use CSS contain for dynamic elements.
Phase 3: Verification
Re-run Lighthouse, deploy, then monitor CrUX for 28-day rolling average improvement. Gate: Lab scores pass; await field data confirmation (28-day cycle).
Phase 4: Output
Return audit results with specific fix recommendations prioritized by impact.
Output Format
{
"audit": {"lcp": {"value_ms": 3200, "status": "poor", "element": "hero-image.jpg", "fixes": ["preload", "compress"]}},
"metadata": {"url": "...", "data_source": "crux", "device": "mobile"}
}Examples
Sample I/O
Input: URL with LCP=4.1s, CLS=0.32, INP=150ms Expected: LCP and CLS flagged as poor; INP passes. Fix priorities: CLS (image dimensions) → LCP (hero image preload)
Show full SKILL.md (171 more words)Show less
Edge Cases
| Input | Expected | Why |
|---|---|---|
| SPA with client rendering | High LCP likely | No server-rendered content for LCP element |
| Page with ads | High CLS likely | Ad slots inject content dynamically |
| All metrics pass in lab | May still fail field | Real devices on slow networks differ from lab |
Gotchas
- Lab vs field gap: Lighthouse runs on a simulated fast device. Real users on 3G with old phones produce very different numbers.
- LCP element changes: The LCP element can differ across page loads (image vs text). Optimize for the MOST COMMON LCP element, not just one.
- CLS attribution: Layout shifts are blamed on the element that moved, but the CAUSE is often an element inserted above it. Trace the cause, not the symptom.
- INP replaced FID: As of March 2024, INP replaces FID. Old references to FID are outdated.
- 28-day lag: CrUX uses a 28-day rolling window. Fixes take up to a month to reflect in field data.
References
- For element-specific optimization techniques, see
references/optimization-techniques.md - For CrUX API usage and monitoring setup, see
references/crux-monitoring.md
© asgard-ai-platform, 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 3 other files (references) in algo-seo-technical of asgard-ai-platform/skills.
- SKILL.md
- examples/sample_scenario.md
- references/crux-monitoring.md
- references/optimization-techniques.md
Open the folder on GitHubat commit 4e7f4f8
Compare with similar skills
Algo SEO Technical 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 |
|---|---|---|---|---|---|---|
| Algo SEO Technical this skillasgard-ai-platform/skills | 242 | — | ~1k | Automated safety check: Pass | MIT | |
| Core Web Vitalstheopenco/llmgateway | 1.7k | — | ~955 | Automated safety check: Pass | Custom licence | |
| First Contentful Paintthedaviddias/Front-End-Checklist | 74k | — | ~427 | Automated safety check: Pass | MIT | |
| Largest Contentful Paintthedaviddias/Front-End-Checklist | 74k | — | ~441 | Automated safety check: Pass | MIT | |
| Performance ProfilerEliasOulkadi/shokunin | 114 | — | ~2.7k | Automated safety check: Notes | MIT | |
| Core Web Vitalskostja94/marketing-skills | 1k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
First Contentful Paint
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Optimize first contentful paint.
Largest Contentful Paint
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Optimize largest contentful paint.
Performance Profiler
EliasOulkadi/shokunin
Performance profiling and optimization for web apps — Core Web Vitals (LCP, INP, CLS), Lighthouse audits, bundle analysis, backend profiling (CPU, memory, DB queries), N+1 detection, caching…
Core Web Vitals
kostja94/marketing-skills
When the user wants to optimize Core Web Vitals, fix LCP, INP, or CLS issues.
Fetchpriority Attribute
thedaviddias/Front-End-Checklist
A skill your agent uses when optimising Largest Contentful Paint (LCP), reducing render-blocking resource contention, or fine-tuning resource loading order in the critical rendering path.
More from asgard-ai-platform/skills
All 207 skills in this repoAlgo Ecom Bm25
asgard-ai-platform/skills
Implement BM25 ranking function for e-commerce product search relevance scoring.
Algo Mfg Cpk
asgard-ai-platform/skills
Calculate Cpk process capability index to assess whether a process meets specification requirements.
Algo Price Elasticity
asgard-ai-platform/skills
Calculate price elasticity of demand to quantify how price changes affect sales volume.
Algo Rank Bayesian
asgard-ai-platform/skills
Apply Bayesian averaging to rank items by combining observed ratings with prior expectations.
Algo Rank Elo
asgard-ai-platform/skills
Implement Elo rating system to rank items or players from pairwise comparison outcomes.
Algo Rank Wilson
asgard-ai-platform/skills
Calculate Wilson Score confidence intervals for ranking items by positive proportion with sample size correction.
Related
Works with
Categories
Questions about Algo SEO Technical
What does Algo SEO Technical do?
Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience. Algo SEO Technical is an agent skill from asgard-ai-platform/skills. Optimize Core Web Vitals (LCP, INP, CLS) for better search rankings and user experience.
When should I use Algo SEO Technical?
Algo SEO Technical fits situations like: the user needs to diagnose page speed issues; improve Largest Contentful Paint; reduce layout shift; pass Googles page experience signals — even if they say my site is slow.
How do I install Algo SEO Technical in Claude Code?
Run `npx skills add asgard-ai-platform/skills --skill algo-seo-technical -a claude-code`. Or copy the skill folder (algo-seo-technical in asgard-ai-platform/skills) into .claude/skills/algo-seo-technical in your project. Claude Code loads it when a task matches its description.
How do I install Algo SEO Technical in Codex?
Run `npx skills add asgard-ai-platform/skills --skill algo-seo-technical -a codex`. Or copy the skill folder (algo-seo-technical in asgard-ai-platform/skills) into .agents/skills/algo-seo-technical in your project. Codex loads it when a task matches its description.
Can I use Algo SEO Technical 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 asgard-ai-platform/skills --skill algo-seo-technical -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/algo-seo-technical, .gemini/skills/algo-seo-technical, .github/skills/algo-seo-technical and .opencode/skills/algo-seo-technical in your project.
What does Algo SEO Technical need to run?
SKILL.md names no scripts, command-line tools or credentials: Algo SEO Technical is instructions for the agent only.
Does Algo SEO Technical access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Algo SEO Technical 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 Algo SEO Technical use?
Algo SEO Technical 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 Algo SEO Technical use?
About 1k tokens (SKILL.md is roughly 4.2k 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 6.2k tokens, read only when the agent opens those files.
What are the alternatives to Algo SEO Technical?
Skills that share tags, products or a category with Algo SEO Technical: Core Web Vitals (theopenco/llmgateway, 1.7k stars), First Contentful Paint (thedaviddias/Front-End-Checklist, 74k stars), Largest Contentful Paint (thedaviddias/Front-End-Checklist, 74k stars) and Performance Profiler (EliasOulkadi/shokunin, 114 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Algo SEO Technical?
asgard-ai-platform (a GitHub organization) maintains it in asgard-ai-platform/skills, which has 242 GitHub stars. The repository holds 207 skills in this directory. The repository was last updated on June 6, 2026.
Source: asgard-ai-platform/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.