klingai-install-auth
Set up Kling AI API authentication with JWT tokens. Use when starting a new Kling AI integration or troubleshooting auth issues. Trigger with phrases like 'kling ai setup', 'klingai api key', 'kling ai authentication', 'configure klingai'.
85
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with clear 'what' and 'when' clauses, explicit trigger phrases, and a distinct niche. Its main weakness is that the capability description could be more specific about what concrete actions it performs beyond 'set up authentication' (e.g., generating JWT tokens, configuring API keys, handling token refresh). Overall it's a solid description that would perform well in skill selection.
Suggestions
Expand the capability list with more specific actions, e.g., 'Generate JWT tokens, configure API credentials, handle token refresh, and resolve common authentication errors for Kling AI API.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI API) and a specific action (JWT token authentication setup), but doesn't list multiple concrete actions beyond setup and troubleshooting. It's more than vague but not comprehensively listing specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up Kling AI API authentication with JWT tokens) and 'when' (starting a new Kling AI integration or troubleshooting auth issues), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes multiple natural trigger phrases users would say: 'kling ai setup', 'klingai api key', 'kling ai authentication', 'configure klingai'. Good coverage of variations including both 'kling ai' and 'klingai' spellings. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI API authentication specifically. The combination of 'Kling AI', 'JWT tokens', and 'API authentication' makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with executable code examples in multiple languages and a clear step-by-step workflow including verification. Its main weakness is moderate verbosity — the JWT explanation in the overview and the full token management class inflate the token count. The content would benefit from splitting advanced patterns into separate files.
Suggestions
Remove the JWT explanation from the Overview — Claude knows what JWT is. Just state: 'Kling AI authenticates via JWT Bearer tokens (30 min expiry) generated from AK/SK credentials.'
Consider moving the Token Management Pattern and Error Handling table into a separate referenced file (e.g., ADVANCED.md) to keep the main skill lean and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements. The Overview explains what JWT is and how it works, which Claude already knows. The Token Management Pattern section adds significant length. However, most content is code-focused and practical. | 2 / 3 |
Actionability | Fully executable code examples in both Python and Node.js, complete with environment variable handling, copy-paste ready .env format, a verification step, and a production-ready token management class. Every step has concrete, runnable code. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (Get Credentials → Generate Token → Verify Authentication) with an explicit verification step in Step 3 that checks response codes and provides diagnostic output. The error handling table serves as a troubleshooting feedback loop. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat long for a single file with no bundle. The Token Management Pattern and Error Handling sections could be split into referenced files. The Resources section provides external links but no internal file references for advanced content. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
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.