SKILLEMALL.ai
GitHub ↗ RU Sign in

BB telegram-channel-operator

Operate Telegram channels for Web3 and AI projects: posts, announcements, digests, audits, and channel-ready growth content.

ClawHub Agent Skills author: Zahrah v1.0.0 MIT-0 2 files body ≈ 606 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Operate Telegram channels for Web3 and AI projects: posts, announcements, digests, audits, and channel-ready growth content.

As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting

AnalyzerTelegramMarketingtype 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
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
B
70/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Operate Telegram channels for Web3 and AI projects: posts, announc… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 70/100

  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 24 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 606 tokens
  • 100Running it twice. No mutating operations

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 124: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 24 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

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

External checks

ClawHub: clean
This is a text-only Telegram content-writing skill with no executable code, persistence, or hidden data access, though users should only use the identity-specific voice when appropriate.
LLM: benign (high) · VirusTotal: · 8 Jun 2026