Name: neuronwriter
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

neuronwriter

NEURONWriter integration. Manage Projects, Users. Use when the user wants to interact with NEURONWriter data.

Quality

70%

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/neuronwriter/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 a highly actionable, executable guide to driving NEURONWriter through the Membrane CLI, with a clear state-based connection workflow. It loses points mainly to filler prose, a repeated command, and slightly inconsistent step numbering rather than to missing capability.

Suggestions

Remove filler lines such as "Use action names and parameters as needed" and the vague Overview bullet list, or replace them with the concrete action names available.

De-duplicate the `membrane action list --intent` instruction that appears in both "Searching for actions" and "Popular actions".

Normalize the connection workflow numbering into a single labeled sequence (Step 1 ensure, Step 2 wait/handle client action, Step 3 search and run) so "Step 2" references resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but includes padding ("Use action names and parameters as needed", the vague Overview bullets, a marketing-style product intro) and repeats the action-list command in both "Searching for actions" and "Popular actions".	3 / 5
Actionability	It provides copy-paste-ready commands covering the common cases — install, login (incl. headless), connection ensure/get with --wait, action list/run with JSON input, and proxy requests with a full flag table — matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has a clear state-driven sequence with polling feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but step numbering is inconsistent ("Step 2" is referenced without a label, "1b" has no "1a"), keeping it below the checklist-level 5 anchor.	4 / 5
Progressive Disclosure	No bundle files exist and the single-file body is organized into clear headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); it cannot reach 5 because there are no one-level-deep references to signal, but structure is good.	4 / 5
	Total	16 / 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 is a concise, third-person, named-product integration statement that clearly answers both what and when. Its main weakness is thin, generic action and trigger language that under-represents the actual SEO/content use cases the body describes.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Manage NEURONWriter projects, users, content briefs, and article drafts."

Add natural trigger terms users would say, such as "SEO content", "keywords", or "competitor analysis", to the Use-when clause.

Tighten the when clause to concrete triggers: "Use when the user wants to research keywords, analyze competitors, or optimize SEO content in NEURONWriter."

Dimension	Reasoning	Score
Specificity	"Manage Projects, Users" names the NEURONWriter domain plus two entities, but the single generic verb "Manage" is not a comprehensive set of concrete actions, matching the 1-2-action anchor rather than the several-actions anchor at 4.	3 / 5
Completeness	It states both a what ("Manage Projects, Users") and an explicit when ("Use when the user wants to interact with NEURONWriter data"), but the when clause is generic rather than concrete trigger phrases, so it sits below the 5 anchor.	4 / 5
Trigger Term Quality	It surfaces "NEURONWriter", "Projects", and "Users", but omits the natural terms users actually say for this tool (SEO content, keywords, competitors, content optimization), so it has some relevant keywords with common variations missing.	3 / 5
Distinctiveness Conflict Risk	The named SaaS product "NEURONWriter" plus its scoped data domain give it a clear niche with distinct triggers and minimal overlap with other skills.	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/neuronwriter/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.