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'.
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/klingai-pack/skills/klingai-team-setup/SKILL.mdQuality
Discovery
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 capability descriptions are somewhat high-level feature areas rather than concrete actions. Overall it performs well for skill selection purposes.
Suggestions
Make capabilities more concrete by listing specific actions, e.g., 'Create and manage per-project API keys, set and enforce usage quotas, assign user roles and permissions'.
| 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 explicit trigger phrases like 'klingai team', 'kling ai organization', 'klingai multi-user', 'shared klingai access' which are natural terms users would say when needing team configuration for Kling AI. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Kling AI team/organization configuration. The trigger terms are highly specific to this particular tool and use case, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
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 solid, actionable code examples for team-based Kling AI configuration with good coverage of quotas, secrets management, and access control. However, it lacks a clear end-to-end workflow sequence with validation steps, and the lengthy inline code blocks could be better organized through progressive disclosure into supporting files. The content is moderately concise but could trim some boilerplate that Claude could generate independently.
Suggestions
Add a numbered setup workflow at the top (e.g., 1. Create API keys → 2. Configure team → 3. Set up quota manager → 4. Verify with test call) with explicit validation checkpoints.
Extract the full TeamQuotaManager and TeamKlingClient implementations into a separate reference file, keeping only usage examples inline in SKILL.md.
Add a verification step showing how to confirm the setup works (e.g., a test call with expected output or a quota report check).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary verbosity—the full dataclass definitions and quota manager class are quite lengthy. The secrets management table is useful but the overall content could be tightened, especially since Claude would know how to structure dataclasses and defaultdicts. | 2 / 3 |
Actionability | The skill provides fully executable Python code for team configuration, quota management, secrets retrieval, and an access control wrapper. The env file examples, CLI commands for secrets managers, and concrete team member configurations are all copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill presents components (config, quotas, secrets, wrapper) but lacks a clear sequential workflow tying them together. There's no explicit setup sequence (e.g., 'Step 1: Create keys, Step 2: Configure team, Step 3: Set up quotas') and no validation checkpoints for verifying the setup works correctly. | 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 code, secrets management details). No bundle files are provided to offload detailed implementations. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
- Commit
d41e58e
- Reviewed
Table of Contents
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.