SKILLEMALL.ai

BD price-probe-dogovornaya

> Заменяет оператора 1-й линии на 60-80%. Полноценный AI-отдел поддержки клиентов: автоматическая категоризация обращений, SLA-трекинг с алертами, эскалационная матрица L1→L2→L3, sentiment analysis, 15+ шаблонов ответов, NPS/CSAT аналитика, онбординг операторов, CRM-интеграция (Bitrix24/amoCRM). 10 режимов работы. Русский язык нативно. Экономит 15-30К руб/мес на зарплате операторов. Customer support AI replacing Tier-1 support agents by 60-80%. SLA tracking, ticket routing, escalation matrix L1/L2/L3, sentiment analysis, CRM integration. Russian language native. Dogfooded at RAAI.

ClawHub Agent Skills author: RAAIPRO v0.0.1 MIT-0 24 files · 3 scripts body ≈ 9 313 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationContact centreCustomer supporttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
76/100
safety, quality, tests
Safety 60%
100
Quality 40%
39
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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: 23. 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: Not a YAML token: Заменяет оператора 1-й линии на 60-80%. Полноценный AI-отдел поддержки клиентов: автоматическая категоризация обращений, SLA-трекинг с алертами, эскалационная матрица L1→L2→L3, sentiment analysis, 15+ шаблонов ответов, NPS/CSAT аналитика, онбординг операторов, CRM-интеграция (Bitrix24/amoCRM). 10 режимов работы. Русский язык нативно. Экономит 15-30К руб/мес на зарплате операторов. Customer support AI replacing Tier-1 support agents by 60-80%. SLA tracking, ticket routing, escalation matrix L1/L2/L3, sentiment analysis, CRM integration. Russian language native. Dogfooded at RAAI. at line 3, column 16: description: > Заменяет оператора 1-й линии на 60-80%. Полноценный AI-отдел под… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); 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")
  • warning body-long SKILL.md body ≈ 9313 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "target_client"

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 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
  • 40Consistency. Frontmatter name (price-probe-dogovornaya) differs from the folder (raai-price-probe-dogovornaya-20260421)
  • 40Execution cost. Instruction body is 9313 tokens: crowds the task out of the window
  • 100Tools and files. No external tools needed
  • 100Steps. 23 steps
  • 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)
  • +4Structure: 0 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • -5Long text without headings
  • -43 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +3Description length 587: enough signal without eating the budget
  • +3Step-by-step instructions: 23 items
  • +4Has examples (41 code blocks)
  • +2Bilingual instructions (RU + EN)

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

External checks

ClawHub: suspicious
This is a legitimate customer-support automation skill, but it asks for broad customer-message, CRM, and refund-related authority without enough scoping or approval controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026