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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/klingai-pack/skills/klingai-team-setup/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable with complete, runnable code, but it functions as a monolithic inlined reference rather than an overview pointing into the bundle, and it lacks validation checkpoints for its access-control and secrets workflows. Progressive disclosure is the main weakness: existing reference files are neither linked nor leveraged.

Suggestions

Replace the inlined TeamConfig/TeamQuotaManager/TeamKlingClient code with concise overviews and one-level-deep links to the matching reference files (team-configuration.md, api-key-wrapper-with-team-context.md, example-team-config.md) so SKILL.md acts as a navigable index.

Add a short sequenced setup workflow (create env keys → load config → wire quota manager → wrap client) with an explicit validation/verification checkpoint, e.g. confirm credentials resolve and run a test authorize() call before going live.

Wire the errors.md reference into the relevant sections (e.g. link it from the quota/access-control sections) so the provided bundle is discoverable rather than orphaned.

Dimension	Reasoning	Score
Conciseness	Prose is lean (one-sentence Overview, compact tables) and assumes Claude's competence with little padding, but the body inlines several large code blocks that could be tightened by leaning on the existing reference files, keeping it just below the fully lean anchor at 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready code across the common cases — team config dataclasses, quota manager, secrets loading, and an access-control client wrapper — with concrete commands and specific examples.	5 / 5
Workflow Clarity	Sections imply a rough order (keys → config → quotas → secrets → wrapper) but are topical rather than a sequenced workflow, and there are no validation/verification checkpoints for operations involving access control and secrets, which caps the score at 3 per the destructive/batch guidance.	3 / 5
Progressive Disclosure	The body inlines large code blocks that duplicate content in the bundle files (team-configuration.md, api-key-wrapper-with-team-context.md) and the 'Resources' section links only to external URLs, never signaling the reference files — so content that belongs in separate files is inlined and the provided references are effectively orphaned.	2 / 5
	Total	14 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 strong: it concisely states concrete capabilities and provides explicit, varied trigger phrases answering both what and when. The only minor weakness is trigger-term breadth, with a few natural phrasings absent.

Dimension	Reasoning	Score
Specificity	Names the domain (Kling AI for teams) and three concrete capabilities — 'per-project API keys, usage quotas, and role-based access' — which is several specific actions with only minor coverage gaps, falling just short of the comprehensive multi-verb anchor at 5.	4 / 5
Completeness	Explicitly answers both 'what' (configure Kling AI for teams with per-project API keys, quotas, role-based access) and 'when' (concrete 'Trigger with phrases like...' trigger phrases), matching the anchor that requires clear what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	Provides multiple natural trigger phrases ('klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access') with synonym variation, but a few natural terms a user might say are missing, so it sits above the midpoint rather than at the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Kling AI team/multi-user setup) with product-specific triggers, making conflict with unrelated skills minimal and clearly distinguishable.	5 / 5
	Total	18 / 20 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: 8585d6d

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