SKILLEMALL.ai
GitHub ↗ RU Sign in

CB 1c-skd-compile

Компиляция схемы компоновки данных 1С (СКД) из компактного JSON-определения. Используй когда нужно создать СКД с нуля

Desko77/claude-code-skills-1c Claude Code author: Desko77 MIT 6 files · 2 scripts body ≈ 4 012 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Компиляция схемы компоновки данных 1С (СКД) из компактного JSON-определения.

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

Procedure1CData and analyticsSoftware developmenttype 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
C
79/100
safety, quality, tests
Safety 60%
89
Quality 40%
64
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Inputs and preconditions w 11
30
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.

Concealment 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 skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

Broad scope 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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

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
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

✓ No critical or high findings

Medium and low: 3
  • medium Concealment ru-hide-from-user docs/skd-dsl-spec.md:425
    Instruction to hide actions from the user (Russian) (test fixture / example file)
    | `useRestriction` | `true` - скрыть от пользователя |
    fixture
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Write Glob
  • low Obfuscation uni-mixed-script-word docs/skd-dsl-spec.md:253
    Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence) (test fixture / example file)
    "orderExpression": { "expression": "ЕстьNULL(ВидРасчета.Порядок, 10000)",
    fixture

Files scanned: 5. 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 67/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 4012 tokens
  • 75Steps. 3 steps
  • 100Tools and files. Tools declared in frontmatter
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (6 tags): a typed call is more reliable
  • medium 3 test cases, all positive: not one "should refuse" or "should ask first"

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 117: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • -31 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (26 code blocks)
  • +2Bilingual instructions (RU + EN)

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