sync-agent-configs

Mirror allowlisted agent skills into a public repository with dry-run review and pruning.

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/guneysol/agent-configs --skill sync-agent-configs-guneysol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-agent-configs
Source: https://github.com/guneysol/agent-configs/tree/main/agents/skills/sync-agent-configs
Command: npx skills add https://github.com/guneysol/agent-configs --skill sync-agent-configs-guneysol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Publishing personal agent skills to a public repository risks leaking company-specific workflows, vendored third-party skills, credentials, and local runtime state. This Skill enforces an explicit allowlist so only reviewed, shareable skills are mirrored into the public agent-configs repository. ## Core Features & Use Cases - Allowlist-based syncing: Copies only the explicitly approved skill directories from ~/.agents/skills into the public repo, skipping everything else by default. - Dry-run-first workflow: Prints a file-level COPY/REMOVE/PRUNE plan before any change is applied, so you review the diff before committing. - Safe pruning and filtering: Removes only named excluded vendor/company directories and never syncs .env files, auth data, logs, sessions, or symlinks. - Use Case: After creating a new local skill, run the dry run to confirm nothing private is staged, then apply the sync and push the updated public mirror. ## Quick Start Use the sync-agent-configs skill to dry-run a mirror of my approved local skills into the public agent-configs repository and show me the plan.

Frequently Asked Questions about sync-agent-configs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish my local agent skills to a public repository safely?▼

Run the bundled sync script in dry-run mode first to review the file-level COPY/REMOVE plan, then re-run with --apply and --prune-excluded. Only skills on the explicit SHAREABLE_SKILLS allowlist are copied, so unreviewed local skills stay private.

How do I sync skills between Codex and Claude Code?▼

Keep shared skills in ~/.agents/skills and symlink ~/.claude/skills to that directory so both tools read the same copies. This Skill then mirrors the approved subset of that folder into the public agent-configs repository.

Does the sync script copy .env files or credentials?▼

No. The script ignores .env files, auth.json, history.jsonl, logs, sessions, shell snapshots, and .DS_Store during both planning and copying. It also refuses to copy symlinks and stops if a managed destination is a symlink.

What happens when I run the sync script without --apply?▼

Without --apply the script performs a dry run: it validates paths, computes the COPY/REMOVE/PRUNE plan for allowlisted skills, prints every planned action, and exits without modifying the repository.

Can the prune option delete unrelated skills in the target repo?▼

No. The --prune-excluded flag removes only the explicitly named excluded directories, such as vendored Vercel skills and company-specific skills, beneath agents/skills. Target-only generic skills are left untouched.