Name: psigen-software
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

psigen-software

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

Quality

66%

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

Quality

Content

67%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 a well-structured, actionable CLI integration guide with real validation feedback loops for connection setup. Its main weaknesses are marketing-fluff padding in the intro and a couple of broken step-numbering references that muddy the workflow sequence.

Suggestions

Cut the introductory marketing paragraph ("used by enterprises looking to streamline workflows") and the auth-plumbing aside; lead with what Claude must do.

Fix the workflow numbering: add a "1a"/"Step 1" label and define the referenced "Step 2" so the skip instruction resolves.

Tighten "Use action names and parameters as needed." into a concrete instruction pointing to the action search command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but phrases like "It's used by enterprises looking to streamline workflows" and "so you can focus on the integration logic rather than auth plumbing" are unnecessary marketing/explanatory padding Claude does not need, matching the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	Concrete copy-paste commands like `membrane connection ensure "https://www.psigen.com/" --json` and `membrane action run <actionId> --connectionId=CONNECTION_ID --input '{...}' --json` cover the common cases, with only minor gaps (e.g. the vague "Use action names and parameters as needed.").	4 / 5
Workflow Clarity	The connect-and-poll flow has real validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states with retry polling), but the sequence references an unlabeled "Step 2" and a "1b" with no "1a", leaving minor sequencing gaps that keep it below score 5.	4 / 5
Progressive Disclosure	The body is well sectioned into Install, Auth, Connecting, Searching, Running, Proxy, and Best practices with content appropriately inline for a CLI integration guide, and the only external pointer is the official docs URL; good structure with minor organization gaps.	4 / 5
	Total	15 / 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 clearly identifies the product niche and includes an explicit 'Use when' trigger, but its action language is generic and its trigger terms lack variation. It is functional and distinct but could be more concrete and comprehensive.

Suggestions

Replace generic verbs ("Manage data, records") with specific PSIGEN actions such as capture, index, classify, or retrieve documents.

Broaden the 'when' trigger with natural user phrasings, e.g. "Use when the user mentions PSIGEN, document capture, or records automation workflows."

Add a few concrete trigger nouns/synonyms (e.g. document capture, records, workflows) to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the PSIGEN domain plus a couple of actions, but the actions (manage data/records) are generic rather than concrete like 'extract' or 'fill forms', so it sits at the domain-plus-1-2-actions anchor rather than score 4.	3 / 5
Completeness	It states both what ("PSIGEN Software integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with PSIGEN Software data"), but the 'when' clause is narrow and circular, so it falls just short of the fully explicit score-5 example.	4 / 5
Trigger Term Quality	The only natural keyword is the product name repeated in "Use when the user wants to interact with PSIGEN Software data"; coverage is relevant but lacks common variations or synonyms, matching the score-3 anchor rather than the fuller coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	The trigger is anchored to the specific named product "PSIGEN Software data", giving it a clear niche with minimal overlap risk, matching the score-5 anchor despite the generic action phrasing.	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/psigen-software/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.