agilab-docs

Synchronize AGILAB canonical docs sources with public mirrors and validate changes.

19|2|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/ThalesGroup/agilab --skill agilab-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agilab-docs
Source: https://github.com/ThalesGroup/agilab/tree/main/.claude/skills/agilab-docs
Command: npx skills add https://github.com/ThalesGroup/agilab --skill agilab-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation governance and build hygiene for AGILAB, ensuring canonical sources and public mirrors stay in sync and consistent with published pages.

Core Features & Use Cases

  • Synchronize canonical docs source with the public mirror and maintain the mirror stamp.
  • Validate changes end-to-end across canonical sources, mirror, and generated docs to prevent publication drift.
  • Provide a guided workflow for editing docs, syncing mirrors, and regenerating public pages while preserving source truth.

Quick Start

Edit the canonical source under ../thales_agilab/docs/source and refresh the public mirror using the provided sync_docs_source script.

Frequently Asked Questions about agilab-docs

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

FAQPage Schema
How do I sync documentation from a canonical source to a public mirror?▼

To sync documentation from a canonical source to a public mirror, edit the canonical files and run the sync_docs_source script. This action refreshes the public mirror while applying the required stamp to maintain consistency.

What is documentation governance and why is mirror validation needed?▼

Documentation governance orchestrates canonical sources and public mirrors to keep published pages consistent. Mirror validation is needed to prevent publication drift by checking changes end-to-end across canonical, mirror, and generated docs.

How do I validate documentation changes across local and public mirrors?▼

Validate documentation changes across mirrors by applying the guided workflow to check end-to-end consistency. This process prevents publication drift by verifying edits across canonical sources, the public mirror, and generated output.

Can I edit generated documentation files directly in the public mirror?▼

You cannot edit generated documentation files directly in the public mirror. The workflow enforces non-editable generated output, requiring you to edit the canonical source and regenerate pages to preserve source truth.

What is the best way to prevent publication drift when publishing docs?▼

The best way to prevent publication drift when publishing docs is to validate changes end-to-end across canonical sources and mirrors. This ensures the generated output remains consistent with the documented procedures and source truth.