SKILLEMALL.ai
GitHub ↗ RU Sign in

AB db-list

Управление реестром баз данных 1С (.v8-project.json). Используй когда нужно работать с реестром баз — список баз, зарегистрировать базу в реестре, какие базы есть

Nikolay-Shirokov/cc-1c-skills Claude Code author: Nikolay-Shirokov MIT 1 file body ≈ 2 419 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Управление реестром баз данных 1С (.v8-project.json). Используй когда нужно работать с реестром баз — список баз, зарегистрировать базу в реестре, какие базы…

As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, running it twice

Procedure1CData 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
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
74
Run on models
none yet
Process rating
B
74/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Result and completion w 14
60
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: 1. 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")

Process rating: all ten parameters 74/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 2 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Failures and branches. 7 branches
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 16 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2419 tokens
  • 100Progress reporting. Reports progress

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
  • +1No license
  • +3Description length 162: enough signal without eating the budget
  • +4Structure: 14 headings
  • +3Step-by-step instructions: 16 items
  • +4Has examples (8 code blocks)
  • +2Bilingual instructions (RU + EN)

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