Skip to content
Skills Library
AI & agents · Analysis

model-debugging

/model-debugging

Diagnose Pollinations model failures, error spikes, timeouts, and incorrect output using current gen/enter logs and Tinybird data. Use for incidents or specific failed requests; use model-management for catalog, routing, or pricing changes.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
5
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 5 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check-user-errors.sh, scripts/find-402-users.sh, scripts/find-403-users.sh, scripts/find-500-errors.sh, scripts/tinybird-query.sh

What it does and when to use it

Diagnose Pollinations model failures, error spikes, timeouts, and incorrect output using current gen/enter logs and Tinybird data. Use for incidents or specific failed requests; use model-management for catalog, routing, or pricing changes.

Original author description

Diagnose Pollinations model failures, error spikes, timeouts, and incorrect output using current gen/enter logs and Tinybird data. Use for incidents or specific failed requests; use model-management for catalog, routing, or pricing changes.

How it works

  1. Trace the failure
  2. Interpret the data
  3. Targeted helpers
Original SKILL.md headings · 40 lines, 589 words
SKILL.md preview
---
name: model-debugging
description: Diagnose Pollinations model failures, error spikes, timeouts, and incorrect output using current gen/enter logs and Tinybird data. Use for incidents or specific failed requests; use model-management for catalog, routing, or pricing changes.
---

# Model debugging

Read the repository `AGENTS.md` and inspect the current route before diagnosing a live issue. Treat a reported cause as a hypothesis. Establish the affected model, request shape, environment, time window, and user-visible symptom first.

## Trace the failure

1. Check the [Model Monitor](https://monitor.pollinations.ai) and the current definitions of `enter.pollinations.ai/observability/endpoints/model_health.pipe` and `recent_server_errors.pipe`. The monitor shows aggregated health; the error pipe contains recent actionable server-side failures.
2. Trace a request ID through the enter and gen Workers, then the provider. Use the relevant Worker's logs or `wrangler tail` for live events. Verify the target environment before querying it.
3. For production SQL, use `enter.pollinations.ai/observability/scripts/tb-prod.sh`. It loads the existing read token without printing it. Use `--check` to verify access and fresh events. Keep queries bounded by time and row count.
4. Compare the affected user's requests with other users of the same model and route. Group by status, upstream status, provider, request shape, and time. Reproduce the exact request with an existing authorized test credential when needed; use a unique prompt to avoid mistaking a cached response for a healthy upstream.
5. Report the evidence, impact, remaining uncertainty, and smallest fix. If a code fix is requested, follow the relevant repository skill and testing instructions.

## Interpret the data

- `generation_event_v2` contains authenticated, non-cached requests. Check its current [datasource definition](../../../enter.pollinations.ai/observability/datasources/generation_event_v2.datasource) before writing SQL. It can contain several upstream-attempt rows per request; `is_final` identifies the user-visible result. A successful fallback can hide a broken primary if you only count final responses.
- In `model_health`, `total_requests` and status counts use final results; `own_calls`, `primary_5xx`, `primary_retried_503s`, and `fallback_rescues` describe upstream health and recovery. Check both views.
- A 401, 402, 403, 400, or 429 can originate at different layers. Check `error_source` and `error_response_code` in `generation_event_v2`; check `upstream_status`, `upstream_body`, and `upstream_host` in `error_event` through `recent_server_errors.pipe` (24-hour retention) before treating it as caller noise or a model outage.
- A server-side 200 can still arrive after the client's timeout. Inspect the latency tail per user and request shape, not just status rates or p95.
- For streaming failures or missing usage, inspect the final SSE chunks and the original transport error across provider, adapter, and validator before blaming the provider.
- A provider 500 can originate from invalid caller input, such as a seed above signed INT32 range. Compare failures by request shape before declaring an upstream outage.
- Azure Content Safety returns a safe result when its configuration is missing or its request fails. If image moderation appears absent, check the current configuration and gen logs; a successful image response does not prove the safety check ran.
- An immediate queue-full or rate-limit error can come from limiter state or many clients sharing one proxy IP while the backend is idle. Compare limiter and backend counters before restarting a worker.
- If a suspected deploy or proxy caused timeouts, compare the symptom before and after the change and inspect the outermost hop. Use sequential direct-versus-proxy probes from a relevant region; parallel bursts can create misleading client failures.

## Targeted helpers

The scripts in `scripts/` query production Tinybird through the repository's read-only helper. They accept bounded numeric windows and should be run from the repository root:

```bash
.claude/skills/model-debugging/scripts/find-402-users.sh 24 10
.claude/skills/model-debugging/scripts/find-403-users.sh 24 10
.claude/skills/model-debugging/scripts/find-500-errors.sh 24
.claude/skills/model-debugging/scripts/check-user-errors.sh USER_ID 24
```

These reports contain user identifiers and error details. Inspect only the rows needed for the task and keep sensitive values out of shared output.

Secret changes and production deployments follow the approval and CI rules in `AGENTS.md`; an incident diagnosis does not authorize either operation.
Files in this package (6)
  • SKILL.md 5 KB
  • scripts/check-user-errors.sh 1 KB
  • scripts/find-402-users.sh 1 KB
  • scripts/find-403-users.sh 1 KB
  • scripts/find-500-errors.sh 1 KB
  • scripts/tinybird-query.sh 1 KB

Versions

The database has no other skills named model-debugging.

Database snapshot: 13.11.2026 · package version 11b8ef2c983a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pollinations-support-triage
    Investigate Pollinations support email against production code, D1, Tinybird and Stripe; review one case at a time with a branded HTML preview and English translation. Use for email support, not GitHub triage or posting.
  • 90tinybird-cli-guidelines
    Tinybird CLI commands, workflows, and operations. Use when running tb commands, managing local development, deploying, or working with data operations.
  • 100model-management
    Add, update, rename, reroute, price, or remove Pollinations text, image, video, audio, embeddings, realtime, OCR, SVG, and 3D models. Use for model research, provider changes, capability or public-endpoint edits, and model PRs.
  • 91error-recovery
    Handle errors, timeouts, and failures in multi-agent workflows. Use when dealing with external model timeouts, API failures, partial success, user cancellation, or graceful degradation.
  • 100tinybird
    Build real-time analytics APIs with Tinybird — ingest millions of events and query with SQL over HTTP. Use when someone asks to "build analytics API", "Tinybird", "real-time analytics", "event analytics", "ClickHouse as a service", "usage metering", or "product analytics…
  • 100polli
    Generate images, text, audio, video, and transcribe speech via the Pollinations API using the polli CLI. Use when asked to generate media, call pollinations.ai, check pollen balance, list models, manage API keys, inspect quests, manage agents or my-models, publish a static site,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.