creating-letta-code-channels SKILL.md skillA
creating-letta-code-channels from letta-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add letta-ai/skills/creating-letta-code-channels@git:20261001.24a73a6Pins git:20261001.24a73a6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- letta-ai/skills
- Path
letta/creating-letta-code-channels/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261001.24a73a6, committed Oct 1, 2026
- First version recorded
- May 4, 2026
- Size
- 4,205 bytes
- Repository stars
- 152
- License
- a license file GitHub does not identify
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 1. Work in `~/letta/letta-code` or a worktree. 2. Read `src/channels/README.md` on branches with dynamic plugins. 3. For a user plugin, create: - `~/.letta/channels/<id>/channel.json` - `~/.letta/channels/<id>/plugin.mjs` - `~/.letta/channels/<id>/accounts.json` 4. Implement `messageActions` for both reply modes: explicit tool replies and automatic relay text use the common outbound adapter path. 5. Start with `dmPolicy: "pairing"` for testing, or `allowlist`/`open` for known headless deployments. 6. Test all four legs: …
Read the whole file at its exact version.
How to install
mdr add letta-ai/skills/creating-letta-code-channels@sha256:1a2c36442bf5b5d6The line at the top of this page pins the label git:20261001.24a73a6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_z3e64hvhuj6dyh2y)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 4, 2026 and Oct 1, 2026, about one every 150 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.24a73a6 latest | 2026-10-01 | 24a73a6 | 4,205 B | A | view · diff |
| git:20260504.974a7ff | 2026-05-04 | 974a7ff | 3,397 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4205 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
letta-ai/skills · 152 stars · license a license file GitHub does not identify · pushed 2026-10-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z3e64hvhuj6dyh2y GET https://markdownregistry.com/api/v1/resolve?ref=letta-ai/skills/creating-letta-code-channels GET https://markdownregistry.com/api/v1/blob/1a2c36442bf5b5d6ea59b5f1b3c902caab73a7b0b333732a3ab0a38ca2c1e28e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.