Skill

jarvis-consolidate

Browse and consolidate redundant memories via LLM-driven clustering

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

Memory Consolidation

LLM-driven consolidation finds groups of redundant memories and synthesizes them into authoritative summaries.

Commands

1. Dry Run (default)

Show what would be consolidated without making changes.

/jarvis-consolidate
/jarvis-consolidate dry-run

Output: List of memory clusters with size, similarity, importance, and previews.

2. Interactive

Step through each cluster, approve or reject consolidation.

/jarvis-consolidate interactive

For each cluster:

  1. Show memory contents and similarity score
  2. Call LLM to generate consolidated summary
  3. Show summary + confidence score + any contradictions
  4. Ask user: approve / reject / edit

3. Undo

Reverse a consolidation run.

/jarvis-consolidate undo <run_id>

Restores all superseded originals and soft-deletes the consolidated summaries.

Workflow

  1. Call find_consolidation_candidates() — ANN-based clustering
  2. For each cluster: a. Load full contents b. Run secret scanner on cluster contents c. Build consolidation prompt, call LLM d. Parse response, assess confidence e. Route based on mode (dry-run / interactive / auto)
  3. For approved consolidations: transactional apply
  4. Report results

Safety

  • Contradictions flagged, never auto-resolved — human reviews via interactive mode
  • Originals preserved — superseded, not deleted
  • Reversible — undo by consolidation_run_id
  • Secret scanning — cluster contents checked before LLM call
  • Disabled by defaultmemory.consolidation.enabled: false
</jarvis-consolidate>
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