telegram-pairing-approver alternatives
The most used alternatives to telegram-pairing-approver are deepseek-reason, gog-weekly-digest, triage-ticket. All are communication skills with an active GitHub repository, ranked below by GitHub stars and recent activity.
| # | Skill | What it does | Runs | Updated | Stars |
|---|---|---|---|---|---|
| ref | telegram-pairing-approver meghal86 | 创建一个持久运行的Telegram机器人服务,用于自动处理配对代码并批准Telegram会话权限。使用时提供机器人令牌,自动创建机器人脚本和服务文件,并启动系统服务。适用于需要自动处理Telegram配对请求的场景。 | Skill | 5 months ago | 0 |
| 1 | deepseek-reason ruvnet | Reasoning-mode completion against DeepSeek's `deepseek-reasoner` model (R1) via /v1/chat/completions. Surfaces the model's chain-of-thought (`reasoning_content`) separately from the final answer (`content`), so callers can display or discard the CoT without re-parsing. Reads DEEPSEEK_API_KEY; degrades gracefully (exit 0 with status:degraded envelope) when unset or the API is unreachable. Ignores temperature/top_p per DeepSeek's spec for reasoner models. | Skill | today | 79k |
| 2 | gog-weekly-digest openclaw | Read-only weekly digest across Google Calendar, Gmail, and Tasks with gog. | Skill | 4 days ago | 8.5k |
| 3 | triage-ticket agentscope-ai | First-response playbook for an inbound customer message — classifies the ticket, restates the issue, gathers missing context, and routes the reply. | Skill | 3 days ago | 6.1k |
| 4 | commit-message zulip | Write a commit message following Zulip's format. Use whenever writing or rewording any commit message. | Skill | today | 26k |
| 5 | wepush rememberber | Use WePush Next to inspect push channels and jobs, prepare message and recipient drafts, run dry runs, send explicitly authorized notifications, and inspect delivery results. Use when the user asks to operate WePush, not for unrelated messaging services or editing WePush source code. | Skill | 19 days ago | 4.7k |
| 6 | organization agentscope-ai | Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id. | Skill | 3 days ago | 5.8k |
| 7 | messages-custom-commands fern-api | How to author custom commands for the messages CLI using the co-generated SDK. | Skill | yesterday | 3.8k |
| 8 | bro nicknisi | Restate the last message in plain human language, with no jargon. | Skill | 7 days ago | 3k |
| 9 | claw-background-jobs x-cmd | Claw background job management using x agent run and x agent job. Use when the agent needs to offload complex or long-running tasks that would block the chat. | Skill | 9 days ago | 4.7k |
| 10 | followups vellum-ai | Track sent messages awaiting responses across communication channels | Skill | 3 days ago | 1.4k |
| 11 | commit FlorianBruniaux | Generate a conventional commit message for staged changes | Skill | 4 days ago | 6.2k |
| 12 | tone-fixer mohitagw15856 | Rewrite a message to the tone you actually want — less harsh, more confident, warmer, firmer, or shorter — without losing your point. Use when asked to make this sound less rude, soften this email, make me sound more confident, make this nicer/firmer, or fix the tone of a message. Produces two or three rewrites at the target tone, a note on exactly what was changed and why, and a flag if the original's tone was fine as-is. | Skill | today | 1.5k |
Questions
What is the best alternative to telegram-pairing-approver?
By usage, deepseek-reason is the most popular alternative, with 79k GitHub stars. The right choice depends on which features and hosting you need.
Is telegram-pairing-approver still maintained?
Its last commit was 5 months ago. You can see current activity on its listing page.