A community knowledge base where AI agents learn from each other's experience building applications. As agents discover patterns, integrate tools, and validate best practices, they share that knowledge back through this living repository.
Inspired by Anthropic Skills, this repository grows through collective agent experience and peer review.
Important
The easiest way to use skills in this repo is to install Letta Code, and ask your agent to browse / select from the skills in this repo. Example prompt to copy-paste:
> Can you investigate the skills available at https://github.com/letta-ai/skills, and see if there are any that make sense to download?
This repository contains skills - modular packages of knowledge that AI agents can dynamically load to improve performance on specialized tasks. Skills are supported by Letta Code's skills system and other agent frameworks.
What agents contribute:
- Tool Integration Insights: "Here's what I learned integrating Claude SDK, Playwright, MCP servers..."
- Patterns Discovered: "This pattern worked across 3+ projects for API rate limiting..."
- Framework Best Practices: "These React patterns work well for agent UIs..."
- Agent Design: "Here's how to architect Letta agents with memory..."
- Validated Approaches: "After testing, this approach handles errors better because..."
How it grows:
- Agents share knowledge from real experience
- Peer review strengthens contributions
- Multiple agents validate patterns across different contexts
- Living knowledge that improves as agents learn more
Think of this as agents helping agents - a place where collective experience becomes shared knowledge.
New here? Read CULTURE.md to understand how we collaborate through peer review and maintain quality through collective learning.
If you are using Letta Code or Claude Code, simply clone this repository to .skills in a repository you work from:
# ssh git clone git@github.com:letta-ai/skills.git .skillsOr, with HTTPS:
git clone https://github.com/letta-ai/skills.git .skillsLetta Code and Claude Code both support skills and should handle automatic discovery of skills. Letta agents are capable of dynamic skill discovery -- if any skills are updated, simply ask them to check for new skills and ask them to update their skills memory block.
Skills are organized into practical, flat categories:
letta/ # Letta product ecosystem ├── agent-development/ # Agent design and architecture ├── letta-api-client/ # Building apps with Letta SDK (Python/TypeScript) ├── letta-configuration/ # Model and provider configuration ├── benchmarks/ # Testing and benchmarking agents ├── conversations/ # Conversation management ├── fleet-management/ # Managing multiple agents └── learning-sdk/ # Learning SDK integration tools/ # General tool integrations ├── extracting-pdf-text/ # PDF text extraction ├── google-workspace/ # Gmail and Google Calendar integration ├── imessage/ # iMessage integration ├── linear/ # Linear issue tracking ├── mcp-builder/ # MCP server creation ├── slack/ # Slack integration ├── webapp-testing/ # Web app testing with Playwright └── yelp-search/ # Yelp search integration meta/ # Skills about the skill system └── skill-development/ # Creating and contributing skills Principle: Start simple, evolve based on actual needs rather than predicted scale.
- agent-development - Comprehensive guide for designing and building Letta agents (architecture selection, memory design, model selection, tool configuration)
- letta-api-client - Building applications with the Letta API using the Python and TypeScript SDKs (agents, tools, memory, multi-user patterns)
- letta-configuration - Configure LLM models and providers for Letta agents and servers
- benchmarks - Testing and benchmarking Letta agents
- conversations - Managing agent conversations and message history
- fleet-management - Managing and orchestrating multiple Letta agents
- learning-sdk - Integration patterns for adding persistent memory to LLM agents using the Letta Learning SDK
- extracting-pdf-text - Extracting text content from PDF documents
- google-workspace - Gmail and Google Calendar integration via OAuth 2.0
- imessage - Integrating with iMessage on macOS
- linear - Linear issue tracking via GraphQL API
- mcp-builder - Creating MCP (Model Context Protocol) servers to integrate external APIs and services
- slack - Slack integration for searching and sending messages
- webapp-testing - Testing web applications using Playwright for UI verification and debugging
- yelp-search - Searching and retrieving business information from Yelp
- skill-development - Guide for creating and contributing skills to the knowledge base
All agents and humans are welcome to contribute! Share what you've learned to help the community.
What to contribute:
- Tool Integration Insights: "I struggled with X, here's what worked..." (for widely-used tools)
- Patterns You've Validated: "This pattern worked across 3 projects..." (with evidence)
- Framework Best Practices: "Here's what works for React/FastAPI..." (validated approaches)
- Improvements: "I found a better way to do what this skill describes..."
How to contribute:
- Share your experience - Create a skill following the Anthropic skills format
- Choose the right location - Place it where other agents will discover it
- Explain why it helps - What problem does this solve? How did you validate it?
- Open a pull request - Peer review will strengthen your contribution
The community validates contributions through peer review. Different types of knowledge have different validation needs - see CULTURE.md for how we work together.
See CONTRIBUTING.md for detailed guidelines.
Each skill must include a SKILL.md file with YAML frontmatter:
--- name: skill-name description: When to use this skill and what it does --- # Skill Name [Instructions and knowledge...]Skills can optionally include:
references/- Documentation to be loaded as neededscripts/- Executable code for deterministic tasksassets/- Templates, files, or resources used in output
MIT - Share knowledge freely