klingai-pricing-basics
Manage understand Kling AI pricing, credits, and cost optimization. Use when budgeting or optimizing costs for video generation. Trigger with phrases like 'kling ai pricing', 'klingai credits', 'kling ai cost', 'klingai budget'.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill klingai-pricing-basics57
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 the specificity of capabilities - it describes the domain well but could benefit from listing more concrete actions the skill can perform. There's also a minor grammatical issue ('Manage understand' should be 'Manage and understand').
Suggestions
Fix the grammatical error: change 'Manage understand' to 'Manage and understand' or restructure the opening
Add more specific concrete actions like 'calculate credit costs per video', 'compare pricing tiers', or 'estimate project budgets'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI pricing/credits/cost optimization) and mentions some actions (budgeting, optimizing costs), but lacks specific concrete actions like 'calculate credit usage', 'compare pricing tiers', or 'estimate project costs'. | 2 / 3 |
Completeness | Clearly answers both what (manage/understand Kling AI pricing, credits, cost optimization) and when (budgeting or optimizing costs for video generation) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | Includes good coverage of natural terms users would say: 'kling ai pricing', 'klingai credits', 'kling ai cost', 'klingai budget', plus contextual terms like 'video generation' and 'cost optimization'. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Kling AI pricing specifically, with distinct product-specific triggers that are unlikely to conflict with general pricing or budgeting 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 template or placeholder rather than functional documentation. It describes what a pricing skill should do but provides zero actual pricing information, credit values, cost formulas, or concrete optimization strategies. Claude would learn nothing actionable from this content.
Suggestions
Add actual pricing tiers and credit costs (e.g., '1 credit = $X, 5-second video = Y credits')
Include concrete cost calculation formulas or examples (e.g., 'A 10-second 1080p video costs approximately X credits')
Replace vague steps with specific actionable guidance (e.g., 'To estimate cost: multiply duration_seconds × resolution_multiplier × model_tier_cost')
Add a quick reference table showing model tiers, their costs, and quality tradeoffs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes unnecessary scaffolding like 'Prerequisites' and 'Overview' sections that don't add value. The instructions are vague placeholders rather than actual information about pricing. | 2 / 3 |
Actionability | The skill provides no concrete pricing information, credit values, cost calculations, or specific guidance. Steps like 'Learn how credits work' and 'Estimate costs for your projects' are abstract descriptions rather than actionable instructions. | 1 / 3 |
Workflow Clarity | The numbered steps are vague directives without any actual process details. There's no concrete workflow for calculating costs, no formulas, no validation steps, and no specific guidance on how to accomplish any of the listed tasks. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one level deep, but the main content is so sparse that it's unclear what value those references would add. The structure exists but the core content is missing. | 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 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.