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

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is actionable and well-sequenced with executable JWT code and a validation step, but the reference bundle is disconnected: files are unreferenced from the body and push a conflicting API-key auth model, breaking progressive-disclosure integrity.

Suggestions

Link the reference files from the body (e.g., a 'References' section pointing to environment-setup.md, errors.md, examples.md) so the bundle is navigable rather than orphaned.

Reconcile the bundle with the body: the references use a plain KLINGAI_API_KEY Bearer scheme while the body uses JWT — pick one auth model across all files to avoid contradictory guidance.

Move the duplicated material (env setup, error table) into the matching reference files and keep the body as a lean overview to remove the inline/bundle duplication.

DimensionReasoningScore

Conciseness

Mostly lean with no padding about what JWT is, but the JWT-generation logic appears twice (Step 2 and the KlingAuth class) and a few inline comments restate obvious context, so it sits below the fully-tight 5 anchor.

4 / 5

Actionability

Provides complete, copy-paste-ready Python and Node.js JWT generation, a verification request, and an auto-refreshing token manager class — fully executable across common cases.

5 / 5

Workflow Clarity

Clear sequenced steps (Get Credentials → Generate JWT → Verify Authentication) with an explicit validation checkpoint in Step 3 and an error-recovery table, but lacks a final post-integration checklist that would reach the 5 anchor.

4 / 5

Progressive Disclosure

Three bundle files exist in references/ (environment-setup.md, errors.md, examples.md) but the body never links to or signals them, and their content both duplicates and contradicts the body (plain KLINGAI_API_KEY bearer vs. JWT) — references are effectively orphaned and inlined content that belongs in those files is duplicated.

2 / 5

Total

15

/

20

Passed

Description

90%Weight 40%Scale 1-5

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 well-crafted, third-person description that answers both what and when and supplies concrete trigger phrases. Its only weakness is modest action specificity for a single-purpose skill, which is appropriate rather than defective.

DimensionReasoningScore

Specificity

Names the domain ('Kling AI API authentication with JWT tokens') but only one concrete action ('Set up'), so it matches the anchor naming a domain with 1-2 actions rather than the multi-action list at 4.

3 / 5

Completeness

Explicitly states what ('Set up Kling AI API authentication with JWT tokens') and when ('Use when starting a new Kling AI integration or troubleshooting auth issues') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Provides four natural trigger phrases ('kling ai setup', 'klingai api key', 'kling ai authentication', 'configure klingai') covering synonyms a user would actually say, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (Kling AI auth via JWT) with distinct branded triggers, minimal overlap risk with other skills.

5 / 5

Total

18

/

20

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.