Telegram archive: chats, messages, contacts, folders, search; import from Telegram Desktop/macOS.
64
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/telecrawl/SKILL.mdUse this for Telegram history questions. Local archive first; the Telegram apps only for live/current state.
~/.telecrawl/telecrawl.dbtdata or native macOS Telegram Postbox (auto-detected)telecrawlclawmac (~200 chats). Local DBs on other Macs may be empty — check status first and prefer SSH to the archive host over answering from an empty DB:ssh -o RequestTTY=no -o RemoteCommand=none steipete@clawmac 'zsh -lc "telecrawl --json status"'telecrawl --json statusEmpty counts mean no import has run on this machine, not "no Telegram data".
All read commands take --json.
telecrawl --json chats --limit 20
telecrawl --json chats --unread
telecrawl --json messages --chat <ID> --limit 50 --after 2026-01-01
telecrawl --json search "query" [--chat ID]
telecrawl --json contacts --limit 50
telecrawl --json folders
telecrawl --json topics --chat <ID>telecrawl doctor # verify a Telegram data source is readable
telecrawl import # merge-import from detected local Telegram app
telecrawl import --fetch-media # also pull Telegram cloud mediaImports merge by default; --restore replaces the archive — treat as destructive and confirm first.
Encrypted age shards to a git repo:
telecrawl backup status
telecrawl backup push92442a1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.