Skill

Sync Stores from Definitions

Syncs agent-knowledge stores from .agent-knowledge/stores.config.json after fresh repo clone. Recreates team-defined stores, detects orphans, supports dry-run, prune, and reindex options.

git-workflow

automation

npx claudepluginhub chris-xperimntl/agent-knowledge

Tool Access

This skill is limited to using the following tools:

mcp__agent-knowledge__execute

Preview

Sync stores from the git-committable definitions config. This is useful when:

SKILL.md

Similar Skills

List Knowledge Stores

Lists all configured knowledge stores (repo, file, web) in the project via mcp__agent-knowledge__execute tool, displaying name, type, ID, and source in a markdown table. Handles empty case with add instructions.

1 tool

agent-knowledge

knowledge-ops

173.8k

Manages knowledge bases: ingest, sync, organize, deduplicate, and retrieve across local files, MCP memory, vector stores, Git repos, Supabase, PostgreSQL. For knowledge management tasks like saving/searching info.

everything-claude-code

agent-prompts-warmup

194

Audits and syncs agent instruction files across coding agents like Claude Code, Cursor, Copilot, Gemini ensuring AGENTS.md matches targets (CLAUDE.md, .cursorrules). First-run scaffolding check; syncs after edits.

memex

Stats

Stars11

Forks3

Last CommitApr 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Sync Stores from Definitions

Sync stores from the git-committable definitions config. This is useful when:

You've cloned a repo that has .agent-knowledge/stores.config.json

You want to recreate all stores defined by the team

You want to check for orphan stores not in the config

Steps

Use the mcp__agent-knowledge__execute tool with command "stores:sync" to sync stores from definitions

Optional arguments:

dryRun: true - Show what would happen without making changes
prune: true - Remove stores not in definitions
reindex: true - Re-index existing stores after sync

Present results in a structured format:

## Sync Results **Created**: 3 stores - my-docs (file) - react-source (repo) - api-docs (web) **Skipped** (already exist): 2 stores - lodash - typescript-docs **Orphans** (not in definitions): 1 store - old-unused-store No errors occurred.

Dry Run Mode

When using dry run, show what WOULD happen:

## Sync Preview (Dry Run) **Would create**: 3 stores - my-docs (file) - react-source (repo) - api-docs (web) **Would skip** (already exist): 2 stores - lodash - typescript-docs **Orphans** (not in definitions): 1 store - old-unused-store To apply these changes, run without --dry-run

If No Definitions Found

If no store definitions config exists:

## No Store Definitions Found The config file `.agent-knowledge/stores.config.json` doesn't exist yet. Store definitions are automatically created when you: - Add a repo: `/agent-knowledge:add-repo <url>` - Add a folder: `/agent-knowledge:add-folder <path>` - Crawl a website: `/agent-knowledge:crawl <url>` The config file will be created automatically and can be committed to git for team sharing.

Error Handling

If some stores fail to sync, report them individually:

## Sync Results **Created**: 2 stores - my-docs - api-docs **Failed**: 1 store - react-source: Directory does not exist: /path/to/repo Continue to resolve the errors manually.