Name: nicereply
Rating: 61.6 (1 reviews)
Author: membranedev

nicereply

Nicereply integration. Manage Users, Roles, Organizations, Projects, Goals, Pipelines and more. Use when the user wants to interact with Nicereply data.

Quality

73%

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

Quality

Content

75%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 actionable and well-structured, with a strong connection-workflow state machine and concrete CLI examples throughout. Its main weaknesses are mild verbosity, a couple of orphaned step references, and no post-run verification guidance.

Suggestions

Tighten the opening "Nicereply is a customer satisfaction survey platform..." paragraph and the headless-environment block to the minimum needed for context.

Fix the orphaned navigation (define "Step 2" / "1a" explicitly or relabel sections so cross-references resolve).

Add a verification step after `membrane action run` (e.g. check the `output` field / error state) since actions can mutate Nicereply data.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with commands, a flag table, and tight best-practices bullets, but the opening product-description paragraph and the headless-environment explanation include mild over-explanation that could be trimmed.	4 / 5
Actionability	Concrete, copy-paste-ready `membrane` commands with `--json` flags and a full proxy-flag table cover the common cases; minor gaps remain (thin "Popular actions" section, proxy example lacks a realistic full call).	4 / 5
Workflow Clarity	The connection flow is a clear sequenced state machine with polling and a retry/feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but "Step 2" and "1b" are orphaned references and there is no verification step after running an action.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no bundle files, but everything is inlined in one ~140-line file rather than splitting the proxy/API reference into a separate file.	4 / 5
	Total	16 / 20 Passed

Description

71%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 clearly identifies a distinct product niche and lists concrete resources with an explicit use-when clause, but its trigger vocabulary is narrow (only the brand name) and the action verb is generic. Expanding trigger synonyms would lift the weaker dimensions.

Suggestions

Add natural trigger synonyms beyond the brand name, e.g. "surveys, CSAT scores, customer satisfaction ratings".

Replace the single generic verb "Manage" with more specific actions (create, list, update, delete) to sharpen the "what".

Drop the vague "and more" or replace it with the remaining concrete resource types.

Dimension	Reasoning	Score
Specificity	Lists several concrete resources ("Users, Roles, Organizations, Projects, Goals, Pipelines") but relies on a single generic verb "Manage" and a vague "and more", leaving minor coverage gaps.	4 / 5
Completeness	Provides a clear "what" (manage the listed Nicereply resources) and an explicit "when" clause ("Use when the user wants to interact with Nicereply data"), but the trigger phrase is generic rather than concrete.	4 / 5
Trigger Term Quality	The only natural keyword is "Nicereply" (repeated as "Nicereply data"); common synonyms users would say — surveys, CSAT, customer satisfaction, ratings — are absent.	3 / 5
Distinctiveness Conflict Risk	"Nicereply" names a specific product niche with distinct triggers, giving it minimal overlap or 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/nicereply/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.