Name: knack
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

knack

Knack integration. Manage Organizations. Use when the user wants to interact with Knack data.

Quality

65%

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/knack/SKILL.md

Quality

Content

68%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 concrete, executable Membrane CLI commands and a clear connection-state workflow, but it wastes tokens explaining Knack basics and omits validation safeguards for destructive record operations. A couple of trims and a pre-delete verification step would meaningfully raise quality.

Suggestions

Add an explicit validation/confirmation checkpoint before running destructive actions (e.g. verify the record ID and confirm with the user before delete-record, and check the output for success after update/create).

Remove the introductory paragraph explaining what Knack is and the vague 'When to use which actions' line; assume Claude's competence and keep only integration-specific guidance.

Fix the dangling 'skip to Step 2' reference — there is no labeled Step 2 — by renumbering the connecting/searching sections into an explicit step sequence.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI commands, but it opens by explaining what Knack is ('Knack is a no-code platform that allows users to build...') and includes vague filler ('When to use actions: Use action names and parameters as needed') that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every stage (npm install, membrane login, connection ensure, action list/run, request) plus a concrete popular-actions table and a proxy flag reference, covering the common cases fully.	5 / 5
Workflow Clarity	The install→authenticate→connect→search→run sequence is present with state-based checkpoints, but destructive/batch actions (delete-record, update-record, list-records) are run with no validation or confirmation step, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly headed sections with no nested references, and for a CLI integration keeping it in one file is appropriate; the only gap is that the action/proxy tables could optionally live in reference files.	4 / 5
	Total	15 / 20 Passed

Description

62%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 well-structured with an explicit 'Use when' trigger and a clear product niche, but its capability statement is thin and generic. Tightening the 'what' with concrete Knack actions and richer trigger synonyms would lift it.

Suggestions

Replace the generic 'Manage Organizations' with concrete Knack actions (e.g. 'Create, update, delete, and list records in Knack objects') so the capability statement is specific.

Add natural trigger synonyms and file/term variants (e.g. 'Knack app', 'Knack database', 'Knack records', 'Knack objects') to improve trigger-term coverage.

Align the description's stated actions with the body, which centers on records/objects/views rather than 'Organizations'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Knack integration') and one concrete action ('Manage Organizations'), matching the anchor for naming a domain plus 1-2 concrete actions, but it is not comprehensive and the single action is fairly generic.	3 / 5
Completeness	It answers both what ('Knack integration. Manage Organizations.') and when ('Use when the user wants to interact with Knack data.'), but the 'what' is somewhat generic so it does not fully reach the explicit-concrete-phrase level of 5.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Knack', 'Knack data') in a 'Use when' clause, but lacks common variations or synonyms a user might say such as 'Knack app', 'Knack database', 'Knack records', or 'Knack objects'.	3 / 5
Distinctiveness Conflict Risk	The Knack product name gives it a clear, distinct niche with a specific trigger ('interact with Knack data'), but the generic 'Manage Organizations' phrasing creates minor overlap risk with general organization-management skills.	4 / 5
	Total	14 / 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/knack/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.