sync-droids

This Skill converts Claude Code agent .md definitions into Factory Droid .md files by mapping model IDs and tool names to match Factory Droid requirements. It ensures deployments do not break due to format differences between the two frameworks.

You can deploy Garura skills and plays into Factory directories by running the sync script, which copies the source markdown files while stripping unsupported frontmatter fields. This process cleans target directories and applies deterministic filesystem operations.

Yes, the deployment process synchronizes Garura memory files by copying the framework's memory directory to the configured Factory memory destination. This ensures that memory is available alongside deployed skills and droids in the target environment.

Yes, you can deploy Factory Droids in either project-scoped or global installation modes by using the --project or --global flags. Running the sync script in global mode deploys components into your home Factory directories by default.

The best way to keep Garura agent definitions aligned with Factory Droid requirements is to use a transformation script that cleans targets, copies markdown sources, and maps frontmatter fields. This guarantees deterministic synchronization during environment setup.

Factory Droid deployments break when Garura skills, plays, or agent definitions contain unsupported frontmatter fields or mismatched model identifiers. Applying frontmatter cleanup and model ID mapping before deployment resolves these format inconsistencies.