Team clients and editors#
One set of workflow skills and executables is shared. Discovery paths and MCP configuration belong to each agent, even when several agents run in one editor. These adapters are based on publisher documentation checked on 2026-10-19.
Recommended setup: Skills CLI or full installer#
For standard Vercel Skills CLI skill management, run npx skills add randrescastaneda/clickup-skills -g, then configure the runtime/MCP for the actual agent using npx --yes github:randrescastaneda/clickup-skills setup --client kilo --skip-skills (replace kilo with the client). --skip-skills deliberately leaves the CLI-managed skill copies alone. The Skills CLI does not provision Python, Krodak's CLI, GitHub CLI, or MCP settings. Ask the installed clickup-setup skill to guide the remaining work. Update skills through npx skills check and npx skills update -g (or project-scoped -p), and runtime through npx --yes github:randrescastaneda/clickup-skills update --client kilo --skip-skills. Do not mix managers for the same skill destination.
Alternatively, the following custom command performs a complete install, managing its own skill copies.
Each teammate runs one command for their client, from any directory:
npx --yes github:randrescastaneda/clickup-skills setup --client kilo
Supported automatic targets are kilo, codex, claude, and copilot for
personal settings, plus vscode with --project-dir /absolute/project.
The installer handles the Python environment, Krodak's latest CLI, six skills,
and a safe configuration merge. Python 3.11+, Node 22+, and Git remain prerequisites.
GitHub CLI must also be installed and personally authenticated for local workflows.
Use update --client CLIENT with the same scope to refresh the managed install.
| Client | Personal configuration managed by setup |
|---|---|
| Kilo | ~/.config/kilo/kilo.jsonc (respects XDG_CONFIG_HOME) |
| Codex | ~/.codex/config.toml (respects CODEX_HOME) |
| Claude Code | ~/.claude.json, preserving all other settings |
| Copilot | ~/.copilot/mcp-config.json |
Project setup uses the destinations below (Codex: .codex/config.toml);
project Codex config may require trusting the project in Codex. Existing project
kilo.jsonc takes precedence over creating .kilo/kilo.jsonc.
Settings updates retain a private sibling backup. Managed server receipts prevent
overwriting locally changed commands. Existing GitHub servers are reused, including
an equivalent remote URL under another name. JSONC comments and unrelated TOML are
retained. Ambiguous settings stop setup. Existing default cu-work mcp entries
from our renderer can be migrated; custom commands require deliberate resolution.
Runtime files live under ~/.local/share/clickup-skills/ by default
(CLICKUP_SKILLS_HOME overrides this). Each update creates a new runtime; older
runtimes are retained so other clients and running sessions keep their paths.
No global npm install, administrator privileges, shell profile edits, or environment
activation are needed. Installed MCP commands never depend on the npx cache.
Use npx --yes github:randrescastaneda/clickup-skills cup init and then cup auth
through the same prefix for personal ClickUp authentication. Use gh auth login
for GitHub. The installer never reads or stores tokens. A machine-local setup is
not shared by committing a project binding, nor does it enable native integration.
The older scripts below remain useful for custom settings, OpenCode, Posit Assistant, and the REST profile. They print configuration rather than merging it.
Configuration matrix#
Run python3 scripts/configure.py --client CLIENT --profile official to print
configuration. Merge the named servers into existing settings; do not replace
unrelated settings. Use default, context, or rest for another profile.
| Client | Renderer | MCP destination | Project skill directory |
|---|---|---|---|
| Codex CLI / Codex extension | codex |
Codex config.toml, [mcp_servers.*] |
.agents/skills/ |
| Claude Code | claude |
Project .mcp.json, or use this repo's marketplace plugin |
.claude/skills/ |
| VS Code MCP configuration | vscode |
.vscode/mcp.json, top-level servers |
.github/skills/ for Copilot |
| Copilot CLI / VS Code Copilot harness | copilot |
~/.copilot/mcp-config.json, or supported project .mcp.json |
.github/skills/ |
| Current Kilo Code | kilo |
.kilo/kilo.jsonc or existing kilo.jsonc, top-level mcp |
.kilo/skills/ |
| Posit Assistant in Positron | posit |
.posit/assistant/settings.json, top-level mcpServers |
Consult the installed Assistant's skill configuration |
VS Code MCP and Copilot CLI MCP are different formats. Current Copilot harness
sessions have their own discovery; a file under .vscode/ alone is not a
portable Copilot CLI setup. Use the renderer for the session actually running.
If GitHub MCP is already provided by your agent, omit the duplicate github
entry while merging the configuration.
Older Kilo releases can use legacy .kilocode/ locations and a different MCP
shape. The kilo renderer targets the current documented mcp / command-array
format. If an installed extension still uses legacy settings, use its MCP UI to
enter the same executable/arguments or remote URLs; verify that version's skill
path before installation. Do not paste the current format into a legacy file.
Install the shared skills#
For personal skills, run the installer from this checkout with the agent name:
python3 scripts/install_skills.py --client copilot
python3 scripts/install_skills.py --client kilo
python3 scripts/install_skills.py --client claude
python3 scripts/install_skills.py --client codex
Each teammate installs only the clients they use. To install in a project:
python3 scripts/install_skills.py --client copilot --scope project --project-dir /absolute/project
The default is a standalone copy, so it works without symlink privileges on
Windows. Copies include our MIT license. After updating the checkout, rerun
with --update to refresh managed copies that have not been locally modified.
Conflicts are checked before any skill is installed. --method link is an
optional alternative for local development. Avoid installing duplicate copies
of the same skills through both a marketplace plugin and personal directories.
VS Code and Positron#
Use the adapter for the agent you run, not merely the editor's name. Codex and Claude Code can run in a terminal inside either editor. Kilo's own configuration belongs to Kilo, and the Posit Assistant configuration belongs to Posit Assistant. Positron's available extensions and Assistant capabilities can differ from VS Code; confirm the installed extension rather than assuming feature parity.
Every local stdio process still needs cu-work on its executable PATH, plus
cup or the configured REST MCP runtime for helper task operations. Installing
an editor plugin does not install those executables or authenticate ClickUp.
Remote official MCP uses each person's OAuth sign-in. Project config stores
environment-variable references; renderers never substitute secret values.
Verification status#
Offline tests validate all seven rendering targets across four profiles, the environment-reference syntax, skill paths, repeated installation, collision handling, and updates that preserve local changes. Linux/macOS/Windows CI runs these checks. An actual installed agent must still discover the six skills, list/call its MCP tools, and complete the live task/PR pilot. Configuration contract tests are not a claim that every editor/extension version was opened.