ONNX Opset Bump Checklist
microsoft/onnxruntime
A checklist for upgrading the pinned ONNX version and opset in ONNX Runtime, covering the files to change, archive hashes, patch rebasing and release-candidate handling.
Syncs or audits ccLoad's CLIProxyAPI protocol-conversion core and registered provider adapters against one pinned upstream commit, then verifies the result.
SKILL.md written in Chinese; this summary is our English description.
Install CLIProxy Core Sync
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install caidaoli/ccLoad sync-cliproxy-core --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .claude/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .claude/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-coreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install caidaoli/ccLoad sync-cliproxy-core --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .agents/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .agents/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install caidaoli/ccLoad sync-cliproxy-core --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .cursor/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .cursor/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/caidaoli/ccLoad.git --path .agents/skills/sync-cliproxy-core--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install caidaoli/ccLoad sync-cliproxy-core --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .gemini/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .gemini/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install caidaoli/ccLoad sync-cliproxy-coreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .github/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .github/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install caidaoli/ccLoad sync-cliproxy-core --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/caidaoli/ccLoad.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/sync-cliproxy-core .opencode/skills/sync-cliproxy-core && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sync-cliproxy-core" agent skill from https://github.com/caidaoli/ccLoad/tree/master/.agents/skills/sync-cliproxy-core into .opencode/skills/sync-cliproxy-core/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sync-cliproxy-core", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sync-cliproxy-core- GitHub stars
- 419
- Token cost
- ~1.5k tokens
- SKILL.md length
- 378 words
- Files
- 8 (incl. scripts, references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Syncs or audits ccLoad's CLIProxyAPI protocol-conversion core and registered provider adapters against one pinned upstream commit, then verifies the result.
- Works in 6 steps: 预检 → 固定目标 → 比较范围 → …
- Aligning ccLoad with a new stable CLIProxyAPI release
- SKILL.md covers 原子同步契约, 权威边界, 同步流程 and 完成报告
- Runs Shell and Go scripts from its folder; calls git, bash and make
What it does
Written in Chinese for the ccLoad repository, this skill syncs the four-protocol conversion core of CLIProxyAPI and the registered provider adapters, with their tests, as one atomic operation. By default it pins the latest stable upstream version, compares, integrates, updates the source record and verifies; a commit or tag you name is used instead. An audit-only request stays read-only and compares against the commit recorded in UPSTREAM.md.
Core and adapters must come from the same immutable upstream commit. If any part cannot be ported, lacks tests or fails verification, the whole sync counts as incomplete, with no core-only fallback. The rules keep ccLoad's registry and wire contracts, forbid pulling in the upstream runtime systems or a Go module dependency on CLIProxyAPI, and keep provider choice at the request-context boundary. A preflight protects your local edits, and stable tags are picked by semantic version, ignoring prereleases.
When your agent uses it
- Aligning ccLoad with a new stable CLIProxyAPI release
- Auditing the core and provider adapter snapshots against upstream without changing files
- Syncing to a specific upstream commit or tag
Example prompts
- “Sync the CLIProxy core to the latest stable upstream release.”
- “Audit the provider adapters against the commit recorded in UPSTREAM.md and report the differences.”
- “Sync the core and adapters to this upstream tag and run the verification scripts.”
Requirements
- A ccLoad checkout
- A local or clonable CLIProxyAPI upstream repository
- Go and bash for the verification scripts
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4c9bc04. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Shell and Go), which the agent can run.
Shell commands in SKILL.md call:
gitbashmakego
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CLIProxy Core Sync loads about 1.5k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 25 tokens; SKILL.md has 378 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from caidaoli/ccLoad at commit 4c9bc04, republished under its MIT licence (© caidaoli). 378 words, ~1,486 tokens.
Download SKILL.mdSave it as
.claude/skills/sync-cliproxy-core/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- sync-cliproxy-core
- description
- 同步或审计 ccLoad 的 CLIProxyAPI 核心与已登记 provider adapter 快照。适用于上游版本对齐，不用于普通渠道配置或独立业务修复。
同步 CLIProxy 转换核心与渠道适配器
一次同步 CLIProxyAPI 的四协议纯转换核心、已登记 provider adapters 及其对应测试。保持 ccLoad Registry 和 provider wire 契约，不引入上游运行时系统。
- 默认调用
$sync-cliproxy-core时，自动固定上游最新稳定版本，并在同一次操作中完成 core 与全部已登记 provider adapters 的比较、集成、来源更新和验证；用户明确指定 commit/tag 时使用指定目标。 - 仅审计时保持只读：固定比较目标、核对来源与 manifest、报告差异和验证结果，不进入集成变更或更新来源步骤；未指定比较目标时使用
UPSTREAM.md已记录的 commit。 - 阅读或编辑本技能本身不执行同步。
原子同步契约
- core 与 provider adapters 必须来自同一 checkout 的同一不可变 commit；只生成一份变化清单，只更新一次来源 commit 和同步日期，只运行一套完成验证。
- 任一同步域无法移植、缺少匹配测试或验证失败时，整个同步未完成。不提供隐式 core-only 降级；用户明确缩小范围时只能审计，不得把部分写入报告成完整同步。
权威边界
- 按任务读取 协议转换边界、
internal/protocol/cliproxy/UPSTREAM.md、core snapshot manifest、provider adapter 语义边界和provider manifest。UPSTREAM.md是来源、固定提交和已落地状态的唯一事实源；core manifest 记录直接映射根、特殊映射、明确排除和最近一次 core/provider 原子差异的审查 blob，provider manifest 是 provider、逐文件映射、生产接线和契约测试的唯一 allowlist。 internal/protocol/registry.go定义四协议契约；internal/protocol/builtin/cliproxy_adapter.go处理通用输入验证、JSON/SSE 规范化和流帧封装；internal/protocol/cliproxy/providers/保存 provider-specific 纯转换。- provider 选择留在 ccLoad 请求上下文边界，按实际 wire dialect/AuthType 决定；不要把 provider 注册成第五种通用客户端协议。
- 不引入 CLIProxyAPI 的认证、配置、路由、缓存服务、插件、动态 Registry、executor 或网络刷新代码。Interactions 只有在 ccLoad 正式支持其线协议后才可登记。
- 不添加 CLIProxyAPI 运行时 Go module 依赖或
replace。源码继续使用ccLoad/internal/protocol/cliproxy/...导入路径。 - Registry 与 provider 边界测试是 ccLoad 兼容性权威。上游行为与本地线协议冲突时，修正根因并保留本地契约，不盲目覆盖。
同步流程
1. 预检
- 确认当前目录属于 ccLoad，并检查
git status --short。 - 保护已有修改。若工作区改动覆盖 core、providers、适配器、Registry、
go.mod、go.sum或UPSTREAM.md，先区分用户修改与本次同步；无法安全隔离时停止并说明冲突。 - 记录当前同步 commit 和目标 commit。
2. 固定目标
- 上游 checkout：本机存在
~/Source/go/CLIProxyAPI时优先使用，否则在临时目录克隆UPSTREAM.md记录的仓库。core、provider 生产源码与测试必须全部来自这个 checkout 的同一个 commit。 - 用户指定 commit/tag 时，解析成完整不可变 commit SHA。
- 用户未指定目标或只说“同步最新”时，以当前记录 tag 去掉
MAJOR.MINOR.PATCH后的前缀作为稳定 tag 系列（记录为fork/vX.Y.Z时系列为fork/v），按语义版本选最高版本并解引用为 commit；忽略预发布 tag，禁止按字典序或提交时间猜版本：
repo=<UPSTREAM.md 的 Repository>; series=<tag 系列>; upstream=<上游 checkout>
tag="$(git ls-remote --tags --refs "$repo" "refs/tags/${series}*" | sed 's#.*refs/tags/##' \
| grep -E "^${series}[0-9]+\.[0-9]+\.[0-9]+$" | sort -V | tail -1)"
git -C "$upstream" fetch --no-tags "$repo" "refs/tags/$tag:refs/tags/$tag"
git -C "$upstream" rev-parse "$tag^{commit}"- 记录并同步解引用后的 commit，而不是 annotated tag object；报告目标和变化范围后直接继续，不等待确认。无法确定 tag 系列、找不到稳定 tag 或 tag 无法解析为 commit 时停止并说明原因，禁止退回到浮动分支 HEAD。
- 若目标 SHA 与当前同步 SHA 相同，不改写
UPSTREAM.md的同步日期；运行确定性审计和验证后报告已是最新版本。
3. 比较范围
- 一次生成目标 commit 相对当前记录 commit 的联合差异：四协议 core、allowlist 中每个 provider 的生产源码及对应
_test.go，不要分两次比较。 - 先生成目录级和文件级变化清单，再确认新增文件是纯转换语义。provider 的
init.go、动态 Registry 和 noop/分配实现测试按 allowlist 排除。 - 每个上游 core 变更必须由 core manifest 分类为直接映射、特殊映射、明确删除、明确排除或已登记 provider。新增 core 源根或本地特例时更新 core manifest；上游删除已同步文件时登记
delete行并删除本地映射；新增 provider 时更新 provider manifest、语义边界和UPSTREAM.md。脚本只从 manifest 读取这些清单，不复制第二份。审计失败不能靠跳过检查解决。 - 明确列出排除的上游包。不要因为编译缺失就搬入 runtime；删除副作用依赖，或在同步包内用已有纯
common/signature/util能力替代。 - 上游删除字段注入时，确认行为是否迁移到被排除的 runtime 层；若是，必须在本地转换边界保留，并用 Registry 契约测试验证。
- 复查
UPSTREAM.md已排除项的排除理由是否仍成立：上游重构可能使旧理由失效（该同步的补回来），也可能采纳了本地契约（删掉过期的本地差异注记）。
Show full SKILL.md (152 more words)Show less
4. 集成变更
- 以可审查的小批次应用源码，但把所有批次视为一个原子同步结果。
- 将上游 import 改为本地
ccLoad/internal/protocol/cliproxy/...。 - 将通用传输适配留在
builtin/cliproxy_adapter.go，provider envelope/字段补全留在providers/<provider>；只有通用协议语义需要时才修改 core。 - 确保每个同步的 provider adapter 被生产请求路径实际调用，不能只复制成死代码。
- 对工具调用 ID、reasoning/signature、usage/cache、JSON 字段形状、错误 envelope、SSE framing/终止事件和跨 chunk 状态逐项核对 core 与 provider 契约。
- 无法表示的客户端请求继续返回
RequestTranslationError，由代理映射为 HTTP 400；不得触发渠道切换或冷却。
5. 更新来源记录
- 只有 core 和全部已登记 provider 的生产源码、对应测试、生产接线都完成后，才一次性更新
internal/protocol/cliproxy/UPSTREAM.md的完整 commit、标签说明和同步日期。 - 逐文件审完差异后，用脚本重算 core manifest 的全部 blob 行，不要手算：
bash .agents/skills/sync-cliproxy-core/scripts/verify_core_scope.sh --refresh-manifest \
--upstream-repo <上游 checkout> --base-commit <原同步 commit> --target-commit <目标 commit> 它按 base..target 重建 review 块，刷新 file/local 行 blob，并删除差异范围外的旧 delete/skip-test 行。只要还有未归类的上游文件、未登记的上游删除或缺失的映射文件，就逐条输出 TODO 并拒绝写入。它只负责记账，不代替审查：delete、skip-test、exclude 行及其理由仍需人工填写，写入后检查 git diff。
- 两次同步之间若修改了被 blob 固定的快照文件，用 manifest 中
# Reviewed atomic delta: <base> -> <target>.记录的两个 commit 重跑同一命令。 - 在
UPSTREAM.md分别记录 core 与 provider 的上游源目录、本地目录和实际落地状态；逐文件事实和本次差异审查 blob 只保留在 manifest，二者共享同一个 commit/date。 - 保留
internal/protocol/cliproxy/LICENSE。许可证或上游归属变化必须显式审查。 - 不在 Skill 中复制 commit、日期或测试数量；这些易变事实只写入
UPSTREAM.md。
6. 验证
先运行确定性审计：
bash .agents/skills/sync-cliproxy-core/scripts/verify_core_scope.sh --self-test
bash .agents/skills/sync-cliproxy-core/scripts/verify.sh --tests --require-providers \
--upstream-repo <上游 checkout> \
--base-commit <原同步 commit>--require-providers 是完整同步的完成门禁，必须同时给出 --upstream-repo 和完整的 --base-commit。base 必须等于 Git HEAD 中修改前 UPSTREAM.md 记录的 SHA。脚本据此强制检查 base 到目标之间的每个 core/provider 变更：必须已映射、删除或明确排除，review blob 必须最新，新增的上游测试符号必须已移植或登记为 skip-test，allowlist provider 必须全部落地。base 等于目标时，只做目标树、review blob 和 provider 的确定性审计。日常审计可以省略这些参数，但不得据此报告完整同步成功。
完成同步后运行仓库级检查；只读审计根据实际审计范围选择相关检查：
go test -tags sonic ./internal/...
make build
golangci-lint run ./...
git diff --check只在并发相关代码受影响时运行 make race-fast 或 make race。根据最终差异更新 .claude/agent-guide/ 中受影响的专题及必要的 README.md / README.zh-CN.md、docs/guide/；只有通用约束或入口变化才修改 CLAUDE.md。
完成报告
报告以下事实：
- 原同步 commit、目标 commit 和上游 checkout；
- 同一次同步覆盖的 core、provider 目录/文件与明确排除的上游模块；
- 为维持 ccLoad Registry/provider wire contract 保留或新增的本地差异；
UPSTREAM.md、许可证和相关项目文档是否更新；- 每条验证命令的结果。
© caidaoli, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (scripts, references) in .agents/skills/sync-cliproxy-core of caidaoli/ccLoad.
- SKILL.md
- agents/openai.yaml
- references/core-snapshot.manifest
- references/provider-adapters.manifest
- references/provider-adapters.md
- scripts/list_go_tests.go
- scripts/verify.sh
- scripts/verify_core_scope.sh
Open the folder on GitHubat commit 4c9bc04
Compare with similar skills
CLIProxy Core Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CLIProxy Core Sync this skillcaidaoli/ccLoad | 419 | — | ~1.5k | Automated safety check: Pass | MIT | |
| ONNX Opset Bump Checklistmicrosoft/onnxruntime | 22k | — | ~12k | Automated safety check: Pass | MIT | |
| OBS Plugin Dependency Upgradesorayuki/obs-multi-rtmp | 5.1k | — | ~609 | Automated safety check: Pass | GPL-2.0 | |
| Breaking Change Analysisruby-git/ruby-git | 1.8k | — | ~1.7k | Automated safety check: Pass | MIT | |
| PR Bumpakitaonrails/my-skills | 213 | — | ~2.7k | Automated safety check: Pass | None | |
| Migrate Internal Package into GhostTryGhost/Ghost | 56k | — | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
OBS Plugin Dependency Upgrade
sorayuki/obs-multi-rtmp
Updates the obs-multi-rtmp plugin repo to the latest upstream plugin template and OBS Studio version, including dependency metadata, then rebuilds it with CMake.
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
PR Bump
akitaonrails/my-skills
Merge Dependabot / dependency-bot bump PRs quickly and safely.
Migrate Internal Package into Ghost
TryGhost/Ghost
Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.
- Official
Go-Redis Release Preparation
redis/go-redis
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
More from caidaoli/ccLoad
ccLoad Release Publisher
caidaoli/ccLoad
Publishes a ccLoad Beta or explicit stable release through a version-tag workflow, including commit, push, CI wait, GitHub Release and container image checks.
Related
Categories
Questions about CLIProxy Core Sync
What does CLIProxy Core Sync do?
Syncs or audits ccLoad's CLIProxyAPI protocol-conversion core and registered provider adapters against one pinned upstream commit, then verifies the result. Written in Chinese for the ccLoad repository, this skill syncs the four-protocol conversion core of CLIProxyAPI and the registered provider adapters, with their tests, as one atomic operation. By default it pins the latest stable upstream version, compares, integrates, updates the source record and verifies; a commit or tag you name is used instead.
When should I use CLIProxy Core Sync?
CLIProxy Core Sync fits situations like: aligning ccLoad with a new stable CLIProxyAPI release; auditing the core and provider adapter snapshots against upstream without changing files; syncing to a specific upstream commit or tag.
How do I install CLIProxy Core Sync in Claude Code?
Run `npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a claude-code`. Or copy the skill folder (.agents/skills/sync-cliproxy-core in caidaoli/ccLoad) into .claude/skills/sync-cliproxy-core in your project. Claude Code loads it when a task matches its description.
How do I install CLIProxy Core Sync in Codex?
Run `npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a codex`. Or copy the skill folder (.agents/skills/sync-cliproxy-core in caidaoli/ccLoad) into .agents/skills/sync-cliproxy-core in your project. Codex loads it when a task matches its description.
Can I use CLIProxy Core Sync in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add caidaoli/ccLoad --skill sync-cliproxy-core -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sync-cliproxy-core, .gemini/skills/sync-cliproxy-core, .github/skills/sync-cliproxy-core and .opencode/skills/sync-cliproxy-core in your project.
What does CLIProxy Core Sync need to run?
Going by SKILL.md and its folder, CLIProxy Core Sync needs a shell and Go for the scripts in its folder and the command-line tools its instructions call (git, bash, make and go). Our summary lists: A ccLoad checkout; A local or clonable CLIProxyAPI upstream repository; Go and bash for the verification scripts.
Does CLIProxy Core Sync access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is CLIProxy Core Sync safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does CLIProxy Core Sync use?
CLIProxy Core Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CLIProxy Core Sync use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.
What are the alternatives to CLIProxy Core Sync?
Skills that share tags, products or a category with CLIProxy Core Sync: ONNX Opset Bump Checklist (microsoft/onnxruntime, 22k stars), OBS Plugin Dependency Upgrade (sorayuki/obs-multi-rtmp, 5.1k stars), Breaking Change Analysis (ruby-git/ruby-git, 1.8k stars) and PR Bump (akitaonrails/my-skills, 213 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CLIProxy Core Sync?
caidaoli (a GitHub user) maintains it in caidaoli/ccLoad, which has 419 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: caidaoli/ccLoad on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.