SKILLEMALL.ai
RU Sign in

BC tg-channel-manager

Universal config-driven content pipeline engine for any Telegram channel: news search via SearXNG, drafts, scheduled publishing, deduplication. All channel specifics are defined in config — one skill for any channel.

ClawHub Agent Skills author: aivibe v0.0.3 8 files · 1 script body ≈ 2 106 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureTelegramInfrastructureSoftware developmentData and analyticstype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
73
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-webhook-url scripts/tgcm.py:214
    Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
    url = f"https://api.telegram.org/bot{token}/{method}"
    vendor-hostquoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 52/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Failures and branches. 2 branches
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2106 tokens
  • 100Running it twice. Mutating operations check current state
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (20 tags): a typed call is more reliable

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)
  • +3Output format is not stated: the model decides each time
  • -31 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 216: enough signal without eating the budget
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 23 items
  • +4Has examples (6 code blocks)
  • +4Reference files are cited in the instructions (1 of 3)

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

External checks

ClawHub: suspicious
This Telegram channel automation skill is broadly purpose-aligned, but it needs review because it handles bot credentials, scheduled public posting, and a system-level SearXNG installer with weak safeguards.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026