agilab-huggingface-spaces

Automate AGILAB Hugging Face Space deployment and drift checks via hf_space_deploy.sh workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates the maintenance and deployment of the official AGILAB Hugging Face Space.

Core Features & Use Cases

  • Aligns Space configuration with the official contract across repositories (agilab, thales_agilab/huggingface) to prevent drift.
  • Provides deployment workflows using hf_space_deploy.sh for both first-proof and advanced profiles, plus validation steps before cutover.
  • Ensures profile consistency, secret guidance, and runtime cutover validation to minimize downtime during updates.

Quick Start

Follow the Hugging Face Space deployment flow from the apps/docs bundle to publish or update the official AGILAB Space against the public agilab checkout.

Frequently Asked Questions about agilab-huggingface-spaces

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

FAQPage Schema
How do I automate Hugging Face Space deployment and prevent configuration drift?

Automating Hugging Face Space deployment and preventing configuration drift is done by aligning Space configuration across the public agilab checkout and companion bundle using the hf_space_deploy.sh workflow, which enforces profile consistency and drift-detection checks.

What is runtime cutover validation in a Hugging Face Space deployment?

Runtime cutover validation is a pre-deployment check that verifies profile consistency, secret handling, and configuration alignment to minimize downtime and ensure a smooth transition during Hugging Face Space updates.

How do I manage secrets and profile consistency when updating a Hugging Face Space?

Managing secrets and profile consistency during Hugging Face Space updates requires following the deployment workflow from the apps/docs bundle, which provides secret guidance and validates configurations against the official contract before cutover.

Do I need a specific repository setup to maintain an official Hugging Face Space?

Maintaining an official Hugging Face Space requires coordinating across the public agilab checkout and the companion huggingface bundle to align the Space contract during drift-prone updates.

What's the best way to align Space configuration across multiple repositories?

Aligning Space configuration across multiple repositories involves applying deployment workflows that enforce profile consistency and execute drift-detection checks, ensuring both first-proof and advanced profiles match the official contract.

Why does my Hugging Face Space deployment fail during configuration drift?

Hugging Face Space deployment fails during configuration drift when the public checkout and companion bundle fall out of sync, requiring drift-detection checks and profile consistency validation before applying runtime cutover.