SKILLEMALL.ai

BB yacli-yandex

Yandex Mail, Disk, and Calendar via yacli MCP. Работает с Яндекс Почтой, Диском и Календарём: разбор входящих, поиск и чтение писем, ответы, загрузка и публикация файлов, просмотр и планирование событий.

ClawHub Agent Skills author: qoderone v1.0.2 MIT-0 10 files · 2 scripts body ≈ 1 944 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting

AnalyzerPersonal productivityAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
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: 10. 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: Yandex Mail, Disk, and Calendar via yacli MCP. Работает с Яндекс П… ^ ); 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")
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 67/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 20 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 5 branches
  • 85Steps. 98 steps, 2 vague phrases
  • 100Tools and files. No external tools needed
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1944 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +4No input/output examples
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +3Description length 203: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 98 items
  • +4Reference files are cited in the instructions (3 of 3)
  • +1License stated
  • +2Bilingual instructions (RU + EN)

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

External checks

ClawHub: clean
This skill is a disclosed Yandex Mail, Disk, and Calendar connector that requires the user to configure and trust local Yandex tooling.
LLM: benign (high) · VirusTotal: · 29 May 2026