Agent Md — AI skill for Claude Code
The field guide to AI context files — CLAUDE.md, MEMORY.md, SKILLS.md, SOUL.md and how they shape agents.
How to install Agent Md
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open eshwarvijay/agent-md and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Agent Md does
The field guide to AI context files — CLAUDE.md, MEMORY.md, SKILLS.md, SOUL.md and how they shape agents.
Alternatives in AI
- Memmy Agent — 🍙 A personal AI agent & local memory hub for all AI agents, gives every AI one shared, fully controlled memor 1k ★
- Guild — Shared context, memory, and task coordination across AI coding agents 311 ★
- Claude Code Patterns — Field-tested Claude Code patterns & anti-patterns for personal agents — an AI workflow that compounds: knowled 120 ★
README
Agents.md
**The field guide to AI context files** — the small set of Markdown documents that quietly decide who your agent is, what it knows, what it can do, and how it behaves.
If you've ever dropped a `CLAUDE.md` into a repo, scribbled notes into a `MEMORY.md`, or wondered why some agents feel coherent across sessions while others forget everything the moment you close the terminal — this guide is for you.
These files aren't a framework you install or a spec you have to obey. They're **conventions** — the same way `README.md`, `LICENSE`, and `.gitignore` became conventions long before anyone standardized them. A handful of teams started naming their agent-configuration files the same way, the names stuck, and now they form a loose but powerful vocabulary for *programming agents in plain English*.
This document is a deep, practical tour of that vocabulary.
Table of Contents
- Why context files exist
- The mental model: a layered identity
- `CLAUDE.md` — the operating manual
- `MEMORY.md` — persistent knowledge
- `SKILLS.md` — the capability registry
- `SOUL.md` — identity and values
- How the files compose
- The wider machinery
- Anti-patterns and best practices
- A complete worked example
- References
1. Why context files exist
A large language model is, by default, **stateless and contextless**. Every conversation starts from zero. It doesn't know your coding standards, your name, which tools it's allowed to call, or what it learned yesterday. You *can* re-explain all of that in every prompt — but that's slow, error-prone, and impossib
Related Skills
Wandesk
Wandesk — Give intelligence shape. Let AI sculpt your desktop. An open-source AI desktop with App Workshop, sh
Web Fetch
LLM-neutral skill that fetches a URL to a temp file so agents can pipe the path through rg / jq / awk instead
Kincode
AI coding assistant in Go. 9MB single binary, zero dependencies. MCP support, Soul files for custom AI persona
Agent Soul
Provide AI agents with continuous identity and persistent memory across sessions and devices using a Git-nativ
Soulcraft
Give your agent a soul that survives model swaps. Identity kit for persistent AI agents: character, memory, an
Beyond The Chatbox
A field guide for moving beyond web chat AI — Claude Desktop and Claude Code setup, context engineering, and p
Related Agents
Brainstem Copilot.Agent
One native Copilot chat with both Brainstem and Brain Surgeon. Address either by name to use capabilities or t
Workspace Writer
Writes a Jarvis's own working files from a confirmed .jarvis/jarvis-spec.md — SOUL.md (persona and voice), USE
Schema Refactor Worker
Performs large mechanical refactors across generated analyzer files when the ontology's field shape changes (e