Name: knot-api
Rating: 56.8 (1 reviews)
Author: membranedev

knot-api

Knot API integration. Manage data, records, and automate workflows. Use when the user wants to interact with Knot API 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/knot-api/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 copy-paste-ready CLI commands and a strong connection/auth feedback loop, but it loses points to intro padding and to a lack of validation around its destructive-capable action/proxy operations. Structure is clean and self-contained with only minor organization gaps.

Suggestions

Trim the introductory paragraph and the 'focus on integration logic rather than auth plumbing' commentary so every token earns its place.

Add an explicit verify/confirm step before destructive proxy requests and action runs (e.g. dry-run or read-before-write) so the workflow includes validation checkpoints.

De-duplicate the overlapping 'Searching for actions' and 'Popular actions' sections, which restate the same action-list command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands, but the opening paragraph explains what the Knot API is and who uses it, and lines like 'so you can focus on the integration logic rather than auth plumbing' add prose padding that could be trimmed, placing it at the mostly-efficient-but-tightenable anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case — install, login, connection ensure, polling, action list/run, and proxy requests — plus a concrete flag table, fully covering the typical workflow with executable examples.	5 / 5
Workflow Clarity	The connection/auth sequence is well-ordered with state checks and a poll-then-retry feedback loop, but the destructive-capable operations (action run and proxy requests supporting POST/PUT/PATCH/DELETE) have no validation or verification steps, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clear sections (Overview, Working with Knot API, Popular actions, Best practices) with no nested references, but the file exceeds the simple-skill threshold and a couple of section headers overlap, leaving minor organization gaps below the 5.	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 correctly pairs a 'what' with an explicit 'Use when...' trigger and targets a distinct niche, but its action verbs are generic and it lacks the natural wedding-domain synonyms a user would actually say. It clears the completeness bar but stops short of the comprehensive, keyword-rich top anchors.

Suggestions

Replace generic verbs with concrete operations a user would request (e.g. 'track RSVPs, manage guest lists, coordinate wedding tasks') to lift specificity and trigger coverage.

Add natural trigger phrases a user would actually say, including wedding-domain synonyms and file/extension cues, rather than only 'interact with Knot API data'.

Tighten the 'when' clause to name the concrete scenarios (e.g. 'Use when the user wants to manage wedding RSVPs, guest lists, or vendor tasks via the Knot API').

Dimension	Reasoning	Score
Specificity	The description names the domain ("Knot API integration") and lists a few actions ("Manage data, records, and automate workflows"), but those actions are generic verbs rather than concrete operations, so it sits at the 1-2-concrete-actions anchor rather than the comprehensive 4-5.	3 / 5
Completeness	Both halves are present — a clear "what" ("Knot API integration. Manage data, records, and automate workflows.") and an explicit "Use when..." trigger — but the "when" is somewhat generic ("interact with Knot API data"), so it falls just below the fully-explicit 5 anchor.	4 / 5
Trigger Term Quality	It surfaces relevant keywords ("Knot API", "data", "records", "workflows", "interact with Knot API data") but misses natural synonyms and user-facing specifics like wedding/guest/RSVP terms, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The "Knot API" niche is specific enough to avoid broad overlap, but the trigger "interact with Knot API data" is generic enough that a closely-related data-integration skill could still collide, keeping it just below the minimal-conflict 5.	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/knot-api/SKILL.md
Commit: f484c82

Reviewed: 6 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.