SKILLEMALL.ai
GitHub ↗ RU Sign in

CF yuboto-omni-api

Implement, troubleshoot, and generate integrations for Yuboto Omni API (SMS/Viber/messaging endpoints, callbacks, lists/contacts/blacklist, cost/balance/account methods). Use when building code or workflows against Yuboto API docs, especially when endpoint details differ between PDF docs and live Swagger.

modbender/skill-library-mcp Agent Skills author: modbender MIT 12 files · 1 script body ≈ 649 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Implement, troubleshoot, and generate integrations for Yuboto Omni API (SMS/Viber/messaging endpoints, callbacks, lists/contacts/blacklist…

As a process F 46/100 · Will not run — References files that are not bundled: assets/OMNI_API_DOCUMENTATION_V1_10.pdf

IntegrationSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
C
70/100
safety, quality, tests
Safety 60%
65
Quality 40%
78
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: assets/OMNI_API_DOCUMENTATION_V1_10.pdf
Tools and files w 18
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.

Secrets in code 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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.

For the author

The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • 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 · 15

✓ No critical or high findings

Medium and low: 15
  • medium Secrets in code secret-labelled-token references/omni_api_v1_10_raw.md:1410
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    A324…0F6&apiKey=XFv4…dFL
  • medium Secrets in code secret-labelled-token references/omni_api_v1_10_raw.md:2011
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    10D9…21E&apiKey=XFv4…dFL
  • medium Secrets in code secret-labelled-token references/omni_api_v1_10_raw.md:2128
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    6865…561&pin=5327&apiKey=XFv4…kdF
  • medium Secrets in code secret-labelled-token references/omni_api_v1_10_raw.md:2309
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    ame&apiKey=XFv4…dFL
  • medium Secrets in code secret-labelled-token references/omni_api_v1_10_raw.md:2368
    Labelled token / key literal (vendor format unknown — verify it is not a live credential)
    xxxx&name=NewSubscriberListName&apiKey=XFv4…yMD
  • low Secrets in code secret-password-literal references/omni_api_v1_10_raw.md:356
    Hard-coded password / key literal (may be an example)
    &sms.sender=TestSender&sms.text=test%20message&apiKey=XFv4…ODA
  • low Secrets in code secret-password-literal references/omni_api_v1_10_raw.md:829
    Hard-coded password / key literal (may be an example)
    sms.twofa.isCaseSensitive=false&sms.twofa.expiration=180&apiKey=XFv4…ktN
  • low Secrets in code secret-high-entropy-token references/omni_api_v1_10_raw.md:830
    High-entropy token-like string (may be an id, hash or a credential)
    jBEQ…dFL
  • low Secrets in code secret-password-literal references/omni_api_v1_10_raw.md:1410
    Hard-coded password / key literal (may be an example)
    A324…0F6&apiKey=XFv4…dFL
  • low Secrets in code secret-high-entropy-token references/omni_api_v1_10_raw.md:1582
    High-entropy token-like string (may be an id, hash or a credential)
    TktN…dFL
  • low Secrets in code secret-password-literal references/omni_api_v1_10_raw.md:1659
    Hard-coded password / key literal (may be an example)
    https://services.yuboto.com/omni/v1/CostDetails?iso2=gr&apiKey=…
  • low Secrets in code secret-high-entropy-token references/omni_api_v1_10_raw.md:1660
    High-entropy token-like string (may be an id, hash or a credential)
    BEQi…dFL
  • low Secrets in code secret-password-literal references/omni_api_v1_10_raw.md:1755
    Hard-coded password / key literal (may be an example)
    https://services.yuboto.com/omni/v1/UserBalance?apiKey=…
  • low Secrets in code secret-high-entropy-token references/omni_api_v1_10_raw.md:1837
    High-entropy token-like string (may be an id, hash or a credential)
    i00O…dFL
  • low Secrets in code secret-high-entropy-token references/omni_api_v1_10_raw.md:2066
    High-entropy token-like string (may be an id, hash or a credential)
    RERC…dFL

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: assets/OMNI_API_DOCUMENTATION_V1_10.pdf

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: assets/OMNI_API_DOCUMENTATION_V1_10.pdf
  • 0Tools and files. 1 referenced file(s) missing: assets/OMNI_API_DOCUMENTATION_V1_10.pdf
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 13 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 100Steps. 38 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 649 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (3 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)
  • +4No input/output examples
  • -33 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 306: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 38 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (2 of 5)

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