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

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

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 strongly actionable with executable code, but it inlines full implementations that duplicate existing reference files and never links to them, hurting both conciseness and progressive disclosure. It also lacks a sequenced setup workflow with validation checkpoints.

Suggestions

Replace the inline TeamConfig/example-team and TeamKlingClient blocks with brief overviews that link to team-configuration.md, example-team-config.md, and api-key-wrapper-with-team-context.md so the SKILL.md body stays an overview.

Add a numbered 'Setup workflow' section (create per-environment keys -> load secrets -> configure team -> deploy wrapper -> verify a test call enforces a quota) with an explicit validation/verification checkpoint.

Reference errors.md near the quota manager so the documented error-handling reference is discoverable from the body.

Dimension	Reasoning	Score
Conciseness	Prose is lean with no conceptual fluff, but ~80 lines of inline code (full dataclasses, an example team, the quota manager, and the wrapper) duplicate content that exists in dedicated reference files, so it could be tightened; not level 3 because not every token earns its place.	2 / 3
Actionability	Provides fully executable Python (dataclasses, TeamQuotaManager, boto3 credential loader, TeamKlingClient wrapper) plus concrete shell commands for secret stores — copy-paste ready, not pseudocode.	3 / 3
Workflow Clarity	Content is organized into topical sections with runtime validation inside authorize(), but there is no sequenced team-setup workflow with explicit validation checkpoints; the quota/batch operations cap it at 2 rather than the level 3 'explicit validate -> fix -> retry' pattern.	2 / 3
Progressive Disclosure	Five reference files exist (team-configuration.md, example-team-config.md, examples.md, errors.md, api-key-wrapper-with-team-context.md) but none are linked from the body, and their content is inlined instead; this fits the level 2 'content that should be separate is inline, references not clearly signaled' anchor rather than the well-signaled level 3.	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 concise, concrete, and third-person, with explicit trigger guidance that answers both what the skill does and when to use it. It is a strong, well-scoped description with no obvious weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'per-project API keys, usage quotas, and role-based access' — matching the 'Lists multiple specific concrete actions' anchor rather than the domain-only level 2.	3 / 3
Completeness	Explicitly answers both what ('Configure Kling AI for teams with per-project API keys, usage quotas, and role-based access') and when ('Trigger with phrases like...'), satisfying the level 3 anchor; not capped at 2 because the 'Use when'/trigger guidance is present.	3 / 3
Trigger Term Quality	Provides four natural trigger phrases ('klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access') that a user would plausibly say, giving good coverage rather than the partial level 2.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Kling-AI-specific team niche with distinct triggers, making conflict with other skills unlikely; far more specific than the level 2 'could still overlap' anchor.	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
Path: plugins/saas-packs/klingai-pack/skills/klingai-team-setup/SKILL.md
Commit: b2e8c53

Reviewed: 5 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.