Name: parma
Rating: 64.8 (1 reviews)
Author: membranedev

parma

Parma integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Parma data.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/parma/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 body is a strong, actionable CLI integration guide with concrete commands and a well-sequenced connection workflow including feedback loops. It could be tightened by removing redundancy and the dangling 'Step 2' reference, and by adding a verify step after action runs.

Suggestions

Remove the redundant 'Popular actions' section (it duplicates 'Searching for actions') and the filler line 'Use action names and parameters as needed.' to trim tokens.

Fix the dangling 'Step 2' reference by labeling the subsequent section as Step 2, and renumber '1b' consistently within the connection flow.

Add a brief verification step after `membrane action run` (e.g., inspect the `output` field and confirm expected state) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, but includes minor padding such as the introductory 'Parma is a SaaS application…' sentence, a redundant 'Popular actions' section that repeats 'Searching for actions', and the filler line 'Use action names and parameters as needed.'	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure/get, action list/run, request) plus a concrete proxy-options table, covering the typical workflow end to end.	5 / 5
Workflow Clarity	The connection flow is a clear state machine with explicit checkpoints and feedback loops (poll until READY, act on CLIENT_ACTION_REQUIRED, re-poll), but 'Step 2' is referenced without a matching header, the '1b' numbering is inconsistent, and there is no verification step after running an action.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections with no nested references, and the single-file layout is reasonable for a CLI integration guide; the only gaps are minor redundancy and the absence of any split-out reference material.	4 / 5
	Total	17 / 20 Passed

Description

73%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 well-formed: third-person, names a specific app and its entities, and includes an explicit 'Use when' trigger. Its main weakness is the generic 'Manage' verb, which limits specificity of the described actions.

Suggestions

Replace the single generic verb 'Manage' with several concrete actions (e.g., 'Create, update, and query Persons, Organizations, Deals…') to raise specificity.

Tighten the when-clause with concrete scenarios (e.g., 'Use when the user wants to create or look up Parma orders, deals, or contacts').

Drop the vague 'and more' or replace it with the remaining entity types so coverage reads as comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	Names the Parma domain and enumerates many concrete entities (Persons, Organizations, Deals, Leads, Projects, Activities), but relies on a single generic verb 'Manage' rather than listing several distinct actions, matching the anchor for one-to-two concrete actions.	3 / 5
Completeness	Provides both a 'what' (manage the listed Parma entities) and an explicit 'when' ('Use when the user wants to interact with Parma data'), but the when-clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	Includes the app name 'Parma', 'Parma data', and natural entity names users would say; coverage is good though a few common synonyms or file/record variants are missing.	4 / 5
Distinctiveness Conflict Risk	The named app 'Parma' appears throughout and the trigger 'interact with Parma data' ties the skill to a clear niche, giving it distinct triggers with minimal conflict risk.	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/parma/SKILL.md
Commit: f484c82

Reviewed: ~21 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.