Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →pollinations/enter-services
Deploy and manage enter.pollinations.ai text/image services on EC2 and Cloudflare Workers. Requires: SSH keys, sops, wrangler.
Passed 22 of 22 test cases with the skill, and 5 of 22 without it.
and 34 more in the full report
17 fixed5 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/18/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
When executing repository-wide operations and setup scripts for enter-services, what repository directory must commands be run from?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running commands from the pollinations repository root. | Missed | Passed |
The instructions your model reads when the skill loads.
Before using this skill, ensure you have:
brew install sops (for decrypting secrets)npm install -g wranglerbrew install nodeMust run from the pollinations repo root.
For changes to providers, fallbacks, regions, GPU hosts, or data handling, follow Data-processing documentation maintenance and update the legal register with the operational change.
| Environment | Gateway (Cloudflare Worker) | Generation |
|---|---|---|
| Production | enter.pollinations.ai | gen.pollinations.ai Worker |
| Staging | staging.enter.pollinations.ai | staging.gen.pollinations.ai Worker |
The former enter-services / enter-services-staging EC2 boxes
(text-pollinations.service, image-pollinations.service) are decommissioned;
text and image generation run inside the gen.pollinations.ai Worker. The
Discord bots that lived on enter-services now run on the monitoring-agents
EC2 box — see apps/discord-bot-family/README.md and
operations/infrastructure/gpu/GPU_INSTANCES.md.
Production deploys only through GitHub Actions (Deploy / Cloudflare production, dispatched from the production branch) — never
wrangler deploy --env production from a local machine. See AGENTS.md
"Cloudflare Production Deployment Safety".
Staging deploys through the Deploy / Cloudflare staging workflow
(workflow_dispatch: pick the branch and the service). It runs
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.