valhalla

Audits a codebase for SEO issues and applies fixes on a git branch.

4|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/justin06lee/justin06lee.dev --skill valhalla-justin06lee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: valhalla
Source: https://github.com/justin06lee/justin06lee.dev/tree/main/.gemini/skills/valhalla
Command: npx skills add https://github.com/justin06lee/justin06lee.dev --skill valhalla-justin06lee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, matplotlib, weasyprint, trafilatura, htmldate, and includes scripts (resource) and references (resource) components.

What problem does it solve? Manually auditing a codebase for SEO issues requires choosing among dozens of disciplines (technical SEO, schema markup, sitemaps, hreflang, Core Web Vitals) and then editing source files one finding at a time. Valhalla removes that decision and execution burden by perceiving the project, deciding which SEO disciplines apply, and applying every relevant fix directly to the source in a single run. ## Core Features & Use Cases - Autonomous full-project SEO pass: Runs a six-phase pipeline (perceive, decide, analyze, plan, apply, report) that ends with one reviewable diff on a feat/seo-pass branch, never the default branch. - Deterministic stack detection: Uses a stdlib-only scanner (seo_inventory.py) to identify the framework, routes, existing SEO surface, and business type before any edits. - 26 bundled discipline skills: Drives internal knowledge for technical SEO, content quality, schema.org, sitemaps, images, GEO/AI search, local, e-commerce, hreflang, SXO, clustering, and drift monitoring, loading each only when relevant. - Safety guardrails: Never fabricates facts (addresses, reviews, authorship), never touches secrets or build output, avoids deprecated schema types like HowTo, and uses INP rather than the retired FID metric. - Use Case: Point it at a Next.js marketing site and it detects missing metadata, generates appropriate JSON-LD, fixes sitemap and heading issues, and hands back a single branch diff to merge or revert. ## Quick Start Ask the assistant to run /valhalla on the current project to audit the codebase and fix all applicable SEO issues on a new branch.

Frequently Asked Questions about valhalla

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

FAQPage Schema
How do I run a full SEO audit on my codebase automatically?

Invoke /valhalla with an optional project path. It scans the codebase with a deterministic inventory script, decides which SEO disciplines apply, fans out specialist analysis in parallel, and applies fixes on a feat/seo-pass branch for you to review as one diff.

What SEO areas does an autonomous codebase audit cover?

The pass covers technical SEO, content quality and E-E-A-T, schema.org markup, XML sitemaps, image optimization, AI search (GEO), local SEO, e-commerce SEO, hreflang and international SEO, SXO, semantic clustering, and drift monitoring, applying only what fits the detected project type.

Does it work with Next.js, Astro, or other frameworks?

Yes. Stack adapter references describe where SEO lives in Next app and pages router, Astro, Nuxt, SvelteKit, Hugo, and static HTML, so edits land idiomatically for the detected framework rather than using generic templates.

Will automated SEO edits break my site or touch secrets?

All changes are applied on a separate feat/seo-pass branch, never the default branch, so the diff is the safety net. The skill never touches .env files, secrets, or build output, and never fabricates facts like addresses, reviews, or authorship.

What happens if Python setup or network access is unavailable?

The run still proceeds. The inventory scanner is stdlib-only and the core flow is reading and editing source, so only the heavier scripts requiring the optional Python runtime and Chromium are skipped and noted in the final report.

When should I use individual /seo commands instead of the autopilot?

Use the individual discipline commands when you want a targeted task such as a single-page analysis, schema validation, or drift comparison against a live URL. The autopilot is for end-to-end codebase passes where you want everything applicable handled in one sweep.