SKILLEMALL.ai
GitHub ↗ RU Sign in

BF telegram-footer-patch

Add a Telegram private-chat footer (`🧠 Model + 💭 Think + 📊 Context`) to OpenClaw replies, with dry-run preview, backup, syntax validation, rollback, and restart guidance.

ClawHub Agent Skills author: Joey-Chen v1.0.11 MIT-0 7 files · 1 script body ≈ 1 167 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process F 38/100 · Will not run — References files that are not bundled: assets/footer-preview.jpg

AnalyzerTelegramInfrastructuretype 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
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
38/100
Will not run
References files that are not bundled: assets/footer-preview.jpg
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
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.
  2. The text references files that are not there: add them or drop the references.
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: 7. 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")
  • warning missing-ref reference to a missing file: assets/footer-preview.jpg
  • note frontmatter-key unknown frontmatter key "spdx"

Process rating: all ten parameters 38/100

Will not run. References files that are not bundled: assets/footer-preview.jpg
  • 0Tools and files. 1 referenced file(s) missing: assets/footer-preview.jpg
  • 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
  • 30Running it twice. 4 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 51 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1167 tokens

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
  • +2Single-language instructions
  • +3Description length 173: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 51 items
  • +4Has examples (5 code blocks)
  • +3All 3 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
The skill mostly does what it says, but it persistently patches OpenClaw’s live Telegram delivery code and adds under-disclosed runtime access to local session records.
LLM: suspicious (high) · VirusTotal: · 14 Jun 2026