What problem does it solve?
Extending Letta Code with custom behavior requires knowing which mod capability to use, where to place the mod file, and how to guard registrations across host surfaces that load different capability subsets. This Skill guides the creation of correct, capability-guarded mod files without importing app internals.
Core Features & Use Cases
- Capability selection guidance: Maps user requests to the right mod type, including agent-callable tools, slash commands, lifecycle/turn events, permission overlays, local model providers, and panels.
- Scoped API patterns: Enforces use of ctx.conversation, ctx.cwd, and letta.capabilities guards so mods work across TUI, headless, and desktop listener hosts.
- Recipe references: Loads focused references for tools, commands, providers, events, permissions, UI panels, plan mode, analysis mode, and multi-capability architecture.
- Use Case: Ask the agent to add a /review slash command that runs while the main agent is busy, and it produces a capability-guarded mod file in ~/.letta/mods/ that forks a scoped conversation and returns handled output.
Quick Start
Ask the agent to create a mod that adds a slash command or tool, for example: create a mod that adds a /whereami command showing the current agent and working directory.