Name: niceboard
Rating: 64.8 (1 reviews)
Author: membranedev

niceboard

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

Quality

78%

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/niceboard/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 content is a strong, executable Membrane CLI reference with a well-validated connection workflow and clear section structure. Its main weaknesses are minor command duplication and the absence of validation guidance for action-run results.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, domain-specific CLI reference Claude would not already know, but the `membrane action list --intent=QUERY` command is repeated across 'Searching for actions', 'Popular actions', and 'Best practices', which is minor trimmable redundancy; not a 5 due to that duplication, not a 3 because the bulk earns its tokens.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for install, login, connection ensure/get with --wait, action run with --input, and proxy requests, plus a flags table covering the common cases; placeholders like CONNECTION_ID are standard and match the anchor-5 example's use of 'file.pdf'.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling feedback loop, matching 'clear sequence with most checkpoints present'; not a 5 because action execution lacks any output validation/verification step beyond 'result is in the output field'.	4 / 5
Progressive Disclosure	The body is well-sectioned (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and no bundle files to navigate; not a 5 because the 'Niceboard Overview' list is sparse and the 'Popular actions' section is near-empty, minor organization gaps.	4 / 5
	Total	17 / 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.

The description is well-structured with an explicit 'Use when' clause and a clear, distinct Niceboard niche, but its action language is generic ('Manage data, records, and automate workflows') rather than concrete and Niceboard-specific. Strengthening the verbs and adding varied trigger phrasings would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Niceboard operations drawn from the body (e.g., 'collect, organize, and prioritize customer feedback', 'configure widgets, data sources, and alerts', 'manage users').

Expand the 'Use when...' clause with concrete trigger phrasings a user would naturally say (e.g., 'when the user mentions customer feedback, Niceboard widgets, alerts, or wants to triage user feedback').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Niceboard integration') and three actions ('Manage data, records, and automate workflows'), but the verbs are generic and abstract rather than concrete Niceboard-specific operations, fitting the 'names domain and 1-2 actions but not comprehensive' anchor; not a 2 because multiple actions are listed, not a 4 because none are concrete like 'extract' or 'fill forms'.	3 / 5
Completeness	It has an explicit 'Use when the user wants to interact with Niceboard data' trigger and a clear (if generic) 'what' statement, satisfying both anchors; not a 5 because the 'what' lacks concrete trigger phrases and the action list is generic.	4 / 5
Trigger Term Quality	Natural trigger terms include 'Niceboard' and 'interact with Niceboard data', which are exactly what a user would say for this SaaS; it is not a 5 because there are no synonyms or varied phrasings beyond the product name and 'Niceboard data'.	4 / 5
Distinctiveness Conflict Risk	The named product 'Niceboard' plus a Niceboard-specific trigger gives it a clear niche with minimal conflict risk against other skills; the generic action verbs do not meaningfully raise overlap because the product name anchors it.	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/niceboard/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.