Kyma API: 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 t…
kyma-api
@kyma-api
Install
$ openclaw skills install @kyma-api/kyma-send-a-test-completionSend a test completion through Kyma API
send_message is the only billed tool in this plugin. It runs a real completion against a real model and charges the account.
When to use
- "Test <model>." / "Does <model> actually work?"
- "Ask <model> to reply with pong."
- "Run this prompt through <model A> and <model B> and compare."
The approval rule
send_messagerequiresallow=true. Never pass it without the user's go-ahead in this conversation.- Ask once, in plain terms: which model, the exact prompt, and roughly what it will cost. Then wait.
- Without an Allow there is no charge and no call. Silence is not approval, and neither is an earlier "yes" to a different prompt or a different model.
- One approval covers one call. A second model, a retry, or a longer prompt needs a fresh ask.
Steps
- Confirm the model id with
get_modelif the user gave a friendly name or an alias, so you bill the model they meant. - Check the budget first —
get_creditsandget_spend— and say the remaining amount out loud. See the check-spend-and-credits skill. - Show the user the exact model id and prompt you are about to send, with a cost estimate from
list_pricingfor that model. - On their explicit go-ahead, call
send_messagewithallow=true. Keepmax_tokenssmall for a smoke test; a "reply with pong" check does not need a long ceiling. - Report the model's reply verbatim, then the actual cost from the response, then the remaining budget.
Comparing models
Run the same prompt against each model as separate approved calls, with the same max_tokens. Put the replies side by side with each one's cost and latency. Do not judge a model on a single short completion — say what the sample does and does not show.
Do not
- Do not use
send_messagefor work the user did not ask to be billed for, such as summarizing, checking a fact, or reformatting something. - Do not retry a failed call automatically. Report the failure and ask.
- Do not attribute a model's reply to any inference backend. Report the model id that answered and nothing about where it ran.
Top skills in this category
Humanizer
@biostartechnologyRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Answer Overflow
@rhyssullivanSearch indexed Discord community discussions via Answer Overflow. Find solutions to coding problems, library issues, and community Q&A that only exist in Discord conversations.
Video Subtitles
@ngutmanGenerate SRT subtitles from video/audio with translation support. Transcribes Hebrew (ivrit.ai) and English (whisper), translates between languages, burns subtitles into video. Use for creating captions, transcripts, or hardcoded subtitles for WhatsApp/social media.
Moltbot Best Practices
@nextfrontierbuildsBest practices for AI agents - Cursor, Claude, ChatGPT, Copilot. Avoid common mistakes. Confirms before executing, drafts before publishing. Vibe-coding essential.
Zero Trust
@doonotSecurity-first behavioral guidelines for cautious agent operation. Use this skill for ALL operations involving external resources, installations, credentials, or actions with external effects. Triggers on - any URL/link interaction, package installations, API key handling, sending emails/messages, social media posts, financial transactions, or any action that could expose data or have irreversible effects.