What problem does it solve?
Power Pages sites omit security headers entirely unless they are explicitly configured as site settings, leaving sites exposed to clickjacking, cross-origin abuse, and misconfigured Content Security Policies that either break the site or provide no protection.
Core Features & Use Cases
- Header inspection and gap analysis: Reads all
HTTP/* site-setting YAML files in .powerpages-site/site-settings/, compares them against a recognized header catalogue, and identifies missing or misconfigured headers.
- CSP composition and validation: Builds Content Security Policies from a starter template with the correct cloud-specific Power Pages runtime host, a per-request nonce, and external URLs discovered by scanning the project's source files.
- Guided remediation: Presents each finding in plain language with accept, customize, or skip options, then applies changes by editing existing YAML files or creating new site settings, and offers deployment afterward.
- Use Case: A developer asks "fix my CSP" after scripts are blocked on their Power Pages site; the skill inspects the current policy, adds the missing runtime host and project-specific external sources, and recommends report-only mode before enforcing.
Quick Start
Ask the assistant to review the security headers on my Power Pages site and fix any gaps it finds.