Name: neetokb
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

neetokb

NeetoKB integration. Manage Articles, Categories. Use when the user wants to interact with NeetoKB data.

Quality

74%

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/neetokb/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 complete CLI commands and a well-sequenced connection workflow that includes state-check feedback loops. Its main weakness is mild over-explanation in the intro and best-practices prose that could be trimmed.

Suggestions

Trim the introductory paragraph ('Think of it as a central repository for FAQs, tutorials, and guides') since Claude can infer NeetoKB's purpose from the domain.

Tighten the Best practices bullets by dropping justification clauses (e.g. 'This will burn less tokens and make communication more secure').

Reconcile the step numbering — label the connection step as 'Step 1' so the 'skip to Step 2' reference is unambiguous, and merge the redundant 'Popular actions' section into 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, flags, and a compact options table with little padding. The one-paragraph intro ('NeetoKB is a knowledge base software... Think of it as a central repository...') and a few best-practice asides ('burn less tokens', 'make communication more secure') are minor over-explanation that could be trimmed, fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully lean level 5.	4 / 5
Actionability	Provides copy-paste-ready, complete bash commands for every step (install, login, connection ensure/get, action list/run, request) with real flags and a worked JSON-input example. Specific examples cover the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connect-to-NeetoKB flow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop until state changes. Minor gaps — an unlabeled 'Step 1' referenced via 'skip to Step 2' and a slightly redundant 'Popular actions' section — keep it just below the level-5 anchor with full feedback loops and checklists.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is organized into clear, navigable sections (Overview, Working with NeetoKB, Searching, Running actions, Proxy, Best practices) with no nested references. At ~158 lines it exceeds the simple-skill 50-line threshold, so it lands at 'good structure; well-placed content' rather than the level-5 simple-skill exception.	4 / 5
	Total	17 / 20 Passed

Description

66%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 answers both what and when with a distinct proper-noun trigger, but its actions are generic ('Manage') and trigger keywords lack synonyms. It is solid but could be sharpened with more concrete verbs and natural-sounding trigger variations.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, update, search, and delete Articles and Categories in NeetoKB'.

Add natural trigger synonyms users might say, e.g. 'Use when the user wants to manage a NeetoKB knowledge base, documentation, FAQs, or articles.'

Tighten the 'when' clause with concrete trigger phrases to lift completeness toward the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (NeetoKB) and two entity-level actions ('Manage Articles, Categories'), but 'Manage' is generic and coverage is not comprehensive. It sits at the anchor listing 1-2 concrete actions without full detail, not the level below (domain only, no actions) nor the level above (several specific actions).	3 / 5
Completeness	Explicitly states both what ('NeetoKB integration. Manage Articles, Categories.') and when ('Use when the user wants to interact with NeetoKB data.'). The 'when' clause is present and explicit but somewhat generic, so it fits 'has both what and when; when could be more specific' rather than the level-5 anchor requiring concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural phrase 'interact with NeetoKB data' plus entity terms 'Articles' and 'Categories', but lacks common synonyms or variations a user might say (e.g. 'knowledge base', 'documentation', 'FAQ'). Coverage is relevant but missing variations, matching the 'some relevant keywords' anchor rather than 'good coverage'.	3 / 5
Distinctiveness Conflict Risk	The proper noun 'NeetoKB' plus 'interact with NeetoKB data' carves out a clear niche with minimal conflict risk against other skills. It clearly matches the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/neetokb/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.