Name: parser-expert
Rating: 56.8 (1 reviews)
Author: membranedev

parser-expert

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

Quality

65%

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

Quality

Content

68%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 well-structured, mostly executable Membrane CLI integration guide with good command coverage and a connection-readiness feedback loop. Its main weaknesses are a broken 'Step 2' reference, missing post-run validation, and a couple of filler/redundant lines.

Suggestions

Label the workflow steps explicitly (e.g. '## Step 1: Connect', '## Step 2: Discover actions') so the 'skip to Step 2' references resolve.

Add a verification step after running actions (e.g. check the `output`/error fields) to satisfy validation for potentially destructive or batch action runs.

Remove the filler line 'When to use which actions: Use action names and parameters as needed.' and de-duplicate the `action list` command between the 'Searching for actions' and 'Popular actions' sections.

Dimension	Reasoning	Score
Conciseness	Largely lean CLI reference with executable commands and a compact flags table; minor filler remains ('When to use which actions: Use action names and parameters as needed.') and the 'Popular actions' section repeats the action-list command.	4 / 5
Actionability	Provides concrete copy-paste commands for install, auth, connection, action discovery/execution, and proxying, plus a flags table; minor gaps are the abstract '/path/to/endpoint' proxy example and unsubstituted CONNECTION_ID/<actionId> placeholders.	4 / 5
Workflow Clarity	A clear install→auth→connect→poll→search→run sequence exists with a state feedback loop, but 'skip to Step 2' references an unlabeled step and there is no validation after running potentially destructive actions.	3 / 5
Progressive Disclosure	No bundle files exist and the guide is a single self-contained document, but it is well-organized with clear section headers and no nested references; it could split the flags/state-machine detail out but stays navigable.	4 / 5
	Total	15 / 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 an explicit 'Use when' trigger and names the specific product, but its capability phrasing is generic and lacks the concrete parsing/extraction actions that define Parser Expert. It is functional but could be sharper.

Suggestions

Replace generic verbs with concrete Parser Expert capabilities, e.g. 'define parsing rules and extract structured data from documents, web pages, and text sources'.

Add natural trigger synonyms users would say — 'parsing', 'extract structured data', 'parse unstructured text' — alongside 'Parser Expert'.

Tighten the 'what' to mirror the body's actual value (structured-data extraction) so the description is distinct from generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Parser Expert) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic and buzzwordy rather than concrete — no mention of parsing rules or structured-data extraction.	3 / 5
Completeness	Provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when...'), though the 'what' is vague, keeping it below a 5.	4 / 5
Trigger Term Quality	Includes the product name and 'Use when the user wants to interact with Parser Expert data', but misses common natural synonyms such as parsing, extraction, or relevant file/source types.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'Parser Expert' gives it a clear niche with low conflict risk, but the broad action verbs ('manage data, automate workflows') leave minor overlap with generic data skills.	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/parser-expert/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.