create-provider

To scaffold an AtlasClaw provider, this tool generates the provider root with PROVIDER.md, README.md, and a skills/ directory, plus optional scripts, references, and assets folders. It supplies templates and a guided workflow to ensure the package meets repository skill unit standards for production deployment.

Building a new AtlasClaw provider requires PROVIDER.md and SKILL.md templates for consistent discovery and activation context, along with a README.md. The scaffolding process supplies these starter files and example layouts to define a repeatable structure for the provider package.

Yes, the provider scaffolding workflow acts as a ready-to-follow blueprint for onboarding new developers. It provides a phased, guided process for building new providers and their skills, accelerating provider production while ensuring consistent metadata and documentation across the team.

The best way to ensure your provider meets skill unit standards is using a structured scaffolding process that defines PROVIDER.md, README, and SKILL.md with consistent templates. This guarantees the resulting package supports production deployment and repository compliance.

Yes, the AtlasClaw provider scaffolding process supports optional scripts, references, and assets directories alongside the required provider root and skills folder. These starter files and example layouts are included to provide a complete package structure for production deployment.