klingai-team-setup

Configure Kling AI for teams with per-project API keys, usage quotas, and role-based access. Trigger with phrases like 'klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access'.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-team-setup/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides concrete, executable code for team-based Kling AI access control, which is its primary strength. However, it lacks a clear step-by-step setup workflow with validation checkpoints, and the content is somewhat verbose with full class implementations inline rather than referenced. The skill would benefit from a sequential 'getting started' flow and splitting detailed implementations into supporting files.

Suggestions

Add a numbered setup workflow at the top (e.g., 1. Create API keys → 2. Configure team → 3. Test credentials → 4. Deploy quota manager) with explicit validation steps like verifying API key connectivity.

Move the full TeamQuotaManager and TeamKlingClient implementations into a separate reference file and keep only usage examples inline in SKILL.md.

Add a validation/verification step after secrets configuration to confirm credentials are correctly loaded before proceeding to quota setup.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary verbosity—full class definitions with docstrings and dataclass boilerplate that could be trimmed. The secrets management table is useful but the overall content is longer than needed for what it teaches.	2 / 3
Actionability	The skill provides fully executable Python code for team configuration, quota management, and access control wrappers, along with concrete CLI commands for secrets management across multiple platforms. Code is copy-paste ready.	3 / 3
Workflow Clarity	The skill presents components (config, quotas, secrets, client wrapper) but lacks a clear sequential workflow showing how to set up a team from scratch. There are no explicit validation checkpoints—e.g., no step to verify API keys work, no guidance on testing quota enforcement before going live.	2 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, but it's a monolithic file with substantial inline code that could benefit from being split into separate reference files (e.g., quota manager implementation, secrets management guide). No bundle files exist to offload detail.	2 / 3
	Total	9 / 12 Passed

Description

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 team configuration) and provides explicit trigger phrases. The main weakness is that the capabilities could be more specific with concrete actions rather than feature categories. Overall it performs well on completeness and distinctiveness.

Suggestions

Make capabilities more concrete by listing specific actions, e.g., 'Create and manage per-project API keys, set and enforce usage quotas, assign role-based access permissions' instead of just listing feature areas.

Dimension	Reasoning	Score
Specificity	Names the domain (Kling AI team configuration) and some actions (per-project API keys, usage quotas, role-based access), but these are more like feature areas than concrete, specific actions. It doesn't list step-by-step operations like 'create API keys', 'set quota limits', 'assign roles'.	2 / 3
Completeness	Clearly answers both 'what' (configure Kling AI for teams with per-project API keys, usage quotas, and role-based access) and 'when' (explicit trigger phrases provided). The 'Trigger with phrases like...' clause serves as an explicit 'Use when' equivalent.	3 / 3
Trigger Term Quality	Includes natural trigger phrases like 'klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access' which cover multiple variations a user might say. Good coverage of relevant terms including both 'klingai' and 'kling ai' spellings.	3 / 3
Distinctiveness Conflict Risk	Very specific niche: Kling AI team/organization configuration. The combination of 'Kling AI' + 'team/organization/multi-user' makes it highly unlikely to conflict with other skills, including a general Kling AI skill.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.