SKILLEMALL.ai
GitHub ↗ RU Sign in

BB sergei-mikhailov-tg-channel-reader

Read posts and comments from Telegram channels via MTProto (Pyrogram or Telethon). Fetch recent messages and discussion replies from public or private channels by time window.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 17 files · 1 script body ≈ 4 537 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Read posts and comments from Telegram channels via MTProto (Pyrogram or Telethon).

As a process B 67/100 · Nearly there — weak spots: when it triggers, running it twice

ProcedureTelegramDockerWriting and documentsSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
80
Quality 40%
81
Run on models
none yet
Process rating
B
67/100
Nearly there
When it triggers w 12
20
Running it twice w 4
30
Tools and files w 18
60
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 4

    ✓ No critical or high findings

    Medium and low: 4
    • medium Dangerous commands cmd-shell-rc README.md:49
      Writes to a shell startup file
      > echo 'export PATH="$HOME/.venv/tg-reader/bin:$PATH"' >> ~/.bashrc
    • medium Dangerous commands cmd-shell-rc README.md:198
      Writes to a shell startup file
      echo 'export PATH="$HOME/.venv/tg-reader/bin:$PATH"' >> ~/.bashrc
    • medium Dangerous commands cmd-shell-rc README.md:204
      Writes to a shell startup file
      echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc
    • medium Dangerous commands cmd-shell-rc SKILL.md:454
      Writes to a shell startup file
      echo 'export PATH="$HOME/.venv/tg-reader/bin:$PATH"' >> ~/.bashrc && source ~/.bashrc

    Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 16 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, read, web, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4537 tokens
    • 85Steps. 37 steps, 2 vague phrases
    • 100Failures and branches. 3 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 12 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +3Description length 175: enough signal without eating the budget
    • +4Structure: 43 headings
    • +3Step-by-step instructions: 37 items
    • +3Output format is stated explicitly
    • +4Has examples (28 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.