Name: knorish
Rating: 60.8 (1 reviews)
Author: membranedev

knorish

Knorish integration. Manage Users, Organizations, Courses, Funnels, Blogs, Affiliates and more. Use when the user wants to interact with Knorish data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/knorish/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.

A highly actionable skill body with concrete CLI commands and clear connection-state handling. Its weak spots are background padding that hurts conciseness and the absence of validation guardrails around destructive operations.

Suggestions

Trim the introductory platform description and the product-overview tree, which restate knowledge Claude already has.

Add an explicit validation/confirmation checkpoint before destructive actions, e.g. require a user confirmation or a dry-run before running delete-user, delete-course, or delete-bundle.

Move the popular-actions table and proxy flag reference into a reference file referenced one level deep from SKILL.md to improve progressive disclosure and reduce token load.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes unnecessary background Claude already knows ("Knorish is a platform that enables individuals and businesses to create and sell online courses...") and a large product-overview tree that could be trimmed, matching anchor 3.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request) plus a popular-actions table and a flag-reference table, covering the common cases as anchor 5 requires.	5 / 5
Workflow Clarity	The connection setup flow is well sequenced with state-polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive actions (delete-user, delete-course, delete-bundle) are listed with no validation or confirmation step, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is a single ~180-line document with clear, well-organized section headers; structure is good with only minor organization gaps, matching anchor 4 rather than 5 (which expects explicit one-level-deep references).	4 / 5
	Total	15 / 20 Passed

Description

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

A solid, distinct description that states both capability and trigger, tied clearly to the Knorish platform. Its main weakness is the generic "Manage" verb and the somewhat vague "interact with Knorish data" trigger phrase.

Suggestions

Replace the generic "Manage" with concrete operations, e.g. "Create, list, update, and delete Users, Courses, Bundles...", to lift specificity.

Make the trigger clause more concrete: "Use when the user wants to manage Knorish users, courses, enrollments, funnels, or affiliates."

Drop the vague "and more" or replace it with the remaining concrete entities to avoid an open-ended claim.

Dimension	Reasoning	Score
Specificity	The description names concrete Knorish entities ("Users, Organizations, Courses, Funnels, Blogs, Affiliates") but relies on a single generic verb ("Manage") without enumerating distinct operations and trails off with the vague "and more," sitting between anchors 3 and 4.	3 / 5
Completeness	It explicitly answers both "what" (manage the listed Knorish entities) and "when" ("Use when the user wants to interact with Knorish data"), but the "when" clause is generic rather than listing concrete trigger phrases, matching anchor 4 rather than 5.	4 / 5
Trigger Term Quality	Natural user-facing terms are present ("Knorish," courses, users, funnels, blogs, affiliates), giving good keyword coverage, though the trigger phrase "interact with Knorish data" is somewhat generic and a few natural phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	It is anchored to a specific named platform ("Knorish") with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/knorish/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.