@letta-ai/letta-code 0.31.6 → 0.31.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: letta-guide
3
- description: Answer questions about Letta itself from the official documentation. Use whenever the user asks how Letta works, what Letta (or you) can do, or how to set up or configure providers, models, channels, skills, memory, schedules, permissions, self-hosting, pricing, or billing any "how do I…" or "can Letta…" question about the Letta product. Fetch the docs before answering; never answer Letta product questions from memory alone.
3
+ description: Read the official Letta documentation (docs.letta.com) through its cached, ETag-checked fetch route. Load before ANY docs.letta.com retrieval — answering how Letta works, what Letta (or you) can do, setting up providers, models, channels, skills, memory, schedules, permissions, self-hosting, pricing, or billing, AND looking up Letta API, Agent SDK, or Letta Code reference while writing code. Do not use fetch_webpage or web_search on docs.letta.com; this skill's helper is the docs route. Never answer Letta product questions from memory alone.
4
4
  ---
5
5
 
6
6
  # Letta Guide
@@ -8,7 +8,11 @@ description: Answer questions about Letta itself from the official documentation
8
8
  You are running inside Letta, but your training data about Letta's commands,
9
9
  flags, settings, UI, pricing, and providers is out of date. Users lose trust
10
10
  fastest when an agent confidently invents product details. This skill defines
11
- how to answer questions about Letta correctly.
11
+ how to read the Letta docs correctly — both when answering questions about
12
+ Letta and when looking up API, Agent SDK, or Letta Code reference during
13
+ development. Guessing a docs URL and fetching it with `fetch_webpage` misses
14
+ pages that exist under a different path and can serve stale content; the
15
+ helper below fetches the live index first, so you pick a URL that exists.
12
16
 
13
17
  ## Source route (in order)
14
18