What problem does it solve? Managing externally sourced skills alongside repository-managed ones risks accidental overwrites and inconsistent installs. This Skill provides the workflow body for the third-party-sync command, reading the skills.yaml declaration file, validating it, pre-checking for unmanaged placement conflicts, and delegating the actual fetch to a dedicated Custom Tool so third-party skills are installed safely and reproducibly. ## Core Features & Use Cases - Declaration validation: Parses skills.yaml and enforces schema rules such as kebab-case names, required source URLs, and rejection of reserved prefixes (agentdev-, repo-) and disallowed fields. - Conflict pre-detection: Before fetching, detects collisions with unmanaged existing placements under .opencode/skills/ and stops instead of overwriting them. - Delegated fetch with dry-run: Delegates acquisition to the third-party skill fetch Custom Tool, supporting dry-run mode that shows the plan (targets, placement paths, source formats) without making changes. - Use Case: A team declares community-built skills in skills.yaml. Running /agentdev/third-party-sync installs or updates all declared skills into .opencode/skills/ while protecting any manually placed skills from being overwritten. ## Quick Start Run the /agentdev/third-party-sync command, optionally naming a single declared skill or adding dry-run, to fetch and place the declared third-party skills.
