klingai-team-setup
Configure Kling AI for team and organization use. Use when setting up shared access, managing team API keys, or organizing projects. Trigger with phrases like 'klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-team-setup64
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 that clearly defines its scope (Kling AI team configuration) and provides explicit trigger guidance. The main weakness is that the specific actions could be more concrete (e.g., 'create team workspaces', 'assign role-based permissions') rather than general administrative terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI configuration) and some actions ('setting up shared access', 'managing team API keys', 'organizing projects'), but these are somewhat general administrative tasks rather than highly specific concrete actions. | 2 / 3 |
Completeness | Clearly answers both what ('Configure Kling AI for team and organization use') and when ('Use when setting up shared access, managing team API keys, or organizing projects') with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms: 'klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access'. These are variations users would naturally say when needing team/org configuration. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI team/organization configuration specifically. The explicit product name and team-focused scope make it unlikely to conflict with other skills. | 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 structural outline for team setup but lacks the concrete, executable guidance needed to be useful. It reads more like a table of contents than actionable instructions, with all substantive content deferred to external references. The absence of any actual commands, API calls, or configuration examples makes it impossible for Claude to execute these tasks without additional information.
Suggestions
Add concrete API calls or CLI commands for each step (e.g., actual curl commands for creating API keys, JSON configuration examples for role definitions)
Include at least one complete, executable example inline showing the full team setup workflow with real configuration values
Add validation checkpoints after key steps (e.g., 'Verify API key works: curl -H "Authorization: Bearer $KEY" https://api.klingai.com/v1/whoami')
Move the quick-start essentials into the main skill rather than deferring everything to external references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief but includes some unnecessary padding like 'Understanding of RBAC concepts' prerequisite and generic output descriptions that don't add value. The overview sentence restates what the title already conveys. | 2 / 3 |
Actionability | Provides only vague, abstract steps with no concrete code, commands, or specific instructions. 'Create Organization' and 'Generate API Keys' describe tasks without showing how to actually do them - no API calls, CLI commands, or configuration examples. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence but lack any validation checkpoints or feedback loops. For operations involving API key management and access controls, there should be verification steps to confirm configurations are correct before proceeding. | 2 / 3 |
Progressive Disclosure | References external files for errors and examples (one level deep), but the main content is too thin - it defers almost all useful content to other files while providing no actionable quick-start material in the skill itself. | 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 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.