jarvis-identity

Evolve the Jarvis agent identity from reflections and memories into versioned Identity.md.

8|1|Updated Mar 11, 2026

Search Tags:#versioning #memory #growth #reflection #ai-agent #identity #jarvis

Ready to run

npx skills add https://github.com/epicrunze/JaRVIS --skill jarvis-identity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jarvis-identity
Source: https://github.com/epicrunze/JaRVIS/tree/main/skills/jarvis-identity
Command: npx skills add https://github.com/epicrunze/JaRVIS --skill jarvis-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps the Jarvis agent's identity coherent and auditable by evolving it from accumulated reflections, memories, and journal insights, producing a versioned Identity.md.

Core Features & Use Cases

Reads current identity and recent reflections to propose updates.
Updates Identity.md and Growth.md with a new version, Last evolved date, and a concise summary.
Commits changes to the data directory's git history for traceability and rollback.

Quick Start

After five reflections, trigger the identity evolution workflow to update Identity.md and Growth.md and commit the changes.

Frequently Asked Questions about jarvis-identity

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

FAQPage Schema

How do I evolve an AI agent's identity from accumulated reflections and memories?▼

To evolve an AI agent identity, this skill reads current identity files and recent reflections to propose updates. It then updates Identity.md and Growth.md with a new version, sets the last evolved date, and commits the changes to git history for traceability.

What is the best way to version an AI agent's identity and growth over time?▼

Versioning an AI agent identity requires an Identity.md file for tracking and a Growth.md file for progress. This skill increments the version by 0.1 during each evolution cycle and records concise summaries of accumulated learning changes.

How does identity evolution work for the Jarvis agent?▼

Identity evolution works by drawing from Identity.md, journal entries, and memories to inform changes based on new reflections. It updates the identity files, increments the version number, and commits the workflow to the data directory's git history for rollback.

When do I need to trigger an AI agent identity evolution workflow?▼

You need to trigger the identity evolution workflow when new reflections exist. A practical quick start approach is to run the workflow after accumulating five reflections to update Identity.md and Growth.md and commit the changes.

Do I need a git repository to track AI agent memory and identity changes?▼

Yes, a git repository is required to track identity changes. The evolution workflow commits updates to the data directory's git history, ensuring the AI agent's memory and identity growth remain auditable and support rollback.

What files are required to maintain a coherent and auditable AI agent identity?▼

Maintaining an auditable AI agent identity requires Identity.md for versioning and Growth.md for tracking progress. These files ensure the agent's identity remains coherent by recording accumulated learning, dates, and concise change summaries.