jarvis-init

Scaffold a project-scoped .jarvis data directory with identity, memories, and journal storage.

8|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/epicrunze/JaRVIS --skill jarvis-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jarvis-init
Source: https://github.com/epicrunze/JaRVIS/tree/main/skills/jarvis-init
Command: npx skills add https://github.com/epicrunze/JaRVIS --skill jarvis-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

JaRVIS needs a persistent per-project data directory to store identity, memories, and journal entries. This skill initializes that structure and migrates older layouts if present.

Core Features & Use Cases

  • Scaffolds the .jarvis data directory at home with subdirectories memories and journal
  • Migrates existing per-project .jarvis as needed
  • Initializes IDENTITY.md, GROWTH.md, memories, and an initial git history
  • Enables a fresh, version-controlled foundation for memory persistence across sessions

Quick Start

Run jarvis-init to scaffold the JaRVIS data directory for the current project and initialize its identity, memories, and journal with a local git history.

Frequently Asked Questions about jarvis-init

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

FAQPage Schema
How do I scaffold a persistent data directory for project memory and journal storage?

To scaffold a persistent data directory, you initialize a project-scoped folder containing memories and journal subdirectories. This structure provides a clean home for persistent state, ensuring identity and historical data remain intact across sessions.

What is the best way to initialize git history for a local memory and identity tracking system?

Initializing git history for a memory tracking system creates an initial commit within the scaffolded data directory. This establishes a version-controlled foundation to track changes to identity files and journal entries over time.

Can I migrate an existing per-project data layout when setting up a new memory directory?

Yes, you can migrate an existing per-project data layout during initialization. The scaffolding step detects older configurations and applies migration rules, ensuring a clean transition without losing previous identity or journal data.

Do I need git installed to set up a version-controlled foundation for persistent state?

Yes, git is a required dependency to set up this version-controlled foundation. It initializes the local repository history within the data directory, enabling version tracking for identity, memories, and journal entries.

How does platform detection work when scaffolding a project-scoped data directory?

Platform detection identifies the operating system environment during initialization. The bundled scripts execute required steps, adjusting scaffolding and migration logic to ensure the data directory is structured correctly for the detected platform.

Why does my persistent state initialization create GROWTH.md and IDENTITY.md files?

Persistent state initialization creates IDENTITY.md and GROWTH.md files to establish a baseline for project identity and development tracking. These files are committed to git within the scaffolded directory, providing a structured starting point for memory persistence.