CtrlK
BlogDocsLog inGet started
Tessl Logo

klingai-install-auth

Set up Kling AI API authentication with JWT tokens. Use when starting a new Kling AI integration or troubleshooting auth issues. Trigger with phrases like 'kling ai setup', 'klingai api key', 'kling ai authentication', 'configure klingai'.

68

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

77%

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

A highly actionable, well-sequenced auth setup with executable code and validation, but it functions as a self-contained monolith that ignores its own bundle files — which also diverge in auth scheme — capping progressive disclosure at 2.

Suggestions

Link the existing reference files from the body (e.g., a 'See references/errors.md for the full error catalog' note) so the bundle is actually navigable rather than orphaned.

Reconcile the auth scheme: the body uses JWT (AK/SK) while references/environment-setup.md and examples.md use a plain KLINGAI_API_KEY Bearer token — pick one and align all files to avoid conflicting guidance.

Trim the inline error table and token-management class into the reference files to tighten conciseness, keeping the body a lean overview pointing to detail.

DimensionReasoningScore

Conciseness

The body is mostly efficient and executable, but the auto-refresh KlingAuth class and duplicated Authorization headers add length that could be tightened; it is not quite the lean 'every token earns its place' of the 3-anchor.

2 / 3

Actionability

Provides complete, copy-paste-ready executable code for both Python and Node.js (JWT generation, verification, auto-refresh) plus a concrete error table, matching the fully-executable 3-anchor.

3 / 3

Workflow Clarity

Steps 1–3 are clearly sequenced with an explicit validation checkpoint in Step 3 (Verify Authentication checking 401/200/400) and a feedback loop via the error-handling table; this is not a destructive/batch operation so no cap applies.

3 / 3

Progressive Disclosure

Three reference files exist (errors.md, examples.md, environment-setup.md) but the body never links to or signals them, and overlapping content (errors, env setup, examples) is kept inline; additionally the references use a conflicting API-key Bearer scheme rather than JWT, so references are present but poorly organized/signaled.

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.

A focused, well-constructed description that clearly states capability and trigger conditions with natural keywords. It is slightly general in the breadth of concrete actions named, capping specificity at 2.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ("Set up Kling AI API authentication with JWT tokens", "troubleshooting auth issues"), but does not list multiple distinct specific actions like the 3-anchor example, so it stops at 2.

2 / 3

Completeness

Explicitly states what it does ("Set up Kling AI API authentication with JWT tokens") and when to use it ("Use when starting a new Kling AI integration or troubleshooting auth issues"), satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Provides natural phrases users would actually say — "kling ai setup", "klingai api key", "kling ai authentication", "configure klingai" — with good coverage of common variations, matching the 3-anchor.

3 / 3

Distinctiveness Conflict Risk

"Kling AI" is a specific niche with distinctive triggers, making it unlikely to fire for unrelated skills; voice is third-person/imperative with no first/second-person penalty.

3 / 3

Total

11

/

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.