スキル core-web-vitals
📦
core-web-vitals
v2.0 コンテンツリビジョン r1 安全 🌐 ネットワークアクセス📁 ファイルシステムへのアクセス⚡ スクリプトを含む⚙️ 外部コマンド
Improve Core Web Vitals with Targeted Fixes
Slow loading, delayed interactions, and unexpected layout shifts damage page experience. This skill guides evidence-based diagnosis and targeted fixes for LCP, INP, and CLS.
対応: Claude Codex Code(CC)
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
エージェントリクエスト
Review the Skillstore skill "core-web-vitals" from https://skillstore.io/skills/addyosmani-core-web-vitals.md and its manifest at https://skillstore.io/api/skills/addyosmani-core-web-vitals/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「core-web-vitals」を使用しています。 The supplied trace shows the hero image request starts after stylesheet loading.
期待される結果:
- Finding: Late image discovery contributes to LCP resource load delay.
- Action: Make the hero image discoverable in initial HTML and give it high fetch priority.
- Verification: Repeat the trace under equivalent conditions; add preload only if discovery remains late.
「core-web-vitals」を使用しています。 A banner appears above the article after loading. Only source code is available.
期待される結果:
- Hypothesis: The banner may displace visible article content because its space is not reserved.
- Action: Reserve a stable banner slot or choose placement that does not move visible content.
- Verification: Capture the affected state at representative viewports before claiming a CLS failure or improvement.
「core-web-vitals」を使用しています。 The supplied interaction trace shows a long task before the click handler begins.
期待される結果:
- Finding: Main-thread contention contributes to input delay before event processing.
- Action: Attribute the blocking task and reduce, defer, or split its nonessential work.
- Verification: Repeat the same interaction and confirm that input delay falls without shifting cost to rendering.
セキュリティ監査
安全v1 • 2026/10/22 バージョン別レポートを開く
All 50 static findings are false positives involving Markdown formatting, fixed imports, documentation links, example requests, and performance guidance. No evidence found of credential theft, unauthorized execution, data exfiltration, or prompt injection in the four reviewed files.
4
スキャンされたファイル
690
解析済み行数
0
レビュー項目
0
誤検知を無視
リスク要因
🌐 ネットワークアクセス (8)
📁 ファイルシステムへのアクセス (4)
⚡ スクリプトを含む (2)
⚙️ 外部コマンド (32)
SKILL.md:43 SKILL.md:48-50 SKILL.md:50-53 SKILL.md:53-61 SKILL.md:61-64 SKILL.md:64-71 SKILL.md:71-73 SKILL.md:73 SKILL.md:76-88 SKILL.md:88-94 SKILL.md:94-103 SKILL.md:103-107 SKILL.md:107-109 SKILL.md:109-110 SKILL.md:110-111 SKILL.md:111-112 SKILL.md:112-117 SKILL.md:117 SKILL.md:118 SKILL.md:123-132 SKILL.md:132-138 SKILL.md:138-146 SKILL.md:146-170 SKILL.md:170-174 SKILL.md:174-176 SKILL.md:176-178 SKILL.md:178-185 SKILL.md:185-194 SKILL.md:194-197 SKILL.md:197-206 SKILL.md:206-209 SKILL.md:209-218
最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。
監査者: codex
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/addyosmani-core-web-vitals/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/addyosmani-core-web-vitals?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/addyosmani-core-web-vitals?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-core-web-vitals/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/addyosmani-core-web-vitals.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
addyosmani. (2026). core-web-vitals security audit report (audit version 1) [Author version 2.0]. Skillstore. https://skillstore.io/skills/addyosmani-core-web-vitals/audits/1BibTeX形式の引用
@techreport{addyosmani-addyosmani-core-web-vitals-2026,
author = {addyosmani},
title = {core-web-vitals security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-core-web-vitals/audits/1},
note = {Author version 2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "core-web-vitals security audit report (audit version 1)"
version: "2.0"
type: report
authors:
- name: "addyosmani"
date-released: "2026-10-22"
url: "https://skillstore.io/skills/addyosmani-core-web-vitals/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-core-web-vitals:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中 45
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
91
仕様準拠
作成できるもの
Reduce storefront loading delays
Review a product page trace to identify delayed hero image discovery and prioritize verified LCP fixes.
Investigate slow application interactions
Analyze a sluggish dashboard interaction to distinguish main-thread contention, expensive handlers, and delayed rendering.
Resolve recurring layout shifts
Review a publishing template for unstable embeds, inserted banners, and font changes using trace evidence and responsive verification.
これらのプロンプトを試す
Understand the metrics
Explain LCP, INP, and CLS for my page. List their good thresholds and the evidence needed before diagnosing a failure.
Review source for likely causes
Review the supplied page code for likely LCP and CLS risks. Separate hypotheses from measured findings and suggest focused verification steps.
Diagnose a measured interaction
Analyze the supplied interaction trace and field INP data. Identify the dominant delay phase, implicated work, targeted fixes, and an equivalent retest.
Plan production verification
Use the supplied CrUX p75 data, traces, and release context to prioritize metric-specific fixes. Define equivalent lab retests and segmented RUM verification.
ベストプラクティス
- Use field evidence to prioritize user impact and browser traces to diagnose the relevant metric.
- Compare measurements under equivalent device, network, page state, and interaction conditions.
- Validate focused code changes in the lab, then wait for new field visits before claiming production improvement.
回避
- Treating a single browser observation as equivalent to a field p75 measurement.
- Adding image preloads, memoization, or font overrides without evidence that they address the measured cause.
- Applying broad prerendering rules without excluding sensitive routes or accounting for early side effects and resource costs.
よくある質問
Which metrics does this skill cover?
It covers Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift.
Can it review source code without a running page?
Yes. It can identify likely causes, but runtime evidence is required to establish failing metrics or measured improvements.
Which tools can use this skill?
The skill supports Claude, Codex, and Claude Code. Browser measurement capabilities depend on the tools available in your environment.
Does it include an automated performance scanner?
No. It supplies guidance and examples, relying on external browser tools, Lighthouse, PageSpeed Insights, CrUX, or supplied measurements.
Can it confirm field improvements immediately?
No. Equivalent lab tests can verify local changes, but CrUX and first-party RUM need new user visits.
Are all referenced measurement guides included?
No. Detailed LCP, INP, and CLS references are included, but some measurement and RUM links require the sibling performance skill.
開発者情報
作成者
addyosmaniライセンス
MIT
作者バージョン
v2.0
Skillstore リビジョン
r1
バージョンに関する注意
作者が宣言したバージョンは有効な SemVer ではありません。
参照
79fc52323997649cbf5ae9e897690d43e1c131ad
メンテナンスの新しさ
2026/10/22
利用状況
0 ダウンロード · 0 閲覧
ファイル構成