Agent skill
sync
Sync stores from definitions config (bootstrap on fresh clone)
Install this agent skill to your Project
npx add-skill https://github.com/blueraai/bluera-knowledge/tree/main/skills/sync
SKILL.md
Sync Stores from Definitions
Sync stores from the git-committable definitions config. This is useful when:
- You've cloned a repo that has
.bluera/bluera-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__bluera-knowledge__execute tool with command "stores:sync" to sync stores from definitions
Optional arguments:
dryRun: true- Show what would happen without making changesprune: true- Remove stores not in definitionsreindex: 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 `.bluera/bluera-knowledge/stores.config.json` doesn't exist yet.
Store definitions are automatically created when you:
- Add a repo: `/bluera-knowledge:add-repo <url>`
- Add a folder: `/bluera-knowledge:add-folder <path>`
- Crawl a website: `/bluera-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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
when-to-query
When to use BK vs Grep/Read for current project
ui
Launch the admin web UI to browse stores, search, and manage knowledge
stores
List all indexed library stores
index
Re-index a knowledge store
test-plugin
Run comprehensive plugin validation test suite
search-optimization
Optimize BK search with intent, detail level, and store filtering
Didn't find tool you were looking for?