CtrlK
BlogDocsLog inGet started
Tessl Logo

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'.

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 content is highly actionable with executable code and accurate pricing tables, but it duplicates bundled reference material inline rather than progressively disclosing it, and lacks an explicit validated workflow for batch/destructive cost operations.

Suggestions

Replace the inlined BudgetGuard/UsageTracker classes with a concise overview and links to references/cost-tracker-class.md and references/budget-enforcing-wrapper.md so the body stays lean and references are actually signaled.

Add an explicit numbered workflow (estimate → pre-batch check → call → record → verify against usage_report) with a validation/retry checkpoint for batch submissions, which would lift workflow_clarity to 3.

Flesh out references/examples.md and references/errors.md with real worked examples and error-resolution steps rather than one-line placeholders, so the progressive-disclosure split earns its place.

DimensionReasoningScore

Conciseness

The body is mostly efficient code and tables, but it inlines four full Python classes (BudgetGuard, pre_batch_check, CostAwareKlingClient, UsageTracker) totaling ~150 lines that largely overlap with the bundled references, padding the SKILL.md beyond what the overview should carry.

2 / 3

Actionability

Provides fully executable, copy-paste-ready Python code with real credit tables, concrete budget enforcement, batch estimation, and usage logging — specific and complete rather than pseudocode.

3 / 3

Workflow Clarity

The cost-aware client and pre-batch check imply a sequence (estimate → check → call → record), but there is no explicit numbered workflow or validation/retry feedback loop for the batch operation, which the rubric caps at 2.

2 / 3

Progressive Disclosure

Four reference files exist (budget-enforcing-wrapper, cost-tracker-class, errors, examples), but the body never signals or links to them, instead duplicating their content inline; examples.md and errors.md are weak, making the split structure poorly navigated.

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 strong: third-person voice, concrete capabilities, explicit 'Use when' guidance, and natural trigger phrases. It fully answers what the skill does and when to invoke it with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Implement budget limits, usage alerts, and spending controls' — naming three distinct capabilities rather than vague language.

3 / 3

Completeness

Explicitly answers what ('Implement budget limits, usage alerts, and spending controls') and when ('Use when managing costs or preventing overruns. Trigger with phrases like...') with explicit triggers.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say ('klingai cost', 'kling ai budget', 'klingai spending limit', 'video generation costs') with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clear niche scoped to Kling AI cost control with distinctive triggers, unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.