klingai-cost-controls
Implement budget limits, usage alerts, and spending controls for Kling AI. Use when managing costs or preventing overruns. Trigger with phrases like 'klingai cost', 'kling ai budget', 'klingai spending limit', 'video generation costs'.
80
77%
Does it follow best practices?
Impact
Pending
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-cost-controls/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 (cost management for Kling AI), provides explicit trigger terms, and answers both what and when. The main weakness is that the capability actions could be more specific—listing concrete operations rather than general categories like 'budget limits' and 'spending controls'.
Suggestions
Make capabilities more concrete by specifying exact actions, e.g., 'Set daily/monthly spending caps, configure usage threshold alerts, track per-video generation costs, and pause generation when budgets are exceeded.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI budget management) and some actions ('budget limits, usage alerts, spending controls'), but these are somewhat generic financial management terms rather than deeply specific concrete actions like 'set daily spending caps' or 'configure email alerts at threshold percentages'. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement budget limits, usage alerts, spending controls for Kling AI) and 'when' (managing costs, preventing overruns) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes good natural trigger terms: 'klingai cost', 'kling ai budget', 'klingai spending limit', 'video generation costs'. These cover variations of the product name and common cost-related phrases a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Kling AI' combined with cost/budget management. Unlikely to conflict with other skills unless there are multiple Kling AI skills, and even then the budget/cost focus narrows it well. | 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.
This is a solid, actionable skill with executable Python code and useful reference tables for Kling AI cost management. Its main weaknesses are the lack of an explicit integration workflow showing how the components fit together in sequence, and some verbosity in utility classes that Claude could easily generate. The optimization strategies table is a standout for its conciseness and practical value.
Suggestions
Add a 'Quick Start' or 'Integration Workflow' section showing the numbered sequence: initialize BudgetGuard → wrap client with CostAwareKlingClient → run pre-batch check → generate → review usage report
Trim the UsageTracker class to a brief description or a few-line snippet, as structured JSONL logging is something Claude can generate without detailed guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with useful tables and executable code, but some classes are verbose (e.g., UsageTracker is straightforward logging that Claude could generate on its own). The BudgetGuard class is fairly long but earns most of its tokens. The optimization strategies table is lean and valuable. | 2 / 3 |
Actionability | All code is fully executable Python with concrete classes, methods, and clear interfaces. The credit cost reference table, BudgetGuard, CostAwareKlingClient, and pre-batch check are all copy-paste ready with specific credit values and thresholds. | 3 / 3 |
Workflow Clarity | The individual components are clear, but there's no explicit end-to-end workflow showing the sequence of steps (e.g., 1. Initialize BudgetGuard, 2. Run pre-batch check, 3. Use CostAwareKlingClient, 4. Review usage). The pre-batch check includes a validation/rejection step, but there's no overall feedback loop or integration sequence documented. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers, but it's a fairly long monolithic file. The credit cost table, optimization strategies, and usage tracking could potentially be split into referenced files. The two resource links at the end are helpful but minimal. | 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
3e83543
- 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.