Please make this a reusable skill, the new standard

[raiden076]

Problem Statement

The limited availability

Proposed Solution

If you turn this into a reusable skill,
The new standard adopted by claude and codex this can be more widely used

Alternatives Considered

No response

Scope

Bridge only (this repository)

Checklist

• I have searched existing issues to ensure this is not a duplicate.

[bardusco]

Thanks for the suggestion! We investigated this and found some relevant constraints.

Analysis

Skills are designed to be self-contained - all content must live inside the skill directory structure. This works great for "pure knowledge" skills, but Conductor has characteristics that make this approach problematic:

1. Asset files that need to be copied to projects (styleguides, workflow templates)
2. Upstream sync requirements - the bridge exists specifically to avoid forking/modifying the original Conductor
3. Version tracking - knowing which Conductor version is in use

If we created a skill in this bridge, we would:

• Duplicate content from upstream (violating the bridge's core principle)
• Create another maintenance point that could drift from upstream
• Lose version traceability

Recommendation

This suggestion makes sense, but it should be directed to the upstream Conductor project rather than this bridge.

The original project (gemini-cli-extensions/conductor) would be the right place to:

1. Publish an official conductor skill
2. Maintain assets within the skill structure
3. Version it as a distributable package

This bridge would continue to exist for OpenCode users who prefer explicit commands (/conductor.setup, /conductor.implement, etc.) or need to customize the integration.

---

That said, we might be missing something. Are you seeing a way to solve this that we haven't considered? If you have ideas on how to make Conductor work as a skill while keeping it synced with upstream (without duplication), we'd love to hear them!

[raiden076]

Why do you not want to fork? What is the philosophy?

[raiden076]

Just make it work with Claude Code, that's all I need actually 🥲

[bardusco]

Good news! We've submitted a PR to the upstream Conductor project that adds skill support: gemini-cli-extensions/conductor#25

What we built

The skill works with both OpenCode and Claude CLI (Claude Code). It uses a symlink-based approach that:

1. Zero duplication - SKILL.md references the original .toml protocol files directly
2. Auto-updates - Running git pull updates the skill automatically
3. Works today - You can test it from the fork while the PR is pending

Try it now (from the fork)

git clone https://github.com/bardusco/conductor.git
cd conductor
git checkout feature/skill-support
./skill/scripts/install.sh
# Choose option 2 for Claude CLI

Restart Claude Code and you're ready to go!

Why we don't fork

The bridge philosophy is to stay in sync with upstream automatically. Forking would mean:

• Manual maintenance to track upstream changes
• Risk of drift between versions
• Duplication of effort

By contributing directly to upstream, everyone benefits - Gemini CLI, Claude CLI, OpenCode, and Codex users.

---

We'll close this issue once the upstream PR is merged. In the meantime, feel free to test from the fork and let us know if you hit any issues!