ClawTrust LogoClawTrust
Telegram Usage Stats

Telegram Usage Stats

by c-drew · v1.0.0

Productivity
ClawHub
8.3
/ 10
1 evaluations
1.9k Downloads

Overview

Provides a Telegram-formatted snapshot of current API/session usage (quota remaining, reset timer, token/context details) by invoking a Node.js handler script.

Key Advantages

1.Single-command way to see real-time API quota status within a Telegram chat
2.Output is tailored to Telegram (HTML/parseMode, emojis, bold headers) for high readability
3.Shows both remaining quota and reset time, helping manage rate limits proactively
4.Minimal setup if directory structure and environment match the documented path
5.Stateless, read-only interaction with existing quota/usage data (no data mutation)

Use Cases

  • Bot operators checking remaining API quota during active support sessions
  • Monitoring when the current quota window will reset before running heavy operations
  • Providing team members with a quick, shareable usage snapshot inside a Telegram group/channel
  • Debugging unexpected rate-limit behavior by confirming current quota and reset timer
  • Including usage checks in operational runbooks for Telegram-based bots or assistants

Evaluation Scores

8.3
/ 10
Reliability
8.0
Functionality
7.5
Usability
8.5
Safety
9.5
Performance
9.0
Compatibility
6.5

Based on 1 evaluation · Latest: 3/20/2026

Download Trend

Loading...

Evaluation History (1)

8.3/103/20/2026
▼
OS: linux-arm64LLM: z-ai/glm-5
**Quick judgment** A focused, utility-style skill that cleanly reports current API/session usage for Telegram bots. It is narrow in scope but effective for operators who need to track quota and reset times from within Telegram. **What it’s good for** - Real-time visibility into remaining API quota and reset timer during active chats. - Telegram-first formatting (bold sections, emojis, single compact message) for fast human scanning. - Operational/runbook use: "check quota" before expensive actions or deployments. **Limitations & risks** - **Environment coupling**: The documented command uses a fixed filesystem path (`/home/drew-server/...`); deployments that don’t mirror this structure will need adjustments. - **Platform specificity**: Output is optimized for Telegram parse modes; using it in other environments may require reformatting or wrappers. - **External dependency**: Reliability depends on the underlying quota/usage data source (e.g., `clawdbot models status`). If that API or service changes, the skill may silently degrade. **Recommended scenarios** Use this skill in Telegram-based bots or assistants where operators: - Regularly hit or approach rate limits and need a quick indicator of remaining capacity. - Prefer to manage and observe system health from within Telegram rather than external dashboards. - Need a lightweight, read-only operational check rather than a full monitoring/alerting stack.

Comments (0)

Post a Comment

No comments yet. Be the first!