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'.
68
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 two languages, a clear step-by-step workflow with verification, and useful error handling guidance. Its main weakness is moderate verbosity — explaining JWT concepts Claude already knows and including general security advice that doesn't add unique value. The content could be tightened by about 20-30% without losing any actionable information.
Suggestions
Remove the JWT explanation in the Overview ('Kling AI uses JWT...Tokens expire after 30 minutes') and trim to just the base URL and key facts Claude wouldn't know.
Trim the Security Checklist to Kling-specific items only (e.g., 'exp ceiling of 1800s enforced by Kling') — general secrets management advice is already known to Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements. The Overview section explains what JWT is and how it works, which Claude already knows. The Token Management Pattern section, while useful, adds significant length. The security checklist contains general best practices Claude would already know (e.g., 'never commit secrets to version control'). | 2 / 3 |
Actionability | Excellent actionability — provides fully executable Python and Node.js code for JWT generation, a complete verification script, and a production-ready auto-refreshing token manager class. All code is copy-paste ready with proper imports and environment variable usage. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (Get Credentials → Generate Token → Verify Authentication) with an explicit verification step that checks status codes and provides diagnostic output. The error handling table serves as a troubleshooting feedback loop, and the token management pattern addresses the refresh lifecycle. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical progression, but it's somewhat monolithic for its length (~120 lines of substantive content). The Token Management Pattern and Error Handling sections could potentially be split into referenced files, though without bundle files this is a minor concern. The Resources section provides external links but no internal file references. | 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
8a9cd04
- 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.