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'.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-known-pitfalls/SKILL.mdSecurity
1 high severity finding. You should review these findings carefully before considering using this skill.
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
I scanned all files for literal credentials. The only direct credential-like literal is API_KEY = "klingai_sk_1234567890" in references/common-pitfalls.md. This is a concrete API key string (not a placeholder like YOUR_API_KEY or sk-xxxx), so it matches the definition of a hardcoded API key and should be flagged. Other values (environment variable names like KLINGAI_API_KEY, the JWT variable names, emails, URLs, and simple example passwords) are documentation placeholders or non-secret values and are ignored.
- Commit
8585d6d
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.