docs-site

Audit Zensical docs sites for nav, links, assets, and workflow consistency.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ajbarea/techne --skill docs-site-ajbarea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-site
Source: https://github.com/ajbarea/techne/tree/main/plugins/techne/skills/docs-site
Command: npx skills add https://github.com/ajbarea/techne --skill docs-site-ajbarea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Docs sites break in ways that are hard to notice until after deploy—nav ordering drifts from the filesystem, internal links and anchors go stale, assets go missing or become orphaned, and CI/workflow steps quietly rot.

Core Features & Use Cases

  • Nav vs filesystem integrity: ensures zensical.toml navigation matches docs/**/*.md and flags missing-or-unlisted pages.
  • Internal link and anchor validation: verifies markdown links (including #anchors) resolve to actual headings/sections.
  • Build/deploy workflow sanity checks: validates .github/workflows/docs.yml triggers, pinned action versions, permissions, and the expected build command.
  • CSS/JS and asset reference audits: checks extra_css/extra_javascript files exist, selectors/classes are present, and docs/assets/or static files aren’t orphaned.

Quick Start

Run the docs-site audit to verify nav ordering, internal links/anchors, referenced assets, and the docs GitHub Pages workflow are all consistent for deployment.

Frequently Asked Questions about docs-site

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

FAQPage Schema
How do I validate internal markdown links and anchors in my docs site?

This Skill checks that markdown link targets and #anchors resolve to actual headings and page sections within docs/**/*.md files. It greps all internal links to verify they point to valid content, preventing broken navigation and dead references before deployment.

Why does my documentation site navigation drift from the filesystem structure?

Documentation site navigation drifts when zensical.toml nav configuration falls out of sync with the actual docs/**/*.md files. The Skill reconciles the nav ordering against the filesystem, flagging any missing or unlisted pages to maintain structural consistency.

How do I check my GitHub Pages deployment workflow for docs site errors?

To check your GitHub Pages deployment workflow, the Skill validates .github/workflows/docs.yml triggers, pinned action versions, and permissions. It ensures the expected build command and CI steps are correctly configured to render markdown without silent failures.

Does this docs site validator work with zensical.toml and GitHub Actions CI?

Yes, this validator works specifically with repositories using zensical.toml plus GitHub Pages CI to render documentation. It parses the zensical configuration and validates GitHub Actions workflow pins, permissions, and build commands for correct deployment.

What is the best way to audit orphaned CSS and JavaScript assets in a documentation repository?

The best way to audit orphaned assets is to check that files referenced in extra_css and extra_javascript configurations exist, verify selectors and classes are present, and identify any unreferenced static files or docs/assets that are no longer actively used.