klingai-known-pitfalls
Avoid common mistakes when using Kling AI API. Use when troubleshooting or learning best practices. Trigger with phrases like ''klingai pitfalls'', ''kling ai mistakes'', ''klingai gotchas'', ''klingai best practices''. '
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill klingai-known-pitfalls --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Kling AI Known Pitfalls ## Overview Documented mistakes, gotchas, and anti-patterns from real Kling AI integrations. Each pitfall includes the symptom, root cause, and tested fix. ## Pitfall 1: Duration as Integer **Symptom:** `400 Bad Request` on valid-looking requests. ```python # WRONG -- duration as integer {"duration": 5} # CORRECT -- duration as string {"duration": "5"} ``` The API require
What does the klingai-known-pitfalls skill do?
Avoid common mistakes when using Kling AI API. Use when troubleshooting or learning best practices. Trigger with phrases like ''klingai pitfalls'', ''kling ai mistakes'', ''klingai gotchas'', ''klingai best practices''. '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill klingai-known-pitfalls --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
