Name: nocrmio
Rating: 63.2 (1 reviews)
Author: membranedev

nocrmio

NoCRM.io integration. Manage Leads, Persons, Organizations, Activities, Notes, Files and more. Use when the user wants to interact with NoCRM.io data.

Quality

75%

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

Quality

Content

76%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, well-structured integration guide built around executable Membrane CLI commands. Its weaknesses are minor conciseness padding and a lack of validation/verification guidance for destructive proxy and action operations, which caps workflow clarity.

Suggestions

Add an explicit verification/retry step for destructive operations (e.g., after `membrane action run` or `membrane request ... -X DELETE`, check the `output`/error fields and confirm the result before proceeding), to lift workflow clarity above the destructive-ops cap.

Trim the SMB intro sentence, the redundant 'Popular actions' section (it duplicates 'Searching for actions'), and the vague 'When to use which actions' filler to tighten conciseness.

Consider moving the proxy flags table or extended action-discovery detail into a one-level-deep reference file so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands with brief explanations, but has minor trimmable padding: the SMB marketing intro, the redundant 'Popular actions' section that repeats the action-list command, and the vague filler line 'When to use which actions: Use action names and parameters as needed.'	4 / 5
Actionability	It provides copy-paste-ready commands for every phase (install, login, connection ensure/get with --wait, action list/run with --input JSON, request with a full flags table), covering the common cases with concrete, executable guidance.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence and state-based feedback loops (poll until READY, branch on CLIENT_ACTION_REQUIRED), but the action-run and proxy-request paths support destructive operations (POST/PUT/DELETE via proxy) with no verification checkpoints, so the destructive-operations cap applies.	3 / 5
Progressive Disclosure	Content is well-organized into clear section headers and appropriately placed, but everything is inlined in a ~140-line SKILL.md with no bundle files and no one-level-deep references; the under-50-line simple-skill exception to reach 5 does not apply.	4 / 5
	Total	16 / 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, brand-specific description that states what it manages and gives an explicit 'Use when' trigger. Its main weakness is the generic 'Manage' action verb and a trigger clause that could list more concrete user phrasings.

Suggestions

Replace the generic 'Manage' with concrete actions (e.g., 'Create, update, search, and delete Leads, Persons, Organizations, Activities, Notes, and Files') to raise specificity.

Expand the 'Use when' clause with concrete trigger phrases users actually say (e.g., 'Use when the user wants to create or update leads, log activities, or query NoCRM.io records').

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete entities ('Leads, Persons, Organizations, Activities, Notes, Files') but the only action verb is the generic 'Manage', not multiple concrete actions, so it sits at the domain-with-limited-actions level rather than comprehensive action coverage.	3 / 5
Completeness	It answers both 'what' (manage the listed NoCRM.io entities) and 'when' ('Use when the user wants to interact with NoCRM.io data'), matching the both-present-but-could-be-more-explicit anchor; not a 5 because the trigger clause is generic rather than a set of concrete trigger phrases.	4 / 5
Trigger Term Quality	The brand term 'NoCRM.io' and core entity names (Leads, Persons, Organizations, etc.) are natural keywords a user would say, with the explicit trigger 'Use when the user wants to interact with NoCRM.io data'; a few common synonyms or phrasings are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The skill is anchored to a specific branded product ('NoCRM.io integration') 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/nocrmio/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.