Use when full MTProto control of Telegram account via Telethon. DM, Voice
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill telegram-userbot --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Telegram Userbot?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-telegram-userbot)More formats (shields.io, HTML) on the badges page.
---
name: telegram-userbot
description: Use when full MTProto control of Telegram account via Telethon. DM, Voice
Note, Call, Video Call, Group/Channel management, member scraping, bot cloning,
outreach automation, broadcast, CRM tracking, content reposting, scheduled messaging,
webhook triggers. Use for all Telegram automation as a real user (not bot API).
domain: automation
author: oyi77
license: Apache-2.0
subdomain: workflow-automation
tags:
- api
- automation
- productivity
- telegram
- userbot
- video
- voice
- webhook
version: 1.0.0
category: automation
---
# Telegram Userbot
## When to Use
**Trigger phrases:**
- "telegram userbot"
- "Use when working with telegram userbot"
- Automating Telegram messaging (DMs, group messages)
- Scraping Telegram group/channel members
- Running Telegram-based lead generation
- Automating Telegram account activities
- Building Telegram automation workflows
## When NOT to Use
- For one-off tasks that will never repeat
- When the process requires human judgment at every step
- When the cost of automation exceeds the cost of manual execution
## Overview
Telegram Userbot automates workflow automation to reduce manual effort and increase reliability.
## Workflow
```python
# Example: Workflow automation
import schedule
import time
def run_workflow():
data = fetch_data()
processed = transform(data)
deliver(processed)
schedule.every().hour.do(run_workflow)
while True:
schedule.run_pending()
time.sleep(60)
```
1. **Define triggers** — Set up events or schedules that initiate the automation
2. **Configure inputs** — Specify data sources and parameters
3. **Design pipeline** — Define the sequence of automated steps
4. **Add error handling** — Set up retries, alerts, and fallback paths
5. **Test end-to-end** — Validate the full automation with realistic data
6. **Deploy and monitor** — Activate and track performance
## Configuration
- Set trigger conditions (schedule, webhook, event)
- Define input validation rules
- Configure notification channels for alerts
- Set retry policies and timeout limits
## Best Practices
- Start with simple automations and iterate
- Add logging at every step for debugging
- Use idempotent operations where possible
- Test with edge cases before deploying
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "Manual is faster for one-off tasks" | One-off tasks become recurring. Automate early, save time later. |
| "I will add error handling later" | You never do. Handle errors from day one. |
| "Automation is overkill" | If you do it twice, automate it. If you do it daily, it is critical infrastructure. |
## Process
1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run telegram userbot workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results
## Verification
- [ ] All steps executed successfully
- [ ] Results validated against acceptance criteria
- [ ] Error handling tested with edge cases
- [ ] Documentation updated with findingsIs this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!