Skip to content

AI Agent Tools, Skills & Memory — How the Best Agents Remember & Act (2026)

Tools

A tool is any function an agent can call. From the LLM’s perspective, a tool has a name, description, and input schema — the LLM decides when and how to call it.

import anthropic
client = anthropic.Anthropic()
tools = [
{
"name": "get_weather",
"description": "Get the current weather for a city.",
"input_schema": {
"type": "object",
"properties": {
"city": {"type": "string", "description": "City name"},
},
"required": ["city"],
},
}
]
response = client.messages.create(
model="claude-opus-4-6",
max_tokens=1024,
tools=tools,
messages=[{"role": "user", "content": "What's the weather in Tokyo?"}],
)
# Check if the model wants to call a tool
if response.stop_reason == "tool_use":
tool_call = next(b for b in response.content if b.type == "tool_use")
print(f"Tool: {tool_call.name}, Input: {tool_call.input}")

Skills

A skill is a higher-level, reusable capability — typically a prompt + a tool or set of tools packaged together. Skills make agents composable.

In this project’s architecture, skills live as .md files in directives/ — structured prompts that tell the agent what to do and which execution scripts to use.

Memory Types

TypeWhat it storesPersistence
In-contextRecent conversationCurrent session only
External (vector)Semantic facts, documentsPermanent
Key-valueUser preferences, statePermanent
EpisodicPast task summariesPermanent

Implementing Memory with a Vector Store

# Simple in-memory vector store (use ChromaDB, Pinecone, etc. in production)
from anthropic import Anthropic
# Store memories as embeddings, retrieve by semantic similarity
# Example uses a simple list for illustration
memory_store = []
def remember(fact: str):
memory_store.append(fact)
def recall(query: str, top_k: int = 3) -> list[str]:
# In production: embed query, search vector store
# Here: simple keyword match for illustration
return [m for m in memory_store if any(w in m.lower() for w in query.lower().split())][:top_k]

MCP and Tool Discovery

MCP (Model Context Protocol) standardizes how agents discover and use tools. Instead of hardcoding tool schemas, an MCP client queries a server for available tools at runtime. See the MCP section for the full guide.