Overview
The Core Web Vitals Diagnostic Assistant is used to answer “Is page speed dragging down conversion?”, performance diagnosis, website quality, and experience metrics. It is suitable for technical, product, marketing, and software users to call after clarifying business goals, content materials, or analysis targets. It combines inputs such as page URLs, reports or problem descriptions, pasted page URLs, performance report summaries, Core Web Vitals metrics… to organize key context and output problem attribution, service improvement suggestions, SOPs, or FAQ checklists, making it easy to continue execution, review, or delivery. Capability positioning supplement: the skills.sh hot signal shows that core-web-vitals has user demand; the platform displays it as a local_service_ops business assistant directory, outputting reviewable diagnostics, suggestions, or production readiness packages.
When to Use
Applicable Scenarios
- Users ask questions such as “Is page speed dragging down conversion?” and need to quickly break down goals, determine priorities, and form actionable results
- Technical, product, marketing, and software users need to generate problem attribution, service improvement suggestions, SOPs, or FAQ checklists around the Core Web Vitals Diagnostic Assistant
- Users have already prepared diagnostic goals (specify the performance, usability, search, conversion, or launch inspection goals to be located.), affected targets (specify the affected users, devices, page types, regions, or business scenarios.), and page links to be diagnosed (fill in publicly accessible pages, sites, reports, or reference links to be diagnosed.), and want to organize them into actionable analysis or optimization results
- Users need to turn Core Web Vitals Diagnostic Assistant-related materials into clear conclusions, priorities, and next-step actions
How to Call
Call the AI Skills API directly through the exported Python runner:
Command Examples
Basic Call
python3 scripts/run.py --params '{}'
Call with Common Parameters
python3 scripts/run.py --params '{"goal":"诊断目标"}'
Parameter Description
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
goal |
string | No | - | Specify the performance, usability, search, conversion, or launch inspection goals to be located |
audience |
string | No | - | Specify the affected users, devices, page types, regions, or business scenarios |
materialUrl |
string | No | - | Fill in publicly accessible pages, sites, reports, or reference links to be diagnosed; a complete accessible URL must be provided |
materialFile |
string | No | - | Upload Lighthouse reports, performance screenshots, metric tables, page descriptions, or technical troubleshooting materials |
materialText |
string | No | - | Paste page URLs, performance report summaries, Core Web Vitals metrics, reproduction scenarios, or website quality issues |
brandRequirements |
string | No | - | Supplement device network, browser, time range, tech stack limitations, unchangeable items, or retest requirements |
See the complete machine-readable parameter structure at references/form-schema.json。
Parameter Value Reference
This skill currently has no categorical parameters that require an additional lookup table.
Supported Input Formats
The current skill directly accepts JSON parameters; if the parameters include a link field, please pass a complete, accessible URL.
Example request
The example parameters below can be passed directly to scripts/run.py, and the runner will send them to the AI Skills API.
python3 scripts/run.py --params '{"goal":"诊断目标"}'
Equivalent --params JSON:
{
"goal": "诊断目标"
}
Example return result
{
"success": true,
"data": {
"message": "示例结果请以技能真实返回结构为准。"
},
"meta": {
"executionTime": 842,
"cached": false
}
}
Deliverables
- Problem attribution, service improvement suggestions, SOP or FAQ checklist: organize core results around the user's goals that can be directly read, reviewed, or delivered.
- Interpretation of input materials: combine the diagnostic goal (state the performance, availability, search, conversion, or launch check goal to be identified.), affected targets (state the affected users, devices, page types, regions, or business scenarios.), and page link to be diagnosed (fill in a publicly accessible page, site, report, or reference link to be diagnosed.) to extract key context and judgment basis.
- Next steps: provide priorities, execution suggestions, or a content framework that can be further processed.
Suggestions for using the results
- First determine whether the output answers the user's core question about the "Core Web Vitals Diagnostic Assistant".
- Then check whether the result covers problem attribution, service improvement suggestions, SOP or FAQ checklist, and whether it provides clear next steps.
- If there is little input material, it is recommended to have the user supplement the goals, audience, constraints, or original materials before running.
Preparation before running
AISKILLS_BASE_URL: defaulthttps://ai-skills.aiAISKILLS_API_KEY: required, used for authenticated callsAISKILLS_TENANT_ID: defaultdefault