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
Pending
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 solid skill description that clearly identifies its niche (Kling AI API authentication), provides explicit 'Use when' guidance, and includes well-chosen trigger phrases with spelling variations. The 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).
Suggestions
Expand the 'what' portion with more specific actions, e.g., 'Generate JWT tokens from access key and secret, configure API endpoints, handle token expiration and refresh' to improve specificity.
| 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 actually 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 trigger terms are highly distinctive and unlikely to conflict with other skills due to the specific product name and authentication focus. | 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 and a clear multi-step workflow including verification. Its main weakness is moderate verbosity — it explains concepts Claude already knows (JWT basics, security best practices) and includes all content inline rather than splitting advanced patterns into separate files. The dual-language support and error handling table are strong practical additions.
Suggestions
Remove the JWT explanation in the overview ('Kling AI uses JWT...') — Claude knows what JWTs are. Just state the key facts: 30-min expiry, Bearer token, base URL.
Trim or remove the Security Checklist — these are generic best practices Claude already knows (don't commit secrets, use .gitignore, rotate keys).
Consider moving the Token Management Pattern to a separate reference file (e.g., KLING_AUTH_PATTERNS.md) and linking to it, keeping SKILL.md focused on the core setup flow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary elements. The overview paragraph explaining what JWT is and how Bearer tokens work is knowledge Claude already has. The security checklist contains generic advice (don't commit secrets, use .gitignore) that Claude knows. The Token Management Pattern class, while useful, adds significant length for what could be a brief reference. | 2 / 3 |
Actionability | Fully executable code examples in both Python and Node.js, with complete import statements, environment variable usage, and copy-paste ready functions. The verification step provides concrete code to test authentication, and the error handling table maps specific errors to specific fixes. | 3 / 3 |
Workflow Clarity | Clear 3-step sequence (Get Credentials → Generate Token → Verify Authentication) with an explicit verification step that checks response codes and provides diagnostic output. The workflow includes a feedback loop via the error handling table that maps failures to fixes, and the token management pattern addresses the ongoing concern of token expiry. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but it's somewhat monolithic — the Token Management Pattern and both language implementations could potentially be split into separate reference files. The Resources section at the end provides external links but the skill itself contains everything inline rather than using progressive disclosure for advanced patterns. | 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
70e9fa4
- 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.