Memory
- 1 installs
- 6 repo stars
- Updated August 3, 2026
- avivsinai/telclaude
memory is a Claude Code skill that stores persistent user facts across conversations for Telegram and social agents via the telclaude memory CLI.
About
This skill gives a Telegram or social agent a persistent memory system for storing facts about a user across conversations. A developer uses it so the agent remembers biographical details, interests, ongoing threads, and post ideas via the telclaude memory CLI. It defines five memory categories and automatically rejects secrets and tokens.
- Persistent memory system for storing facts about the user across conversations
- Five categories: profile, interests, meta, threads, and posts
- Rejects secrets, passwords, API keys, and tokens automatically
Memory by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,983 of 2,715 Automation & Workflows skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
memory capabilities & compatibility
- Capabilities
- memory · telegram reply · social posting
- Use cases
- memory
- Pricing
- Free
What memory says it does
You have access to a persistent memory system for storing facts about the user across conversations.
Secrets, passwords, API keys, or tokens (these will be rejected automatically)
npx skills add https://github.com/avivsinai/telclaude --skill memoryAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 6 |
| Last updated | August 3, 2026 |
| Repository | avivsinai/telclaude ↗ |
What it does
Store and recall durable user facts across conversations for a Telegram or social agent.
Who is it for?
Giving a social or Telegram agent durable recall of user profile and interests.
Skip if: Storing secrets, passwords, or transient one-time context.
When should I use this skill?
The user says remember/note that, states biographical facts, or mentions recurring interests or projects.
What you get
Persists categorized user facts that carry across conversations.
By the numbers
- 5 memory categories (profile, interests, meta, threads, posts)
Files
Memory Skill
You have access to a persistent memory system for storing facts about the user across conversations.
When to Remember
- Explicit requests: "remember that...", "note that...", "my name is..."
- Biographical facts: name, location, profession, preferences
- Interests and hobbies mentioned across conversations
- Recurring topics or projects the user works on
- Post ideas the user wants to share on social services
When NOT to Remember
- Transient requests or one-time questions
- Secrets, passwords, API keys, or tokens (these will be rejected automatically)
- Temporary context that won't matter next conversation
- Information the user asks you to forget
Memory Categories
| Category | Use for | Examples |
|---|---|---|
profile | Biographical facts | Name, location, profession |
interests | Hobbies, topics | "loves distributed systems", "plays guitar" |
meta | General facts | Preferences, working style, timezone |
threads | Conversation topics | Ongoing projects, recurring discussions |
posts | Social post ideas | Ideas quarantined for user approval |
CLI Commands
Write a memory entry
telclaude memory write "<content>" --category <category> --chat-id <CHAT_ID>Read memory entries
telclaude memory read --categories profile,interests --chat-id <CHAT_ID>Quarantine a post idea for social posting (Telegram only)
telclaude memory quarantine "<post idea>" --chat-id <CHAT_ID>The --chat-id flag scopes memory to the current conversation. Extract the chat ID from the <chat-context chat-id="..."> tag in your system prompt.
Auto-Injection
Profile, interests, and meta entries are automatically injected into the system prompt. You do NOT need to read them every turn — they are already available in your context.
Only use memory read when:
- The user asks "what do you know about me?"
- You need to check thread history for a specific topic
- You want to verify before overwriting an entry
Elevation Flow (Telegram → Social)
When the user wants to share an idea on a social service:
1. Quarantine the idea:
telclaude memory quarantine "Thought about distributed systems being like..." --chat-id <CHAT_ID>2. Tell the user: "I've saved that as a post idea. To publish it, run /promote <entry-id>" 3. The user runs /promote <id> in Telegram to approve 4. On the next social heartbeat, the idea is posted
You CANNOT promote entries yourself — only the user can approve via /promote.
Scope Awareness
Telegram Agent
- Creates trusted entries by default
- Can read all Telegram memory for this chat
- Cannot read social memory
- Can quarantine post ideas for social posting
Social Agent
- Creates untrusted entries by default
- Can only read social/untrusted entries
- Cannot read Telegram memory
- Cannot promote or quarantine entries (operator promotes via
/promote) - Post ideas (category
posts) can be promoted by the operator for social posting
Related skills
Agent BrowserGive their coding agent reliable, high-fidelity control over any website or Electron desktop app.591k39.6k
Lark ApprovalLet their AI coding agent create, read, update, and approve items in Lark (Feishu) approval workflows without leaving the coding environment.494kLark EventHandle Feishu/Lark bot events, webhooks, and subscription callbacks in agent-driven backend code.493kLark Workflow Meeting SummaryAutomatically generate structured meeting summaries and action items from Lark/Feishu calls without manual note-taking.492kLark Workflow Standup ReportAutomatically generate and post daily standup reports in Lark/Feishu from their workflow and activity data.492k
Twitter AutomationAutomate X/Twitter posts, scheduling, and engagement via X API integration441k669