letta-ai/creating-letta-code-channels
letta/creating-letta-code-channels/SKILL.md
Builds and debugs Letta Code channels, including first-party channel adapters and dynamic user channel plugins under ~/.letta/channels. Use when adding Telegram, WhatsApp, Bluesky, Slack, Discord, or custom channel support; testing channel routing, pairing, MessageChannel, runtime dependencies, or channel plugin manifests.
$ install --global
skillsauthnpx skillsauth add letta-ai/skills creating-letta-code-channelsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 7:49 AM134.4s5 files scanned
SKILL.md
- name:
- creating-letta-code-channels
- description:
- Builds and debugs Letta Code channels, including first-party channel adapters and dynamic user channel plugins under ~/.letta/channels. Use when adding Telegram, WhatsApp, Bluesky, Slack, Discord, or custom channel support; testing channel routing, pairing, MessageChannel, runtime dependencies, or channel plugin manifests.
- license:
- MIT
Creating Letta Code channels
Use this when adding or debugging Letta Code channel support.
First choice
- User plugin (
~/.letta/channels/<id>/) for headless experiments, community plugins, and fast workflow tests. - First-party channel (
src/channels/<id>/) when the channel needs bespoke Desktop UI, custom account snapshots, Slack/Discord-style auto-routing, rich protocol fields, or migration/compatibility shims.
User plugins cannot shadow first-party ids: telegram, slack, and discord are ignored under ~/.letta/channels/. Use ids like telegram-test, whatsapp-community, or custom-chat.
Core workflow
- Work in
~/letta/letta-codeor a worktree. - Read
src/channels/README.mdon branches with dynamic plugins. - For a user plugin, create:
~/.letta/channels/<id>/channel.json~/.letta/channels/<id>/plugin.mjs~/.letta/channels/<id>/accounts.json
- Always implement
messageActionsif agents should reply viaMessageChannel. - Start with
dmPolicy: "pairing"for testing, orallowlist/openfor known headless deployments. - Test all four legs:
- plugin discovery/import
- inbound
adapter.onMessage(msg)to route/pairing - routed channel notification reaches the agent
- outbound
MessageChannelcallsmessageActions.handleAction→adapter.sendMessage
- Run targeted tests, then
bun run typecheck,bun run lint,bun run build.
References
Read only what is needed:
references/user-plugins.md— dynamic plugin manifest/account/runtime/headless flow and gotchas.references/first-party-channels.md— first-party channel file cascade and safety checks.references/testing.md— smoke-test checklist and commands.
Scaffold helper
Use the bundled scaffold for a minimal user plugin skeleton. Replace <path-to-this-skill> with this skill directory path:
npx tsx <path-to-this-skill>/scripts/scaffold-user-channel-plugin.ts \
my-channel "My Channel" \
--runtime-package [email protected] \
--runtime-module some-sdk
It creates channel.json, plugin.mjs, and accounts.example.json. Replace the TODO inbound/outbound implementation with the real SDK calls.
Hard lessons
MessageChannelsilently feels broken ifplugin.messageActionsis missing. Every plugin that should reply needsdescribeMessageTool()andhandleAction().- For public channels, suppress tool approval/control prompts unless there is verified operator routing. Posting approval prompts publicly leaks tool input and invites forged
approvereplies. - User plugin runtime resolution must not count parent/dev
node_modules. Runtime modules should resolve from explicit runtime dirs only. - Headless pairing is CLI-first:
letta channels pair --channel <id> --code <code> --agent <agent-id> --conversation <conversation-id>. - Running listeners reload
pairing.yamlandrouting.yamlon the next inbound miss; restart only when adapter/account config itself changed.
Related Skills
letta-ai/navigating-chatgpt-history
testing
VerifiedTrustedCommunity
Navigates archived ChatGPT or Claude-style conversation exports and a MemFS reference archive on demand. Use when recalling what a past assistant knew, searching old conversations, rendering specific chats, seeding reference memory from export sidecars, or mining historical context without doing a full import.
106SKILL.mdUpdated May 23, 2026
letta-ai/letta-filesystem-to-memfs
testing
VerifiedTrustedCommunity
Migrates deprecated Letta Filesystem folders/files to MemFS using markdown document corpora, chunking, local lexical search, and QMD semantic search via the memfs-search skill. Use when replacing folders.files.upload, working with PDFs or document QA, or emulating open_file, grep_file, and search_file behavior.
106SKILL.mdUpdated May 23, 2026
letta-ai/compaction-prompts
data-ai
VerifiedTrustedCommunity
Configures Letta agent compaction settings and custom summarization prompts. Use when a user asks to change an agent's compaction prompt, improve summaries after context eviction, tune sliding-window or all-message compaction, or design companion/coding-agent continuity summaries.
106SKILL.mdUpdated May 23, 2026
letta-ai/memfs-search
development
VerifiedTrustedCommunity
Semantic search over agent memory files. Use when you need to find conceptually related memory blocks, discover forgotten reference files, check what you already know before creating new memory, or search beyond exact keyword matching. Currently supports QMD (local, no API keys).
106SKILL.mdUpdated Apr 6, 2026