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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean and highly actionable, with exact pricing tables and runnable code. Its weaknesses are the absence of an explicit cost-estimation workflow with checkpoints and poor progressive disclosure: bundle reference files exist but are orphaned and never linked from the body.

Suggestions

Link the existing references/ files from the body (e.g., 'See [pricing-structure.md](references/pricing-structure.md) for full plan details') and move the large pricing/optimization tables out of SKILL.md into those files, keeping the body as an overview.

Add a short sequenced workflow (estimate credits -> check BudgetGuard -> choose optimization strategy) with an explicit validation/budget checkpoint instead of presenting the tools as isolated sections.

Either populate references/examples.md with real worked examples or remove it so the bundle has no empty placeholder files.

Dimension	Reasoning	Score
Conciseness	The body is data-dense (seven pricing tables plus two concise code blocks) with no conceptual padding Claude already knows, so every token earns its place; only minor blemishes like the non-savings 'callbacks' row keep it from being perfect.	3 / 3
Actionability	Provides two complete, executable Python blocks (estimate_cost and BudgetGuard) with example invocations and output, plus exact per-feature credit tables that are copy-paste ready.	3 / 3
Workflow Clarity	The skill supplies discrete tools (estimate, guard, optimize) but never sequences them into an explicit workflow with validation checkpoints; the estimate→guard→optimize flow is only implicit, matching 'steps present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	Five reference files exist under references/ but the body never links to or signals them (examples.md is effectively empty), while detailed pricing, optimization, and budget content that should be split out remains inline in SKILL.md.	2 / 3
	Total	10 / 12 Passed

Description

90%

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: it states a clear niche, includes an explicit 'Use when' clause, and supplies natural trigger phrases with spelling variants. Its only weakness is the single abstract verb 'Understand' instead of enumerating concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain clearly ('Kling AI pricing, credits, and cost optimization strategies') but relies on a single abstract verb ('Understand') rather than listing multiple concrete actions, matching 'names domain and some actions, but not comprehensive'.	2 / 3
Completeness	Explicitly answers both what ('Understand Kling AI pricing, credits, and cost optimization strategies') and when ('Use when budgeting or estimating costs'), with an explicit 'Use when...' clause present.	3 / 3
Trigger Term Quality	Provides four natural trigger phrases a user would actually say ('kling ai pricing', 'klingai credits', 'kling ai cost', 'klingai budget'), including klingai/kling ai spelling variants, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	'Kling AI pricing' is a narrow, well-defined niche with distinct triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.