Fast Telegram CLI for reading, searching, and sending messages.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontelegramExecute the skills CLI command in your project's root directory to begin installation:
Fetches telegram from skillhq/telegram and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate telegram. Access via /telegram in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
6
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
6
stars
Fast Telegram CLI for reading, searching, and sending messages.
Use this skill when the user:
npm install -g @skillhq/telegram
First-time setup requires API credentials from https://my.telegram.org/apps
telegram auth # First-time login
telegram logout # Clear saved session
telegram check # Verify session is valid
telegram whoami # Show logged-in account
telegram whoami --json # Account info as JSON
telegram inbox # Unread messages summary
telegram chats # List all chats
telegram chats --type group # Filter: user, group, supergroup, channel
telegram chats -n 200 # List up to 200 chats
telegram read "ChatName" -n 50 # Read last 50 messages
telegram read "ChatName" --since "1h" # Messages from last hour
telegram read "ChatName" --until "2h" # Messages up to 2 hours ago
telegram read @username -n 20 # Read DM with user
telegram read 123456789 -n 10 # Read by chat ID
telegram search "query" --chat "ChatName" # Search within chat
telegram search "query" --all # Search all chats (global)
telegram search "query" -n 20 # Limit results
telegram send @username "message" # Send DM
telegram send "GroupName" "message" # Send to group
telegram reply "ChatName" 12345 "response" # Reply to message ID
telegram contact @username # Get contact info
telegram members "GroupName" # List group members
telegram members "GroupName" -n 500 # Fetch up to 500 members
telegram admins "GroupName" # List admins only
telegram groups # List all groups
telegram groups --admin # Groups where you're admin
telegram kick "GroupName" @username # Remove user from group
telegram mute "ChatName" # Mute forever
telegram mute "ChatName" -d 1h # Mute for 1 hour
telegram mute @username -d 8h # Mute DM for 8 hours
telegram mute "GroupName" -d 1d # Mute for 1 day
telegram unmute "ChatName" # Unmute
telegram folders # List all folders
telegram folder "Work" # Show chats in folder
telegram folder-add "Work" "ProjectChat" # Add chat to folder
telegram folder-remove "Work" "ProjectChat" # Remove chat from folder
telegram sync # Sync last 7 days to ./telegram-sync
telegram sync --days 30 # Sync last 30 days
telegram sync --chat "ChatName" # Sync specific chat only
telegram sync --output ~/exports # Custom output directory
Most commands support multiple output formats:
| Flag | Use Case |
|---|---|
| (default) | Human-readable terminal output |
--json |
Structured JSON for programmatic processing |
--markdown |
Markdown-formatted for display or export |
telegram inbox --json # JSON format
telegram inbox --markdown # Markdown format
telegram read "Chat" --json # JSON with messages array
telegram read "Chat" --markdown # Markdown with messages
telegram chats --json # JSON with chat list
telegram members "Group" --markdown # Markdown member list
Supported on: inbox, read, search, chats, members, groups, contact, whoami
When using this CLI as an AI agent:
--json--markdown@, numeric IDs also worksend, reply, kick) should be confirmed with the user before executing-n to limit members output on very large groupsCheck inbox for unread messages:
telegram inbox
Read recent messages from a group:
telegram read "MetaDAO Community" -n 20
Get messages from the last 2 hours:
telegram read "Project Chat" --since "2h"
Search for a topic across all chats:
telegram search "futarchy" --all
Search within a specific chat:
telegram search "deadline" --chat "Work Team"
Send a message:
telegram send @username "Hello, checking in!"
Export a chat's history:
telegram sync --chat "Project Chat" --days 14 --output ~/exports
Filter chats by type:
telegram chats --type channel --json
Kick a user from a group:
telegram kick "My Group" @spammer
@ (e.g., @username)--since, --until) accept formats like "1h", "30m", "7d"sync command creates one markdown file per chat in the output directoryMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: telegram is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in telegram — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for telegram matched our evaluation — installs cleanly and behaves as described in the markdown.
telegram has been reliable in day-to-day use. Documentation quality is above average for community skills.
telegram is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
telegram fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: telegram is focused, and the summary matches what you get after install.
We added telegram from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in telegram — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend telegram for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 75