AB send-a-test-completion
Run one real, billed chat completion through Kyma API with the user's explicit approval and report back the output and what it cost. Use when the user asks to test a model, check that a model actually answers, compare two models on the same prompt, or says something like "reply with pong via <model>".
Run one real, billed chat completion through Kyma API with the user's explicit approval and report back the output and what it cost.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 2. 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 65/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. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (send-a-test-completion) differs from the folder (kyma-send-a-test-completion)
- 100Tools and files. No external tools needed
- 100Steps. 15 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 528 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 302: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 15 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.