klingai-pricing-basics
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'.
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-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 clear trigger terms and explicit '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 including both spaced and unspaced forms of the product name. | 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 unless there are multiple Kling AI-related skills, and even then the pricing/cost focus distinguishes it. | 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 concrete pricing data, executable code examples, and well-structured tables. Its main weaknesses are including some boilerplate code Claude could generate independently (BudgetGuard) and lacking a clear decision workflow for choosing plans/modes. The pricing information is time-sensitive and could become outdated, though this is inherent to the domain.
Suggestions
Remove or significantly trim the BudgetGuard class—Claude can generate this pattern from a one-line instruction like 'implement a daily credit budget guard'.
Add a brief decision workflow: 'To choose a plan: 1. Estimate monthly credits needed using estimate_cost() 2. Compare against plan tiers 3. If API access needed, calculate resource pack requirements separately'.
| 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 generate on its own. The cost estimation function is useful 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 examples include expected output. | 3 / 3 |
Workflow Clarity | This is primarily a reference/pricing skill rather than a multi-step workflow, but the cost optimization strategies are presented as independent tips rather than a sequenced decision process. The BudgetGuard lacks integration guidance showing how to use it within a generation workflow with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and tables, but everything is inline in a single file. The pricing tables, cost estimation code, and budget guard could be split into separate referenced files. For a skill of this length (~100 lines of substantive content), some separation would improve navigability. | 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.