jarvis-settings

Configure Jarvis settings by merging changes into ~/.jarvis/config.json.

3|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/rsprudencio/claude-plugins --skill jarvis-settings
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jarvis-settings
Source: https://github.com/rsprudencio/claude-plugins/tree/main/plugins/jarvis/skills/jarvis-settings
Command: npx skills add https://github.com/rsprudencio/claude-plugins --skill jarvis-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jarvis configuration often requires repeatedly viewing and updating settings across vaults, which is error-prone and time-consuming. This skill provides a runnable, menu-driven configuration manager that reads the current config, merges changes safely, and guides first-time setup.

Core Features & Use Cases

  • View and display current config from ~/.jarvis/config.json and summarize key components (vault, Auto-Extract, memory DB, shell integration).
  • Interactively configure Vault path, Auto-Extract mode and thresholds, advanced settings (promotion thresholds, vault paths, memory system), and optional shell integration.
  • Merge changes into existing config without overwriting untouched keys and write defaults on first-time setup.

Quick Start

Run /jarvis-settings to view and update your Jarvis configuration.

Frequently Asked Questions about jarvis-settings

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

FAQPage Schema
How do I configure Jarvis settings like vault paths and auto-extract thresholds?▼

You can configure Jarvis settings by running a menu-driven interface that reads ~/.jarvis/config.json, lets you set vault paths, auto-extract thresholds, and memory mappings, then safely merges changes without overwriting untouched keys.

What is the best way to manage Jarvis configuration across multiple vaults without errors?▼

Managing Jarvis configuration safely is done through an interactive menu that reads and merges changes into ~/.jarvis/config.json, preserving untouched keys and offering a reindex option when vault paths change to prevent configuration drift.

Does Jarvis shell integration require manual configuration file editing?▼

Jarvis shell integration does not require manual editing; the configuration manager provides an optional interactive setup step that writes the necessary settings directly into ~/.jarvis/config.json during the guided workflow.

Can I set up Jarvis memory directory mappings and promotion thresholds on first launch?▼

First-time Jarvis setup is fully guided; the configuration manager writes default settings and lets you interactively configure memory directory mappings and promotion thresholds before saving to ~/.jarvis/config.json.

Why do my Jarvis configuration changes keep overwriting existing settings?▼

Jarvis configuration overwrites happen when editing files manually; using the configuration manager ensures safe merging of changes into ~/.jarvis/config.json, preserving existing untouched keys during updates.

When should I reindex after changing my Jarvis vault path?▼

You should reindex when your vault path changes; the Jarvis configuration manager detects vault path updates and offers a reindex option to ensure your memory database stays synchronized with the new directory.