Name: knock
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

knock

Knock integration. Manage data, records, and automate workflows. Use when the user wants to interact with Knock data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/knock/SKILL.md

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 CLI commands and a clearly sequenced, state-checked connection workflow. Its main weaknesses are a dangling 'Step 2' reference, light error-recovery guidance for actions, and minor conciseness padding.

Suggestions

Define or remove the dangling 'Step 2' references so the connection workflow navigates coherently to the action-search section.

Add a short error-recovery feedback loop for action failures (e.g. re-check connection state, retry with corrected input) parallel to the connection-state handling.

Trim editorial filler like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands with only minor over-explanation (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection'); the brief Knock intro is justified context for a third-party product Claude may not know.	4 / 5
Actionability	It provides copy-paste-ready, fully executable commands for install, login, connection, action discovery, action execution, and proxying, plus a flag table covering the common proxy cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with explicit state-based checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / error states) and polling guidance, but it references a 'Step 2' that is never defined and lacks error-recovery feedback loops for action execution.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-sectioned SKILL.md; headers organize the content clearly and most material is appropriately placed, though the thin 'Knock Overview' bullet list and the inline proxy-flag table represent minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

57%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 clearly Knock-scoped and answers both what and when, but its capability phrasing is generic and omits Knock's notification focus. Trigger coverage is adequate but lacks notification synonyms.

Suggestions

Replace generic phrasing with concrete Knock capabilities, e.g. 'Send in-app, email, and push notifications; manage workflows and triggers.'

Broaden the 'when' clause to mention notification scenarios, e.g. 'Use when the user wants to send notifications or manage Knock workflows, triggers, and users.'

Dimension	Reasoning	Score
Specificity	It names the Knock domain but the actions 'Manage data, records, and automate workflows' are mostly generic; it never mentions notifications, Knock's core capability, so it sits below the midpoint rather than at the '1-2 concrete actions' anchor.	2 / 5
Completeness	Both a 'what' ('Knock integration. Manage data, records, and automate workflows.') and a 'when' ('Use when the user wants to interact with Knock data.') are present, but the 'when' is somewhat generic and could be more specific about notification use cases.	4 / 5
Trigger Term Quality	'Knock', 'data', 'records', and 'workflows' are relevant keywords and the 'Use when...' clause gives a usable trigger, but it misses common synonyms like 'notifications', 'in-app messages', 'email', or 'push'.	3 / 5
Distinctiveness Conflict Risk	The 'Knock' brand name and 'Use when the user wants to interact with Knock data' trigger give it a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing leaves minor overlap with other integration skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/knock/SKILL.md
Commit: f484c82

Reviewed: 5 days 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.