klingai-webhook-config
Configure webhook callbacks for Kling AI task completion. Use when building event-driven pipelines or replacing polling. Trigger with phrases like 'klingai webhook', 'kling ai callback', 'klingai notifications', 'video completion webhook'.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 clear trigger terms and explicit 'when' guidance. Its main weakness is that the 'what' portion could be more specific about the concrete actions involved (e.g., registering endpoints, configuring payload formats, handling retry logic). Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions beyond 'configure webhook callbacks', such as 'register callback URLs, verify webhook signatures, parse completion payloads' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Kling AI webhook callbacks) and mentions a couple of actions (configure webhook callbacks, replacing polling), but doesn't list multiple concrete actions like registering endpoints, verifying signatures, handling payloads, etc. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure webhook callbacks for Kling AI task completion) and 'when' (building event-driven pipelines, replacing polling) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'klingai webhook', 'kling ai callback', 'klingai notifications', 'video completion webhook'. Good coverage of variations including the product name and common synonyms like callback/notification. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Kling AI webhooks — with distinct trigger terms that are unlikely to conflict with other skills. The combination of 'Kling AI' and 'webhook' creates a clear, narrow scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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, actionable skill with executable code examples covering the full webhook lifecycle including a thoughtful reliability/fallback pattern. The main weakness is moderate verbosity—providing both Flask and Express examples plus the full JWT auth boilerplate inflates the token cost. The workflow is clear with good error handling guidance and the requirements table is a nice touch.
Suggestions
Consider moving the Express.js receiver to a separate reference file to reduce the main skill's token footprint, or pick one language and note the pattern translates directly.
Extract the JWT auth helper into a shared reference (or reference the auth skill if one exists) rather than repeating the boilerplate inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary verbosity. The JWT auth boilerplate in the task creation example adds bulk that isn't specific to webhooks. Providing both Flask and Express receivers is useful but adds length; the overview section's explanation of how webhooks work is somewhat redundant for Claude. | 2 / 3 |
Actionability | Fully executable code examples in Python and JavaScript, complete with JWT auth setup, Flask/Express webhook receivers, payload shape documentation, and a fallback polling pattern. The code is copy-paste ready and covers the full workflow from task submission to webhook handling. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced: submit task with callback → receive webhook → process result. The reliability pattern with fallback polling addresses the critical failure mode of missed callbacks. The requirements table provides clear validation criteria for the webhook endpoint. The 4-step 'How It Works' section establishes the sequence clearly. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a requirements table, but it's somewhat monolithic at ~120 lines. The webhook reliability pattern and the dual-language receiver examples could potentially be split into referenced files. However, external references to API docs are provided at the end. | 2 / 3 |
Total | 10 / 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
70e9fa4
- 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.