SKILLEMALL.ai

AC pollinations

Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images, videos, audio, vision/analysis, transcription) or mentions Pollinations. Supports 25+ models (OpenAI, Claude, Gemini, Flux, Veo, etc.) with OpenAI-compatible chat endpoint and specialized generation endpoints.

sundial-org/awesome-openclaw-skills Agent Skills author: sundial-org 4 files · 3 scripts body ≈ 1 643 tokens Open the sourcegithub.com analyzed 2 d ago

Pollinations.ai API for AI generation - text, images, videos, audio, and analysis. Use when user requests AI-powered generation (text completion, images…

As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationAI and agentsMedia and videotype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
90
Quality 40%
90
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
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.

Exfiltration 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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

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

    ✓ No critical or high findings

    Medium and low: 2
    • medium Exfiltration net-credential-use scripts/image.sh:176
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Authorization: Bearer $POLLINATIONS_API_KEY" -o "$OUTPUT" "$URL"
    • medium Exfiltration net-credential-use scripts/tts.sh:67
      Credential used in a network call (verify the destination is the intended service)
      curl -s -H "Content-Type: application/json" -H "Authorization: Bearer $POLLINATIONS_API_KEY" \

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

    Against the Agent Skills spec

    • note edit-residue the text marks something as outdated (lines 166): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 59/100

    • 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
    • 30Running it twice. 1 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 54 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1643 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 363: enough signal without eating the budget
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 54 items
    • +3Output format is stated explicitly
    • +4Has examples (10 code blocks)
    • +3All 3 scripts are documented

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