Link a Web App Manifest for installability
SkillWeb & browsingweb-app-manifest is an agent skill for checking whether a site links a Web App Manifest correctly so it can be installed as a Progressive Web App. It reviews templates, rendered HTML, and shared components, validating the final browser-facing markup rather than the source framework abstraction.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that supports loading skills, and add the web-app-manifest skill to its available skills.
Then ask your AI: use the Link a Web App Manifest for installability skill
What your AI can do with it
- Check whether an HTML file links a Web App Manifest
- Verify required manifest fields: name, short_name, icons (192px and 512px), start_url
- Flag missing display: standalone and theme_color settings
- Review templates, server-rendered HTML, and shared components for violations
- Create a minimal manifest and link it from the HTML head
- Explain the manifest format and how icons work across platforms
Getting started
- Have an agent that supports loading skills, and add the web-app-manifest skill to its available skills.
- Ask the agent to review a template, rendered HTML file, or shared component for a linked Web App Manifest.
- The agent checks the final markup, verifies required manifest fields, and flags exact elements, attributes, or routes that violate the rule.
- Ask the agent to fix issues by creating a minimal manifest and linking it from the HTML head, or to explain the manifest format.
- Consult references/rule.md for full implementation details and framework-specific guidance.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/web-app-manifest/SKILL.md and read by ahel’s review.
A Web App Manifest is the minimum requirement for a site to be installable as a Progressive Web App. Installed PWAs launch in their own window, appear in app switchers, and can receive push notifications. Even for non-PWA sites, the manifest improves the experience when users bookmark to their home screen and provides metadata for browser share dialogs.
Quick Reference
- Link manifest.json with
- Include name, short_name, icons (192px and 512px minimum), and start_url
- Set display: standalone to hide browser chrome when launched from home screen
- Set theme_color to control the browser address bar and OS taskbar color
Check
Check if this HTML file has a Web App Manifest linked. If so, verify the manifest has all required fields for installability.
Fix
Create a minimal Web App Manifest with the required fields and link it from the HTML head.
Explain
Explain the Web App Manifest format, which fields are required for installability, and how icons work across different platforms.
Code Review
Review templates, server-rendered HTML, and shared components that output markup related to Link a Web App Manifest for installability. 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/en/rules/html/web-app-manifest
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What does the manifest do for a non-PWA site?
- It improves the experience when users bookmark the site to their home screen and provides metadata for browser share dialogs.
- Which manifest fields are required for installability?
- name, short_name, icons (192px and 512px minimum), and start_url. Setting display: standalone and theme_color is also recommended.
Advanced
- Item type
- skill
- Key
web-app-manifest- Source
- github.com/thedaviddias/front-end-checklist