auditor-estatico-plus

Audit static landing pages for security, performance, and SEO issues.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/Alpizar28/SkillsAntigravity --skill auditor-estatico-plus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditor-estatico-plus
Source: https://github.com/Alpizar28/SkillsAntigravity/tree/main/skills/auditor-estatico-plus
Command: npx skills add https://github.com/Alpizar28/SkillsAntigravity --skill auditor-estatico-plus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill audits technical SEO, performance, and security for static landing pages or frontend-only sites (HTML, Next.js). It detects risky patterns such as exposed tokens, insufficient accessibility, and heavy scripts.

Core Features & Use Cases

  • Security checks: Detect secrets or API keys in code (e.g., STRIPE_KEY, SUPABASE_KEY); validate forms have basic validation and do not expose sensitive data.
  • Performance optimizations: Flag uncompressed images or missing dimensions; identify render-blocking scripts; recommend lazy loading where appropriate.
  • SEO & Accessibility: Verify presence of title, meta description, and og:image; check heading hierarchy (single H1, sequential order); ensure alt text on images and sufficient color contrast for accessibility.

Quick Start

Audit a static site to identify security, performance, and SEO issues and generate a prioritized report.

Frequently Asked Questions about auditor-estatico-plus

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

FAQPage Schema
How do I audit a static landing page for SEO and performance issues?

To audit a static landing page for SEO and performance, you scan for render-blocking scripts, uncompressed images, and missing meta tags. This identifies technical health issues and delivers a prioritized report for frontend-only sites.

How do I check my Next.js or HTML code for exposed API keys and secrets?

Checking HTML or Next.js code for exposed API keys involves scanning static assets for sensitive patterns like STRIPE_KEY or SUPABASE_KEY. This security audit detects risky token exposures and validates that forms do not leak sensitive data.

What is checked during a frontend accessibility audit for static sites?

A frontend accessibility audit for static sites checks heading hierarchy for a single H1 and sequential order. It also verifies images have alt text and confirms sufficient color contrast to meet accessibility standards.

Can I use this static site audit tool on projects with a backend?

You should not use this static site audit on projects with active backend calls. It is explicitly designed for static hosting, HTML, and Next.js front-end-only projects where backend calls are absent or minimal.

What's the best way to find render-blocking scripts and unoptimized images on a static site?

The best way to find render-blocking scripts and unoptimized images on a static site is running a technical performance audit. It flags missing image dimensions, identifies heavy scripts, and recommends lazy loading where appropriate.