pwa-audit

Audit Next.js/PWA projects for compliance, performance, and security issues.

Updated Jun 23, 2026

Search Tags:#performance #security #audit #Next.js #PWA

Ready to run

npx skills add https://github.com/guideops/agentic-shared --skill pwa-audit-guideops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pwa-audit
Source: https://github.com/guideops/agentic-shared/tree/main/skills/pwa-audit
Command: npx skills add https://github.com/guideops/agentic-shared --skill pwa-audit-guideops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the audit of Next.js/PWA projects to ensure compliance, performance, and security, reducing the risk of issues post-deployment.

Core Features & Use Cases

Compliance Check: Validates PWA requirements such as service worker, HTTPS, and offline fallback.
Performance Evaluation: Inspects for client bundle size, image optimization, and SSR guards.
Security Review: Checks for hardcoded API keys, CSP headers, and secure configuration.
Use Case: Deploy your Next.js/PWA project with confidence, knowing it's been thoroughly audited for potential issues.

Quick Start

Run the 'pwa-audit' command to start the audit process on your current directory. Use '--path' to specify a different project directory.

Frequently Asked Questions about pwa-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit a Next.js PWA for compliance and security?▼

To audit a Next.js PWA for compliance and security, run a local script execution that validates PWA criteria including manifest validation, service worker checks, HTTPS enforcement, and offline support. The audit reviews Next.js-specific configurations to reduce post-deployment risks.

What does a PWA compliance check include for service workers and offline support?▼

A PWA compliance check includes validating your manifest, verifying service worker registration, enforcing HTTPS, and confirming offline fallback capabilities. It ensures your application meets critical PWA criteria for reliable offline performance and secure connections.

How can I check my Next.js project for hardcoded API keys and CSP headers?▼

You can check for hardcoded API keys and CSP headers by running a security review script on your Next.js project directory. This local audit scans for secure configuration issues, hardcoded credentials, and validates your Content Security Policy implementation.

Does the PWA audit evaluate client bundle size and image optimization?▼

Yes, the PWA audit evaluates performance by inspecting client bundle size, image optimization, and SSR guards. This performance evaluation helps identify rendering bottlenecks and asset optimization issues within your Next.js application.

Can I run a PWA performance audit on a specific project directory?▼

Yes, you can run a PWA performance audit on a specific project directory by executing the audit command with the '--path' flag. By default, the audit runs on your current working directory if no path is specified.

Do I need a local environment setup to validate PWA requirements?▼

Yes, you need a local environment setup to validate PWA requirements because the audit relies on local script execution. This setup is necessary to accurately inspect your Next.js configurations, service workers, and offline support mechanisms.