Skill

jarvis-sync

Manage multi-remote memory sync — view status, force sync, retry failures, and validate routing rules.

From jarvis
Install
1
Run in your terminal
$
npx claudepluginhub rsprudencio/jarvis --plugin jarvis
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Jarvis Sync Management

Manage the multi-remote sync engine that routes memories to configured PostgreSQL remotes.

Commands

jarvis sync status (default)

Show current sync state:

  1. Read sync config via get_sync_config() from tools
  2. If sync disabled → report "Sync is disabled" and exit
  3. Call get_queue_stats() to get per-destination counts
  4. Present summary:
    • Enabled remotes (names only, never show URLs)
    • Pending / sending / done / failed / DLQ counts per remote
    • Overall health assessment

jarvis sync force [remote]

Force immediate drain of the sync queue:

  1. If remote specified, only process that destination
  2. Call _sync_iteration() directly (not the background loop)
  3. Report results

jarvis sync retry-dlq [remote]

Re-queue dead-letter entries for retry:

  1. Call retry_dlq(pool, destination) from sync_queue
  2. Report how many entries were reset to pending

jarvis sync lint

Dry-run rule evaluation against sample memories:

  1. Load routing rules from config
  2. Call validate_sync_config() — report any errors
  3. Fetch 10 recent memories from core.memories
  4. Evaluate routing for each, show which destinations each would route to
  5. Highlight any memories with no route (local-only by default)

jarvis sync sweep

Retroactively route existing memories that predate rule creation:

  1. Requires explicit user confirmation (destructive-ish: creates many queue entries)
  2. Load all active local-origin memories
  3. Evaluate routing for each
  4. Enqueue sync entries for unsynced destinations
  5. Report total entries created

Security

  • Never display remote URLs or credentials in output
  • Use redact_dsn() from sync_config if URL display is ever needed
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars3
Parent Repo Forks0
Last CommitMar 3, 2026