TAAC Docs Pages Pipeline
SkillDocs & knowledgeConfigure or diagnose TAAC Zensical builds, navigation, and GitHub Pages deployment.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the TAAC Docs Pages Pipeline skill
What this skill tells your AI
The instructions your AI receives, as published by puiching-memory/taac_2026 in .agents/skills/taac-docs-pages-pipeline/SKILL.md and read by ahel’s review.
Use the local site guide for build commands,
navigation, and workflow validation. Ordinary prose edits follow that guide's
writing conventions and the strict-build requirement in AGENTS.md.
- For navigation, assets, or page-path issues, inspect the affected page and
zensical.toml; consult the sectionindex.mdwhen its role changes. - For CI or Pages claims, inspect
.github/workflows/deploy-docs.ymland.github/workflows/ci.yml. Trace the relevant event, path filters, job conditions, and checkout ref. PR validation and main deployment differ. - For mixed code/docs changes, account for the CI-completion path before interpreting a skipped direct deployment as a failure.
- Compare the deployed commit and workflow result when diagnosing stale Pages.
Local
site/contents alone do not establish deployment status.
Use the guide's workflow checks for YAML changes; a successful documentation build establishes local rendering, not successful remote deployment.
Signals
- GitHub stars
- 315
- Forks
- 63
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
taac-docs-pages-pipeline- Source
- github.com/puiching-memory/taac_2026