Understand Kling AI pricing, credits, and cost optimization strategies. Use when budgeting or estimating costs. Trigger with phrases like 'kling ai pricing', 'klingai credits', 'kling ai cost', 'klingai budget'.
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-pricing-basics/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 description with strong trigger terms and clear 'when' guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions it performs (e.g., comparing plans, calculating per-video costs, recommending credit packages). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions like 'compare subscription plans, calculate per-video credit costs, recommend cost-saving strategies' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI pricing/credits/cost optimization) and some actions ('budgeting', 'estimating costs'), but doesn't list multiple concrete actions like comparing plan tiers, calculating credit usage, or recommending subscription levels. | 2 / 3 |
Completeness | Clearly answers both 'what' (understand Kling AI pricing, credits, and cost optimization strategies) and 'when' (use when budgeting or estimating costs), with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'kling ai pricing', 'klingai credits', 'kling ai cost', 'klingai budget'. These cover common variations of how users would phrase cost-related queries about Kling AI. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Kling AI pricing and credits — this is a clear niche that is unlikely to conflict with other skills, as it targets a specific product's cost structure. | 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 reference skill with excellent pricing tables and actionable code examples. Its main weaknesses are that it includes some code patterns Claude could generate independently (BudgetGuard), and it lacks a clear decision workflow for budgeting tasks. The content would benefit from tighter organization and a clearer step-by-step process for cost planning.
Suggestions
Add a brief decision workflow at the top: e.g., '1. Determine generation needs → 2. Estimate credits with the function → 3. Choose plan → 4. Set budget guard limits'
Remove or significantly trim the BudgetGuard class—Claude can generate this pattern from a one-line instruction like 'Implement a daily credit limit check before each generation call'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with well-structured tables, but includes some unnecessary elements like the BudgetGuard class which is a generic pattern Claude could easily generate on its own. The cost estimation function is borderline—useful as a reference but could be more concise. | 2 / 3 |
Actionability | Provides fully executable Python code for cost estimation and budget guarding, concrete pricing tables with specific numbers, and a clear cost optimization strategies table with specific savings multipliers. The guidance is copy-paste ready. | 3 / 3 |
Workflow Clarity | The cost estimation and budget guard sections provide useful tools, but there's no clear workflow for how to actually approach budgeting—e.g., 'first estimate costs, then set budget limits, then monitor usage.' The optimization strategies are listed but not sequenced into a decision process. | 2 / 3 |
Progressive Disclosure | Content is reasonably well-organized with clear section headers and tables, but everything is inline in one file. The API resource packs, cost estimation code, and budget guard could be split into separate 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 | |
3e83543
Table of Contents
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.