Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
OpenClaw+21 moreClaude CodeCursorCodex CLIMuseOpenClaw
Manus
Grok
Grok Bot+18 agentsSiteSupport: SSG Infrastructure & Layout Diagnostics Core
A backend diagnostic core for resolving SSG configuration, theme precedence, and build pipeline failures.
Free
SiteSupport: SSG Infrastructure & Layout Diagnostics Core
Example session with this skill installed
Diagnose a Hugo build where changes to the header partial aren't showing up. The site uses the 'ananke' theme. Config lists theme = 'ananke'. Directory has layouts/partials/header.html.
- Read your context and instructions
- Compiled the sitesupport
The diagnostic core has analyzed the Hugo project structure and identified a theme override conflict preventing layout updates from rendering.
SSG Diagnostic Report
{
"symptom_evaluation": {
"normalized_symptom": "Root-level layout edits ignored — theme-level file takes precedence"
},
"root_cause_analysis": {
"identified_vulnerability_type": "THEME_OVERRIDE_PRECEDENCE",
"target_file_blockade": "themes/ananke/layouts/partials/header.html"
},
"remediation_protocol": {
"execution_steps": [
"Verify that layouts/partials/header.html exists in the root directory.",
"Ensure the filename matches the theme partial exactly (case-sensitive).",
"Run 'hugo --gc --minify' to clear the internal build cache and force a re-evaluation of the layout lookup order.",
"Check the 'public/' folder to see if the generated HTML contains the root-level changes."
],
"verification_methodology": "Inspect the local build output using a text crawler or manual source check before deploying to the CDN to isolate build issues from propagation delays."
}
}
Next steps
- Copy the theme's default partial to the root layouts folder if creating a new override.
- Trigger a clean build using the
--gcflag to prune stale assets. - Validate the lookup order in the Hugo documentation if using multiple themes.
Connects securely to your tools. The creator never sees your data.
About this skill
Build and configuration failures in Static Site Generators (SSGs) often lead to stalled deployments and high support ticket volumes. Identifying whether a layout bug stems from a theme override conflict, a config syntax error, or an asset pipeline break usually requires manual inspection of directory trees and engine-specific precedence rules.
This skill provides a production-grade diagnostic core for SSG infrastructures. It acts as an autonomous middleware for hosting control panels, support automation tools, and CI/CD pipelines.
What it does
- Normalizes symptoms by mapping raw user observations to canonical diagnostic categories.
- Audits file precedence to detect silent layout blockades where theme files override root changes.
- Identifies root causes across theme hierarchies, asset pipelines, and configuration syntax.
- Generates remediation protocols including specific file paths, code adjustments, and CLI commands.
- Enforces data integrity by refusing to speculate and requesting missing config files when state is insufficient.
How it works
- The host system sends a JSON payload containing the SSG engine, user-observed behavior, and current directory tree snippet.
- The core evaluates the directory structure against the specific engine's inheritance rules (Hugo, Jekyll, Hexo, or Eleventy).
- The system identifies the specific vulnerability type, such as
THEME_OVERRIDE_PRECEDENCE. - It emits a machine-readable JSON report containing a normalized symptom, the root cause, and a multi-step remediation protocol.
Frameworks & tools
Designed for integration with Hugo, Jekyll, Hexo, and Eleventy. Supports backend implementation via Python (FastAPI/Pydantic) or Node.js for deployment into hosting control panels and ticket automation systems.
Why this beats prompting it yourself
Generic prompts often hallucinate causes for complex SSG build orders or ignore engine-specific file precedence rules. This skill follows a strict API contract and a non-speculative logic gate, ensuring you get machine-readable remediation steps instead of conversational guesses.
Use cases
- Automating technical support tickets for static site hosting providers.
- Building self-service diagnostic tools for low-code SSG deployment platforms.
- Implementing automated build-failure analysis in CI/CD pipelines.
- Resolving complex theme inheritance conflicts in large multi-team Hugo projects.
Known limitations
Does not support dynamic frameworks like Next.js, Nuxt, or SvelteKit. Requires read access to the project directory structure and configuration files to function.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean today
- Free to download with an account
Needs access to
Json Schema
Github