一键在 Manus 中运行任何 Skill

开始使用

config-manager

星标21

分支4

更新时间2026年5月2日 11:30

Use AI Config Sync Manager's bundled OSS CLI for Claude configuration status, connect, and sync workflows.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

slash9494

slash9494/ai-config-sync-manager

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Config Manager

AI Config Sync Manager is an OSS workflow for keeping AI assistant configuration explicit, inspectable, and recoverable.

Rules

Resolve the bundled CLI from the host plugin root: ${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync. The plugin's launcher resolves the runtime in this order: AI_CONFIG_SYNC_ROOT (dev override), PATH ai-config-sync (npm install -g or npm link), then npm exec fallback.
Always export AI_CONFIG_SYNC_HOST=claude before invoking the CLI from this skill so the default sync direction is claude -> codex.
Prefer --dry-run before any write.
Status checks both global and current project scopes by default.
Print status CLI output as-is. Do not rewrite Codex and Claude status into different summary formats.
If status prints a detail file path, point the user to that file for full item lists and before/after previews.
Text sync for instructions and skills uses layered rules/terminology-map.json and generic rules/host-target-templates.json; user/project overrides may add product-specific workflow vocabularies and host-specific target templates.
Manual review means show the diff and require explicit approval before apply.
Verify backups before applying changes.
Require manual confirmation before running commands that modify Claude configuration.
Keep output focused on changed paths, skipped paths, and recovery steps.

Commands

AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" status
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" connect
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync --from claude --to codex --dry-run

同仓库更多 Skills

同仓库

agent-router

slash9494/ai-config-sync-manager

Choose one external agent for bounded comparison work.

2026-07-1221

sample

slash9494/ai-config-sync-manager

Greets the user politely.

2026-07-0421

config-manager-paraphrase

slash9494/ai-config-sync-manager

Paraphrase host-strict-vocab tokens (Claude-only in codex files, Codex-only in claude files) and register per-line overrides through the bundled open-source CLI so the result is masked from future status diffs.

2026-05-0921

config-manager-connect

slash9494/ai-config-sync-manager

Connect Codex with the bundled open-source AI Config Sync Manager CLI.

2026-05-0721

config-manager-reference

slash9494/ai-config-sync-manager

Print the AI Config Sync Manager reference (commands, areas, risk levels, mapping qualities, action verbs, terminology layers, hidden markers, file locations) through the bundled open-source CLI.

2026-05-0721

config-manager-status

slash9494/ai-config-sync-manager

Check AI Config Sync Manager status through the bundled open-source CLI.

2026-05-0721

name	config-manager
description	Use AI Config Sync Manager's bundled OSS CLI for Claude configuration status, connect, and sync workflows.

Config Manager

AI Config Sync Manager is an OSS workflow for keeping AI assistant configuration explicit, inspectable, and recoverable.

Rules

Resolve the bundled CLI from the host plugin root: ${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync. The plugin's launcher resolves the runtime in this order: AI_CONFIG_SYNC_ROOT (dev override), PATH ai-config-sync (npm install -g or npm link), then npm exec fallback.
Always export AI_CONFIG_SYNC_HOST=claude before invoking the CLI from this skill so the default sync direction is claude -> codex.
Prefer --dry-run before any write.
Status checks both global and current project scopes by default.
Print status CLI output as-is. Do not rewrite Codex and Claude status into different summary formats.
If status prints a detail file path, point the user to that file for full item lists and before/after previews.
Text sync for instructions and skills uses layered rules/terminology-map.json and generic rules/host-target-templates.json; user/project overrides may add product-specific workflow vocabularies and host-specific target templates.
Manual review means show the diff and require explicit approval before apply.
Verify backups before applying changes.
Require manual confirmation before running commands that modify Claude configuration.
Keep output focused on changed paths, skipped paths, and recovery steps.

Commands

AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" status
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" connect
AI_CONFIG_SYNC_HOST=claude "${CLAUDE_PLUGIN_ROOT}/bin/ai-config-sync" sync --from claude --to codex --dry-run