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

Blog Docs Log in Get started

parseur

Parseur integration. Manage Mailboxs. Use when the user wants to interact with Parseur data.

Quality

72%

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/parseur/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 highly actionable, with copy-paste-ready Membrane CLI commands and a well-sequenced connection state machine that includes a real feedback loop. It loses points only on mild intro padding and the absence of validation/verification guidance for the destructive or batch data operations the skill is meant to manage.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, built from concrete commands and config tables, but includes minor padding Claude does not need — the business-value intro ("helps them streamline workflows and reduce manual data entry") and the "so you can focus on the integration logic rather than auth plumbing" aside.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for the common cases — install, login (including headless completion), connection ensure, polling, action list/run with JSON input, and a proxy flags table — covering the full workflow surface.	5 / 5
Workflow Clarity	The connection-readiness flow is clearly sequenced with an explicit feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED, surface CONFIGURATION_ERROR), but the skill manages mailboxes/documents/data with no validation or confirmation guidance for those actual operations.	4 / 5
Progressive Disclosure	The skill is a single well-organized SKILL.md with clear section headers and no nested or buried references, and no bundle files exist to split; it is slightly long for a single file with no progressive split, keeping it just below the ideal.	4 / 5
	Total	17 / 20 Passed

Description

62%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 includes both a capability statement and an explicit "Use when" trigger, and the Parseur proper noun keeps it distinct. It is held back by a single vague action ("Manage Mailboxs"), a typo, and a generic trigger phrase that omits the natural terms users would actually say.

Suggestions

Expand the capability list beyond mailboxes to reflect what the body covers, e.g. "Manage Parseur mailboxes, documents, templates, and integrations."

Replace the generic trigger with concrete user phrases: "Use when the user wants to parse emails or PDFs, extract data with Parseur, or manage Parseur mailboxes and templates."

Fix the typo "Mailboxs" → "Mailboxes" so the description reads cleanly.

Dimension	Reasoning	Score
Specificity	"Parseur integration. Manage Mailboxs." names the domain plus one concrete action (managing mailboxes), but coverage is not comprehensive — only mailboxes are named, omitting documents, templates, and integrations that the body shows exist.	3 / 5
Completeness	Both a "what" (Parseur integration, manage mailboxes) and an explicit "when" ("Use when the user wants to interact with Parseur data") are present, but the "when" clause is generic and could name concrete triggers more specifically.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Parseur data" surfaces the proper noun and a generic "interact with Parseur data" phrase, but misses natural variations like parsing emails, extracting data from PDFs, or template creation that users would actually say.	3 / 5
Distinctiveness Conflict Risk	The Parseur proper noun gives the skill a clear, distinct niche with low conflict risk, but the broad "interact with Parseur data" trigger leaves some overlap with generic data-handling skills rather than fully tight, Parseur-specific triggers.	4 / 5
	Total	14 / 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/parseur/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.