skills.rest
doodledood
doodledoodCOMMUNITY
Explore all skills by this author →
GitHub

sync-plugins

Synchronize Claude Code plugins from source repositories into OpenCode format.

1|Updated Jan 21, 2026
Search Tags:#automation#workflow#plugins#sync#conversion#repositories#OpenCode
One-click install
npx skills add https://github.com/doodledood/opencode-plugins --skill sync-plugins
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-plugins
Source: https://github.com/doodledood/opencode-plugins/tree/main/.claude/skills/sync-from-claude-plugins
Command: npx skills add https://github.com/doodledood/opencode-plugins --skill sync-plugins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync-plugins helps teams automatically translate Claude Code plugin definitions from source repositories into the OpenCode format, ensuring consistency and up-to-date plugin references across deployments.

Core Features & Use Cases

  • Centralizes and automates the conversion of plugins from multiple source repos into the OpenCode structure.
  • Supports incremental syncing via SYNC.md to minimize work and reduce rework.
  • Reads and applies conversion guidelines from references/CONVERSION_GUIDE.md, NOTES.md, and REPOS.md for a single source of truth.

Quick Start

Run /sync-plugins --all to sync all configured plugins from all repos, or specify repo:plugin pairs to target specific plugins.

Frequently Asked Questions about sync-plugins

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

FAQPage Schema
How do I sync Claude Code plugins into the OpenCode format?▼

Sync Claude Code plugins into OpenCode format by running /sync-plugins --all to convert all configured source repositories, or specify repo:plugin pairs to target individual plugins for conversion.

What does converting Claude Code plugins to OpenCode actually change?▼

Plugin conversion into OpenCode enforces model updates, removes user-invocable fields, and applies skill-to-command mappings before writing changes back to the repository's plugin directories.

Can I incrementally sync plugins from specific source repositories?▼

Incremental plugin sync from specific source repositories uses the SYNC.md file to minimize rework, while the --repo flag filters the synchronization scope to targeted repositories.

What configuration files are needed to automate plugin conversion across repositories?▼

Automating plugin conversion requires references/REPOS.md for source repository listings, references/CONVERSION_GUIDE.md and NOTES.md for conversion guidelines, and SYNC.md for tracking incremental sync states.

What is the difference between --all and --full flags when syncing plugins?▼

The --all flag syncs all configured plugins from every source repository, while --full forces a complete re-sync bypassing the incremental tracking in SYNC.md to ensure all conversions are fully reapplied.

Why are user-invocable fields removed during OpenCode plugin conversion?▼

User-invocable fields are removed during OpenCode plugin conversion because OpenCode maps skills directly to commands, making explicit user invocation fields redundant and ensuring format consistency.

Related Skills

Explore More Software Engineering Skills→
EmasoftEmasoft
4

plugin-validation-skill

Validate Claude Code plugin manifests, hooks, skills, MCP servers, and marketplace entries.

Community
Advanced
AveerAveer
1

zeus-omo

Configure oh-my-opencode-slim plugin provider mappings, codebase maps, and tmux sessions.

Community
Intermediate
JylhisJylhis
1

import-skills

Import external Claude Code skills from a GitHub repository into the marketplace.

Community
Advanced
TrommlTromml
8

kimchi:convert

Convert Claude Code plugins into OpenCode and Codex formats.

Official
Intermediate