SKILLEMALL.ai
GitHub ↗ RU Sign in

CB 1c-db-cfe-admin

Управление расширениями в базе 1С через ibcmd: список, проверка применимости, безопасный режим, активность, удаление. Используй когда EDT нет и нужно включить или выключить расширение, снять безопасный режим либо удалить расширение из базы. Не используй, если EDT открыта (infobase_admin AI-EDT) или нужна сборка .cfe (скилы 1c-cfe-*).

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

Управление расширениями в базе 1С через ibcmd: список, проверка применимости, безопасный режим, активность, удаление.

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

Analyzer1CSecuritytype 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
88/100
safety, quality, tests
Safety 60%
95
Quality 40%
77
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
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.

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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Glob AskUserQuestion

Files scanned: 3. 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
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 70Failures and branches. 5 branches
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 12 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2201 tokens

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 335: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (2 code blocks)
  • +3All 2 scripts are documented
  • +2Bilingual instructions (RU + EN)

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