klingai-cost-controls
Implement cost controls and budget management for Kling AI. Use when managing spending limits, tracking costs, or preventing budget overruns. Trigger with phrases like 'klingai cost', 'kling ai budget', 'klingai spending', 'video generation costs'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-cost-controls63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 with excellent trigger terms and completeness. The main weakness is that the capabilities could be more specific - listing concrete actions like 'set spending caps', 'generate cost reports', or 'configure budget alerts' would strengthen the specificity dimension.
Suggestions
Add 2-3 more concrete actions to the capabilities section, such as 'set spending caps, generate cost reports, configure budget alerts' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (cost controls, budget management for Kling AI) and mentions some actions (managing spending limits, tracking costs, preventing budget overruns), but doesn't list multiple concrete specific actions like 'set daily limits', 'view cost reports', or 'configure alerts'. | 2 / 3 |
Completeness | Clearly answers both what (implement cost controls and budget management) and when (managing spending limits, tracking costs, preventing budget overruns) with explicit trigger phrases provided in a 'Trigger with phrases like' clause. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural trigger terms users would say: 'klingai cost', 'kling ai budget', 'klingai spending', 'video generation costs'. These are realistic phrases a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining Kling AI with cost/budget management. The explicit product name 'Kling AI' combined with cost-specific triggers makes it highly unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a skeleton or placeholder rather than actionable guidance. It lists what should be done at a very high level but provides no concrete implementation details, code examples, or specific instructions for implementing cost controls. The content fails to teach Claude anything it couldn't infer from the topic name alone.
Suggestions
Add executable Python code examples for tracking API usage costs, such as a CostTracker class with methods for logging requests and calculating cumulative spend
Include specific budget enforcement logic with concrete thresholds and hard-stop implementations (e.g., raising exceptions when budget exceeded)
Provide actual Kling AI pricing numbers or a pricing lookup mechanism so Claude can calculate real costs
Add validation checkpoints in the workflow, such as 'check remaining budget before each API call' with specific code patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary filler like 'This skill teaches how to' and generic prerequisites. The instructions are high-level summaries rather than actionable content, which wastes tokens without providing value. | 2 / 3 |
Actionability | The skill provides only vague, abstract guidance with no concrete code, commands, or specific implementation details. Steps like 'Understand Pricing' and 'Set Budgets' describe rather than instruct, with no executable examples for cost tracking or budget enforcement. | 1 / 3 |
Workflow Clarity | The five steps are extremely high-level labels without any actual sequence, validation checkpoints, or implementation details. For a cost control system that could prevent budget overruns, there are no concrete validation steps or feedback loops. | 1 / 3 |
Progressive Disclosure | The skill does reference external files for errors and examples, which is appropriate structure. However, the main content is so thin that it's essentially just a table of contents with no substantive overview content to orient the reader. | 2 / 3 |
Total | 6 / 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 | |
- 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.