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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is highly actionable with executable code, but it is held back by inlining detail that duplicates unreferenced bundle files and by the absence of an explicit validated workflow. Organization into sections is reasonable, yet navigation to the reference files is missing.

Suggestions

Link the existing reference files (team-configuration.md, api-key-wrapper-with-team-context.md, example-team-config.md, errors.md) from the body instead of inlining duplicate implementations — the body and references currently define conflicting role models and quota fields.

Add an explicit numbered setup workflow with validation checkpoints (e.g., verify the config loads, run a low-credit test generation before going live) since credential and quota configuration is a risky operation.

Trim the inline Python class definitions and move detailed implementations into the references so SKILL.md stays a lean overview pointing one level deep to the bundle.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence with no condescending concept explanations, but it inlines several full Python class definitions that duplicate material in the reference files and could be tightened by offloading detail.	2 / 3
Actionability	It provides fully executable Python classes, concrete .env snippets, and real secret-manager commands (aws/gcp/vault/op) that are copy-paste ready and specific.	3 / 3
Workflow Clarity	Sections imply a topical order (keys → team config → quotas → secrets → wrapper) but there is no explicit numbered procedure and no validation/verification checkpoint for this risky credential-and-quota setup.	2 / 3
Progressive Disclosure	Five reference files exist but none are linked from the body, and large implementations are inlined that overlap (even conflict) with those references — content that should be separate is inline and references are not signaled.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, action-oriented, and pairs a clear capability statement with explicit natural-language triggers. It avoids verbosity and generic fluff while remaining distinct from other skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — "per-project API keys, usage quotas, and role-based access" — naming specific actions rather than vague language.	3 / 3
Completeness	It states what the skill does (configure team access) and gives an explicit "Trigger with phrases like..." clause equivalent to a "Use when" trigger, answering both what and when.	3 / 3
Trigger Term Quality	Trigger phrases "klingai team", "kling ai organization", "klingai multi-user", and "shared klingai access" are natural terms a user would plausibly say, with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Kling AI team/multi-user setup is a narrow niche with distinct Kling-specific triggers, making conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 1 day 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.