SKILLEMALL.ai

BC 1c-platform-docs

1C platform API documentation tools via bsl-platform-help MCP server - search, info, members, constructors. Supports keyword, semantic (embeddings), and hybrid search. Use when checking built-in functions, types, methods, or properties of the 1C platform.

Desko77/claude-code-skills-1c Agent Skills author: Desko77 MIT 2 files body ≈ 846 tokens Open the sourcegithub.com↗ analyzed 6 d ago

1C platform API documentation tools via bsl-platform-help MCP server - search, info, members, constructors.

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationWriting and documentsAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
C
53/100
Has gaps
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

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

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 53/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
    • 100Tools and files. No external tools needed
    • 100Steps. 15 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 846 tokens
    • 100Running it twice. No mutating operations
    • 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)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +3Description length 255: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 15 items
    • +2Bilingual instructions (RU + EN)

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