CtrlK
BlogDocsLog inGet started
Tessl Logo

hookdeck

Hookdeck integration. Manage Connections, Issues, Workflows. Use when the user wants to interact with Hookdeck data.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hookdeck/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with executable commands and a clear, state-driven connection workflow. Its main weaknesses are minor padding in the intro and an inlined bulk reference table that would benefit from a separate file.

Suggestions

Trim the opening "Hookdeck is a webhook management tool..." paragraph to a one-line product framing; Claude can infer the rest.

Move the 20-row Popular actions table into a references/ file and link to it from SKILL.md to improve progressive disclosure.

Add an explicit validation/check step before mutating actions (create-connection, update-connection) to strengthen the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the introductory "Hookdeck is a webhook management tool..." paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" are mild padding that could be trimmed.

4 / 5

Actionability

Copy-paste executable commands cover the common cases end to end — install, login (including headless completion), connection ensure/poll, action list/run with JSON input, and proxy requests with a full flags table.

5 / 5

Workflow Clarity

The connection lifecycle is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, but mutating actions (create/update connection) lack an explicit pre-mutation validation step.

4 / 5

Progressive Disclosure

Sections are well-organized and clearly signaled, but the 20-row actions table is bulk reference content inlined in SKILL.md with no one-level-deep reference files to offload it (no references/ bundle exists).

4 / 5

Total

17

/

20

Passed

Description

75%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.

The description is concise, third-person, and covers both what the skill does and when to use it, anchored to a distinct product niche. It falls short of the top anchor only on comprehensiveness of trigger synonyms and concrete trigger phrases.

Suggestions

Broaden the entity list in the "what" clause to include Destinations, Events, and Sources for fuller coverage.

Add concrete user-facing trigger phrases (e.g. "webhooks", "delivery issues", "event retries") to the "Use when" clause.

Add a file-extension or product-synonym cue so users who say "webhook management" rather than "Hookdeck" still trigger it.

DimensionReasoningScore

Specificity

"Manage Connections, Issues, Workflows" names several specific action-objects but omits prominent Hookdeck entities (Destinations, Events, Sources, Transformations), leaving minor coverage gaps.

4 / 5

Completeness

It states a clear "what" ("Manage Connections, Issues, Workflows") and an explicit "when" ("Use when the user wants to interact with Hookdeck data"), but the trigger clause is slightly generic rather than concrete.

4 / 5

Trigger Term Quality

Natural terms like "Hookdeck", "Connections", "Issues", "Workflows", and "interact with Hookdeck data" are present, but common synonyms users might say ("webhooks", "events", "logs") are missing.

4 / 5

Distinctiveness Conflict Risk

Anchoring to the named product "Hookdeck" with a product-scoped trigger gives it a clear niche with minimal conflict risk, though the generic nouns Connections/Issues/Workflows carry minor overlap.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.