Name: parsioio
Rating: 66.4 (1 reviews)
Author: membranedev

parsioio

Parsio.io integration. Manage Documents, Parsers, Inboxs, Templates, Folders, Users. Use when the user wants to interact with Parsio.io data.

Quality

80%

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

Quality

Content

88%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.

A highly actionable, well-sequenced integration guide with executable commands, a flag table, and explicit connection-state validation feedback loops. Minor conciseness trimming and optionally offloading the proxy flag table to a reference file would push it to the top tier.

Dimension	Reasoning	Score
Conciseness	The body is command-focused and mostly lean, with brief, useful context for Membrane-specific behavior (e.g., --wait long-polling, the clientAction fields); a few explanatory prose sentences ("This is the fastest way to get a connection...", the best-practices bullets) could be trimmed, keeping it just below a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (login, headless auth, connection ensure/get, action list/run with JSON input, proxy) plus a complete flag table and JSON-output handling.	5 / 5
Workflow Clarity	The connection workflow is explicitly sequenced with validation checkpoints and a feedback loop: branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, poll --wait until state changes, and re-poll after the user completes the action.	5 / 5
Progressive Disclosure	No bundle files exist and the body makes no file references; the doc is a single well-organized guide with clear section headers and no buried or nested references, though its length (~120 lines, including a flag table and proxy options that could live in a reference file) keeps it from a 5.	4 / 5
	Total	18 / 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.

A solid third-person description that states both capability and a use-trigger around a clearly distinctive third-party app. Its main weakness is the generic "Manage" verb for every entity and a thin, jargon-only set of trigger terms with a minor typo.

Suggestions

Replace the single generic verb "Manage" with several distinct concrete actions per entity (e.g., "List and fetch documents, create and update parsers, manage inbox and template settings").

Expand the "Use when..." clause with concrete, natural trigger phrases a user would actually say (e.g., "Use when the user wants to parse emails, extract data from Parsio documents, or manage Parsio inboxes, templates, and folders").

Fix the typo "Inboxs" → "Inboxes" and consider adding common synonyms or file-type cues users might mention.

Dimension	Reasoning	Score
Specificity	Names the Parsio.io domain plus six concrete managed entities ("Manage Documents, Parsers, Inboxs, Templates, Folders, Users"), matching the anchor listing several specific items with minor coverage gaps; not a 5 because every action is the single generic verb "Manage" rather than multiple distinct concrete actions.	4 / 5
Completeness	Explicitly answers both what ("Manage Documents, Parsers, Inboxs, Templates, Folders, Users") and when ("Use when the user wants to interact with Parsio.io data"), but the "when" clause is generic rather than a list of concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	Includes the distinctive trigger "Parsio.io" and the domain nouns (Documents, Parsers, Templates, Folders, Users), but these are mostly the app's own jargon with no common user synonyms, natural variations, or file-type terms; also contains the typo "Inboxs".	3 / 5
Distinctiveness Conflict Risk	The named third-party app "Parsio.io" creates a clear, distinct niche with a unique trigger and minimal 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/parsioio/SKILL.md
Commit: f484c82

Reviewed: 10 hours 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.