Przejdź do treści
Biblioteka skilli
AI i agenci · Analiza

klingai-common-errors

/klingai-common-errors

Diagnozuje i naprawia typowe błędy API Kling AI, przy nieudanym generowaniu wideo i problemach z API.

Licencja
MIT
Ostatnia zmiana repozytorium
26.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
3
Przestarzałość

Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Diagnozuje i naprawia typowe błędy API Kling AI, przy nieudanym generowaniu wideo i problemach z API.

Wyzwalacze z opisu

kling ai errorklingai not workingfix klingaiklingai failed
Oryginalny opis (EN)

Diagnose and fix common Kling AI API errors. Use when troubleshooting failed video generation or API issues. Trigger with phrases like ''kling ai error'', ''klingai not working'', ''fix klingai'', ''klingai failed''.

Jak działa

  1. Overview
  2. HTTP Error Codes
  3. Task-Level Failures
  4. JWT Authentication Errors
  5. Rate Limit Handling
  6. Diagnostic Checklist
  7. Debug Logging
  8. Prerequisites
  9. Instructions
  10. Output
Sekcje z nagłówków SKILL.md, w oryginale · 160 linii, 864 słów
Podgląd SKILL.md
---
name: klingai-common-errors
description: 'Diagnose and fix common Kling AI API errors. Use when troubleshooting
  failed video generation

  or API issues. Trigger with phrases like ''kling ai error'', ''klingai not working'',
  ''fix klingai'',

  ''klingai failed''.

  '
allowed-tools: Read, Write, Edit, Bash(npm:*), Grep
version: 1.18.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- kling-ai
- debugging
- errors
compatibility: Designed for Claude Code
---
# Kling AI Common Errors

## Overview

Complete error reference for the Kling AI API. Covers HTTP status codes, task-level failures, JWT issues, and generation-specific problems with tested solutions.

## HTTP Error Codes

| Code | Error | Cause | Solution |
|------|-------|-------|----------|
| `400` | Bad Request | Invalid parameters, malformed JSON | Validate all required fields; check `model_name` is valid |
| `401` | Unauthorized | Invalid/expired JWT token | Regenerate JWT; verify AK/SK; check `exp` claim |
| `402` | Payment Required | Insufficient credits | Top up API resource pack or subscription |
| `403` | Forbidden | Content policy violation or API disabled | Review prompt against content policy; enable API access |
| `404` | Not Found | Invalid task_id or wrong endpoint | Verify task_id; check endpoint path spelling |
| `429` | Too Many Requests | Rate limit exceeded | Implement exponential backoff (see pattern below) |
| `500` | Internal Server Error | Kling platform issue | Retry after 30s; if persistent, check status page |
| `502` | Bad Gateway | Upstream service unavailable | Retry with backoff; typically transient |
| `503` | Service Unavailable | System maintenance | Wait and retry; check announcements |

## Task-Level Failures

When HTTP returns `200` but `task_status` is `"failed"`:

| `task_status_msg` | Cause | Solution |
|-------------------|-------|----------|
| Content policy violation | Prompt contains restricted content | Remove violent, adult, or copyrighted references |
| Image quality too low | Source image is blurry or too small | Use image >= 300x300px, clear and sharp |
| Prompt too complex | Too many scene elements | Simplify to 1-2 subjects, clear action |
| Generation timeout | Internal processing exceeded limit | Retry; reduce duration from 10s to 5s |
| Invalid image format | Unsupported file type | Use JPG, PNG, or WebP |
| Mask dimension mismatch | Mask size differs from source | Ensure mask matches source image dimensions exactly |

## JWT Authentication Errors

### Problem: `401` on every request

```python
# WRONG — missing headers parameter
token = jwt.encode(payload, sk, algorithm="HS256")

# CORRECT — include explicit headers
token = jwt.encode(payload, sk, algorithm="HS256",
                   headers={"alg": "HS256", "typ": "JWT"})
```

### Problem: Token works then fails after 30 min

```python
# WRONG — token generated once at import time
TOKEN = generate_token()

# CORRECT — refresh before expiry
class TokenManager:
    def __init__(self, ak, sk):
        self.ak, self.sk = ak, sk
        self._token = None
        self._exp = 0

    @property
    def token(self):
        if time.time() >= self._exp - 300:  # 5 min buffer
            payload = {"iss": self.ak, "exp": int(time.time()) + 1800,
                       "nbf": int(time.time()) - 5}
            self._token = jwt.encode(payload, self.sk, algorithm="HS256",
                                     headers={"alg": "HS256", "typ": "JWT"})
            self._exp = int(time.time()) + 1800
        return self._token
```

## Rate Limit Handling

```python
import time
import requests

def request_with_backoff(method, url, headers, json=None, max_retries=5):
    """Retry with exponential backoff on 429 and 5xx errors."""
    for attempt in range(max_retries):
        response = method(url, headers=headers, json=json)

        if response.status_code == 429:
            retry_after = int(response.headers.get("Retry-After", 2 ** attempt))
            print(f"Rate limited. Retrying in {retry_after}s...")
            time.sleep(retry_after)
            continue
        elif response.status_code >= 500:
            wait = 2 ** attempt
            print(f"Server error {response.status_code}. Retrying in {wait}s...")
            time.sleep(wait)
            continue

        response.raise_for_status()
        return response

    raise RuntimeError(f"Max retries ({max_retries}) exceeded")
```

## Diagnostic Checklist

When a generation fails, check in order:

1. **Auth valid?** — Test with a simple GET request first
2. **Credits available?** — Check balance in developer console
3. **Model valid?** — Verify `model_name` matches catalog exactly
4. **Parameters valid?** — `duration` must be `"5"` or `"10"` (string, not int)
5. **Prompt clean?** — Remove special characters, keep under 2500 chars
6. **Image accessible?** — For I2V, verify image URL is publicly accessible
7. **Feature exclusivity?** — `image_tail`, `dynamic_masks`, and `camera_control` are mutually exclusive

## Debug Logging

```python
import logging

logging.basicConfig(level=logging.DEBUG)
logger = logging.getLogger("kling")

def debug_request(method, url, headers, json=None):
    """Log request/response for debugging."""
    logger.debug(f"→ {method.__name__.upper()} {url}")
    logger.debug(f"→ Body: {json}")
    r = method(url, headers=headers, json=json)
    logger.debug(f"← Status: {r.status_code}")
    logger.debug(f"← Body: {r.text[:500]}")
    return r
```

## Prerequisites

- A sandbox workspace, synthetic or rights-cleared diagnostic brief, secret references, approved scope, redaction rules, draft-only destination, and incident owner.

## Instructions

1. Reproduce errors with sandbox fixtures only; do not log authorization headers, prompts, source assets, response bodies, or generated asset URLs.
2. Capture aggregate status, error class, credit use, policy/rights outcome, and task state while verifying redaction and retention controls.
3. Halt the canary and remove temporary drafts on scope, policy, rights, budget, or retention drift; revoke temporary access where appropriate.
4. Store a redacted diagnostic receipt for the approved window and restore the known-good configuration before resuming work.

## Output

Produce an error-triage receipt with environment, fixture classification, error class, aggregate status/credit signal, policy/rights/draft-only checks, incident owner, cleanup proof, and rollback reference. Exclude prompts, assets, identities, and credentials.

## Error Handling

| Condition | Response |
|---|---|
| Sensitive material appears in diagnostics | Stop collection, delete the artifact, correct redaction, and rotate/revoke access as needed. |
| Policy, rights, budget, or retention drift | Cancel tasks, remove drafts, and require owner review before retrying. |

## Examples

`env=ci-sandbox; error=429; retries=backoff; budget=within-cap; policy=pass; destination=draft-only; cleanup=verified` is a valid triage record.

## Resources

- [API Reference](https://app.klingai.com/global/dev/document-api/apiReference/model/textToVideo)
- [Content Policy](https://app.klingai.com/global/dev/document-api/protocols/paidServiceProtocol)
- [Developer Portal](https://app.klingai.com/global/dev)
Pliki w paczce (2)
  • SKILL.md 7 KB
  • references/error-codes.md 5 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.

Migawka bazy z 28.10.2026 · wersja paczki 9997c0aa0ff8 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100klingai-known-pitfalls
    Opisuje typowe błędy przy pracy z API Kling AI i dobre praktyki, które pozwalają ich unikać.
  • 100klingai-debug-bundle
    Ustawia logowanie i debugowanie integracji z API Kling AI, przy rozwiązywaniu problemów z generowaniem wideo i budowie obserwowalności.
  • 100klingai-install-auth
    Konfiguruje uwierzytelnianie API Kling AI i klucze API przy starcie nowej integracji lub naprawie problemów z autoryzacją.
  • 100klingai-model-catalog
    Przedstawia modele Kling AI i ich możliwości w generowaniu wideo, pomocne przy wyborze modelu i poznawaniu funkcji.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.