SKILLEMALL.ai
GitHub ↗ RU Sign in

DF telegram

Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.

razzant/ouroboros Agent Skills author: razzant 20 files · 19 scripts body ≈ 2 423 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.

As a process F 33/100 · No process to follow — weak spots: steps, result and completion, when it triggers

IntegrationTelegramCloudflareWriting and documentsLearningData and analyticstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
D
75/100
safety, quality, tests
Safety 60%
94
Quality 40%
47
Run on models
none yet
Process rating
F
33/100
No process to follow
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
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.

Obfuscation 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 files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.

For the author

Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.

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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Obfuscation uni-mixed-script-word lib/telegram_quiz.py:310
    Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence)
    answer is still accepted as the owner's message (В17a=A); a superseded card is
  • low Exfiltration exfil-webhook-url lib/telegram_api.py:581
    Webhook / callback URL commonly used for exfiltration (verify the destination) (the skill's own vendor host; quoted — discussed, not commanded)
    self.api_base = f"https://api.telegram.org/bot{self.token}"
    vendor-hostquoted

Files scanned: 20. 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")
  • note frontmatter-key unknown frontmatter key "type"
  • note frontmatter-key unknown frontmatter key "entry"
  • note frontmatter-key unknown frontmatter key "plugin_api"
  • note frontmatter-key unknown frontmatter key "runtime"
  • note frontmatter-key unknown frontmatter key "os"
  • note frontmatter-key unknown frontmatter key "permissions"
  • note frontmatter-key unknown frontmatter key "env_from_settings"
  • note frontmatter-key unknown frontmatter key "subscribe_events"
  • note frontmatter-key unknown frontmatter key "conflicts"
  • note frontmatter-key unknown frontmatter key "model_experience"
  • note frontmatter-key unknown frontmatter key "timeout_sec"
  • note frontmatter-key unknown frontmatter key "companion_processes"
  • note edit-residue the text marks something as outdated (lines 112): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 33/100

  • 0Steps. Prose only: no discrete steps
  • 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. 10 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2423 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)
  • +3Description length 90: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3No numbered steps or checklist
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • -5Long text without headings
  • -39 of 9 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions

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