Import workspaces from local, URL, or GitHub templates with collision handling.
npx skills add https://github.com/Miosa-osa/canopy --skill import-miosa-osa
Please help me install this Agent Skill. Skill: import Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/workspace/import Command: npx skills add https://github.com/Miosa-osa/canopy --skill import-miosa-osa
Importing workspace templates often leads to conflicts, missing secrets, and fragmented provisioning across multi-source sources. This skill centralizes the import lifecycle, ensuring safe preview, collision resolution, and automatic workspace setup.
Run the import command with a local template and follow the prompts to resolve variables and secrets.
High-intent search queries and answers about installing and using this skill.
Safe workspace template import uses configurable collision strategies—rename, skip, replace, or prompt—to resolve file conflicts without overwriting existing files. A dry-run preview flag lets you detect and review collisions before applying any changes to the target directory.
Yes, previewing workspace provisioning changes is possible by running the import command with the dry-run flag. This executes the acquire and preview steps, showing potential file collisions and missing secrets without modifying the target directory or launching the workspace.
Automating workspace provisioning from a GitHub template is best handled by the import command's end-to-end flow: acquire, preview, resolve, provision, and launch. It supports URL-based acquisition and optional secret prompts to enable fully automated provisioning without manual intervention.
Required secrets are managed during workspace template import through optional secret prompts designed for automation. The import process detects missing secrets during the preview phase and can prompt for them interactively or accept predefined inputs to complete the provisioning step.
Yes, workspace template import supports custom target directories through the target flag. This directs the provisioning step to a specific destination path for directories, agents, and budgets, overriding the default location when applying the imported template.
You should use a dry-run preview for workspace template import whenever provisioning from local, URL, or GitHub sources to anticipate file collisions and missing secrets. It is especially recommended before applying templates with the replace collision strategy to prevent data loss.
kenbanks-pengScan job boards, score matches, and store results in SQLite.
Miosa-osaProvision agents, budgets, and configuration from YAML or TOML workspace templates.
jason660519Authenticate with the 1Password CLI and inject secrets into environments.
MantisWareImport workspace templates from local files, URLs, or GitHub repositories with collision handling and secret prompts.
