agilab-installer

Automates AGILAB installation, app deployment, debugging across macOS, Linux, Windows with idempotent scripts and run evidence generation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AGILAB Installer Skill provides structured, repeatable guidance and tooling to install AGILAB, install apps/pages, and debug installation and test failures, reducing manual setup time and drift.

Core Features & Use Cases

  • Idempotent root installer workflow across macOS/Linux/Windows with install.sh / install.ps1.
  • Apps/pages installer automation using src/agilab/install_apps.sh / install_apps.ps1 and app install entry.
  • Data seeding, dataset archives, and post-install hooks to ensure ready environments.
  • Debugging and validation aids such as write_tokki_scope and run evidence generation for reproducible handoffs.

Quick Start

Run the root installer with the apps repository and test options to validate a reproducible, idempotent AGILAB deployment.

Frequently Asked Questions about agilab-installer

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

FAQPage Schema
How do I perform an idempotent AGILAB installation across macOS, Linux, and Windows?

An idempotent AGILAB installation is automated via root installer scripts like install.sh and install.ps1, ensuring repeatable deployments across macOS, Linux, and Windows without drift. Running these scripts validates reproducible environments safely.

What is the best way to automate app deployment and data seeding after an AGILAB install?

App deployment and data seeding are automated using install_apps.sh or install_apps.ps1 alongside app install entry points. Post-install hooks then populate dataset archives to ensure your AGILAB environment is fully ready for use.

Does the AGILAB installer provide debugging guidance for failed installation or test workflows?

The AGILAB installer provides debugging guidance and validation aids like write_tokki_scope and run evidence generation. These features capture reproducible evidence to help diagnose and resolve installation or test failures effectively.

Why does my AGILAB post-install environment lack the required datasets and configuration?

Missing post-install datasets indicate skipped data seeding hooks or failed app install entry scripts. The AGILAB installer applies post-install hooks and dataset archives to ensure ready environments and prevent manual setup drift.

Can I validate a reproducible AGILAB deployment before running the full application?

You can validate a reproducible AGILAB deployment by running the root installer with the apps repository and test options. This workflow generates run evidence to confirm idempotent installs and successful app deployment before full execution.

When do I need to use the apps/pages installer scripts instead of the root AGILAB installer?

Use apps/pages installer scripts like install_apps.sh when adding specific AGILAB modules after the initial root setup. The root installer handles core environment setup, while apps/pages scripts manage targeted app installation and post-install data seeding.