SKILLEMALL.ai

BC optimacros

Помощь с Optimacros: синтаксис формул, проектирование модели, выбор между справочниками/свойствами/кубами, работа с версиями и временем, DCA, UAM/МДП, Workflow, доступы, скрипты и практические паттерны моделирования. Использовать, когда пользователь просит помочь с формулами Optimacros, архитектурой модели, мультикубами, справочниками, доступами, блокировками, скриптами или разбором ошибок в OM.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 5 files body ≈ 5 600 tokens Open the sourcegithub.com analyzed 2 d ago

Помощь с Optimacros: синтаксис формул, проектирование модели, выбор между справочниками/свойствами/кубами, работа с версиями и временем, DCA, UAM/МДП…

As a process C 63/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

ProcedureSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
100
Quality 40%
50
Run on models
none yet
Process rating
C
63/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
40
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: 5. 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: Помощь с Optimacros: синтаксис формул, проектирование модели, выбо… ^ ); 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 ≈ 5600 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 63/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 40Consistency. Frontmatter name (optimacros) differs from the folder (optimacros-helper-ru)
  • 70Failures and branches. 18 branches
  • 70Execution cost. Instruction body is 5600 tokens
  • 85Steps. 275 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100When it triggers. States when to use and when not to
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • 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
  • +1No license
  • +3Description length 398: enough signal without eating the budget
  • +4Structure: 54 headings
  • +3Step-by-step instructions: 275 items
  • +2Bilingual instructions (RU + EN)

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