Run any Skill in Manus with one click

Get Started

config-manager-status

Stars21

Forks4

UpdatedMay 7, 2026 at 16:34

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

slash9494

slash9494/ai-config-sync-manager

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	config-manager-status
description	Check AI Config Sync Manager status through the bundled open-source CLI.

Config Manager Status

Use this skill when the user asks for config sync status, host detection, or Claude/Codex drift.

Behavior

If the user passes -h / --help (or asks for usage/help), run ... status --help and print the CLI output as-is — do not execute the status report.
Resolve the bundled CLI from the Codex plugin root: AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" status. The launcher resolves the runtime via AI_CONFIG_SYNC_ROOT (dev override) → PATH ai-config-sync → npm exec fallback.
Always export AI_CONFIG_SYNC_HOST=codex before invoking the CLI from this skill so the default sync direction is codex -> claude.
Default status checks both global and current project scopes.
Use --scope global, --scope project, or --scope all only when the user asks to narrow the report.
Use --include area[,area:item] and --exclude area[,area:item] when the user asks for a filtered diff. Item selectors are supported for itemized areas such as skills, permissions, and hooks.
Use ... status --json only when structured output is needed for follow-up automation.
Print the CLI output as-is for user-facing status. Do not rewrite it into a different summary format.
The CLI may collapse 10+ item diffs per scope/area into counts such as +12, -3, ~10, or !2; when that happens, tell the user to open the printed detail file for the full item list and before/after previews.
Preserve the CLI's concrete item/source details when relaying status. Do not collapse items into vague phrases such as "content differs" or "missing skills" without the detail-file pointer.
Do not infer sync state by editing or scanning config files directly when the CLI is available.
If the bundled CLI is unavailable, report that the user must npm install -g ai-config-sync-manager (or run npm link from the repo) and re-run connect.

Safety

Status is read-only.
Highlight items marked manual, partial, permissions, hooks, or custom commands as higher-risk apply targets.
Do not apply changes from a status command.

More from this repository

same repository

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-sync

slash9494/ai-config-sync-manager

Preview and apply AI config sync plans through the bundled open-source CLI.

2026-05-0721

Config Manager Status

Use this skill when the user asks for config sync status, host detection, or Claude/Codex drift.

Behavior

If the user passes -h / --help (or asks for usage/help), run ... status --help and print the CLI output as-is — do not execute the status report.

Resolve the bundled CLI from the Codex plugin root: AI_CONFIG_SYNC_HOST=codex "$HOME/.agents/plugins/ai-config-sync-manager/bin/ai-config-sync" status. The launcher resolves the runtime via AI_CONFIG_SYNC_ROOT (dev override) → PATH ai-config-sync → npm exec fallback.

Always export AI_CONFIG_SYNC_HOST=codex before invoking the CLI from this skill so the default sync direction is codex -> claude.

Default status checks both global and current project scopes.

Use --scope global, --scope project, or --scope all only when the user asks to narrow the report.

Use --include area[,area:item] and --exclude area[,area:item] when the user asks for a filtered diff. Item selectors are supported for itemized areas such as skills, permissions, and hooks.

Use ... status --json only when structured output is needed for follow-up automation.

Print the CLI output as-is for user-facing status. Do not rewrite it into a different summary format.

The CLI may collapse 10+ item diffs per scope/area into counts such as +12, -3, ~10, or !2; when that happens, tell the user to open the printed detail file for the full item list and before/after previews.

Preserve the CLI's concrete item/source details when relaying status. Do not collapse items into vague phrases such as "content differs" or "missing skills" without the detail-file pointer.

Do not infer sync state by editing or scanning config files directly when the CLI is available.

If the bundled CLI is unavailable, report that the user must npm install -g ai-config-sync-manager (or run npm link from the repo) and re-run connect.

Safety

Status is read-only.

Highlight items marked manual, partial, permissions, hooks, or custom commands as higher-risk apply targets.

Do not apply changes from a status command.