klingai-team-setup

Name: klingai-team-setup
Rating: 64 (1 reviews)
Author: jeremylongshore

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-team-setup

github.com/jeremylongshore/claude-code-plugins-plus-skills

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'.

Review Score

64%

Validation Score

13/16

Implementation Score

35%

Activation Score

90%

SKILL.md

Review

Evals

Generated

12 days ago

Warnings & errors only

Criteria	Score
allowed_tools_field	'allowed-tools' contains unusual tool name(s)
metadata_version	'metadata' field is not a dictionary
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata

Overall Assessment

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	Score	Reasoning
Conciseness	2/3	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.
Actionability	1/3	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.
Workflow Clarity	2/3	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.
Progressive Disclosure	2/3	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.

Overall Assessment

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	Score	Reasoning
Specificity	2/3	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.
Completeness	3/3	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.
Trigger Term Quality	3/3	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.
Distinctiveness Conflict Risk	3/3	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.