Name: nlp-cloud
Rating: 55.2 (1 reviews)
Author: membranedev

nlp-cloud

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

Quality

62%

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

Quality

Content

67%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 a strong, actionable integration guide with concrete Membrane CLI commands, a well-sequenced connection workflow with state-checking checkpoints, and clean sectioning. Its main weakness is an over-explanatory intro paragraph that pads tokens with general NLP background Claude already knows.

Suggestions

Trim or remove the intro paragraph ("NLP Cloud is an API that provides... scalable and reliable NLP services") — Claude already knows what NLP Cloud is.

Label the destination of "Skip to Step 2" (e.g. an explicit '## Step 2: Run actions' heading) so the cross-reference resolves.

Add one short sample `membrane action run` output snippet so the 'result is in the output field' guidance is concrete.

Dimension	Reasoning	Score
Conciseness	Quotes "NLP Cloud is an API that provides various natural language processing features... without building their own models" over-explain what NLP Cloud is — knowledge Claude already has — while the rest (commands, flag table, best practices) is mostly efficient; matches anchor 3 ('Mostly efficient but includes some unnecessary explanation').	3 / 5
Actionability	Quotes like `membrane connection ensure "https://nlpcloud.io/" --json` and `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{...}' --json` are concrete executable commands with flags; minor gaps (ID placeholders, no sample run output) keep it below anchor 5.	4 / 5
Workflow Clarity	The connection flow (ensure → poll until non-BUILDING → branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → poll again after action) is a clear sequence with state-checking checkpoints and a poll-again feedback loop; the dangling "Skip to Step 2" reference (no labeled Step 2) is a minor gap, so it sits at anchor 4 rather than 5. No destructive/batch cap applies.	4 / 5
Progressive Disclosure	The body is organized into clear sections (Overview, Working with NLP Cloud, Install, Authentication, Connecting, Searching actions, Proxy, Best practices) with no external references needed; at ~80 lines it exceeds the under-50-line simple-skill exception, so it matches anchor 4 ('Good structure; most content appropriately placed') rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly pairs a 'what' with an explicit 'Use when' trigger and is anchored to a distinct NLP Cloud niche, but its action language is generic rather than concrete and it omits natural synonym triggers. Tightening the action verbs and adding common NLP terms would lift it toward the top anchors.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Run sentiment analysis, translation, NER, and summarization via NLP Cloud.'

Add natural trigger synonyms users actually say, e.g. 'Use when the user mentions NLP Cloud, sentiment analysis, or machine translation.'

Drop the filler clause 'Manage data, records, and automate workflows' which overlaps with broad data-management skills and dilutes distinctiveness.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the NLP Cloud domain but the actions are generic ('manage', 'automate') rather than concrete; matches anchor 2 ('Names the domain but actions are minimal or generic') and falls short of anchor 3 because no genuinely concrete actions are listed.	2 / 5
Completeness	Quotes provide a clear 'what' ("NLP Cloud integration. Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with NLP Cloud data"); the 'when' is present but generic, matching anchor 4 and falling short of anchor 5's concrete trigger phrases.	4 / 5
Trigger Term Quality	Quotes "NLP Cloud" and "interact with NLP Cloud data" provide a relevant proper-noun trigger but miss natural synonyms users might say (e.g. 'sentiment analysis', 'translation', 'NER'); matches anchor 3 ('Some relevant keywords but missing common variations or synonyms').	3 / 5
Distinctiveness Conflict Risk	The "NLP Cloud" trigger carves a clear niche with minimal conflict risk, but generic phrases like "Manage data, records, and automate workflows" create minor overlap with general data-management skills; matches anchor 4 ('Mostly distinct; minor overlap risk').	4 / 5
	Total	13 / 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/nlp-cloud/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.