klingai-install-auth
Execute set up Kling AI API authentication and configure API keys. 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'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-install-auth68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 strong completeness and distinctiveness. It clearly identifies the use case and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more detailed - it mentions 'set up' and 'configure' but doesn't elaborate on what that entails.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI API) and some actions ('set up authentication', 'configure API keys'), but lacks comprehensive detail about what specific configuration steps or capabilities are involved. | 2 / 3 |
Completeness | Clearly answers both what ('set up Kling AI API authentication and configure API keys') and when ('starting a new Kling AI integration or troubleshooting auth issues') with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'kling ai setup', 'klingai api key', 'kling ai authentication', 'configure klingai' - these are phrases users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI specifically, with distinct triggers that are unlikely to conflict with other API setup skills due to the explicit 'kling' and 'klingai' terms. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a high-level outline but lacks the concrete, executable guidance needed for effective authentication setup. The instructions describe what to do conceptually without showing how - no actual code for setting environment variables, no example API requests, and no specific validation commands. The skill defers too much to external references while keeping only abstract steps.
Suggestions
Add executable code examples for setting environment variables (e.g., `export KLING_API_KEY=your_key` and Python/Node.js code to load it)
Include a concrete verification request with expected response format (e.g., a curl command or Python snippet that calls a simple endpoint)
Add specific error indicators and what they mean inline (e.g., '401 = invalid key, 403 = key disabled')
Show the actual API key format or structure so users can validate they copied it correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary padding like the 'Overview' section restating what the skill does, and the prerequisites list basic requirements Claude would know to check. | 2 / 3 |
Actionability | The instructions are vague and abstract - 'Navigate to your account settings > API' and 'Set up your environment variables' provide no concrete code, commands, or specific examples. No executable snippets for setting env vars or making test requests. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack concrete validation checkpoints. 'Verify Setup: Test your authentication with a simple request' doesn't show what that request looks like or how to interpret success/failure. | 2 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present but the main content is too thin - it defers critical actionable content (examples, error handling) to other files while keeping only vague instructions in the main skill. | 2 / 3 |
Total | 7 / 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 | |
- 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.