Name: processplan
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

processplan

ProcessPlan integration. Manage Organizations, Users. Use when the user wants to interact with ProcessPlan data.

Quality

68%

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

Quality

Content

75%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 a clear sequenced workflow and validation checkpoints. Its main limit is generic phrasing in the description-side context and minor gaps (placeholders, inconsistent step labeling) that keep all dimensions at 4 rather than 5.

Suggestions

Fix the step labeling inconsistency (e.g., label the connection section '1a' and the action-search/run section 'Step 2') so the sequence is unambiguous.

Replace generic placeholders with a concrete worked example (e.g., a sample CONNECTION_ID and a real actionId) so commands are immediately runnable.

Trim the opening product-marketing paragraph to one line of domain context, or move it under the Overview section, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly an efficient CLI reference with executable commands and a flag table; only the opening product-context paragraph ('It helps businesses design, automate, and optimize...') could be trimmed, fitting 'efficient with minor over-explanation' rather than the fully lean 5.	4 / 5
Actionability	Concrete copy-paste commands (membrane login, connection ensure, action list/run, request) with a clear options table cover common cases, but placeholder values (CONNECTION_ID, actionId) and the discovery-only 'Popular actions' section leave minor gaps versus the fully copy-paste-ready 5.	4 / 5
Workflow Clarity	There is a clear sequence (install → authenticate → connection ensure → poll state → search → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll loop, but labeling is slightly inconsistent ('1b' without a matching '1a'/'Step 2'), so it is just below the fully explicit 5.	4 / 5
Progressive Disclosure	A single file with well-organized section headers (Overview, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices) and no external references; the bulk action/proxy detail could arguably be split out, so it lands at 'good structure, minor organization gaps' rather than 5.	4 / 5
	Total	16 / 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 answers both what and when and is anchored to a distinct named product, but its actions and trigger phrases are generic, capping it at the upper-mid range. Tightening 'Manage' into concrete verbs and adding concrete trigger terms would lift the weakest dimensions.

Suggestions

Replace the generic verb 'Manage' with specific actions (e.g., 'create and update Organizations, invite and manage Users, run process workflows').

Expand the 'Use when' clause with concrete natural triggers (e.g., 'Use when the user wants to create organizations, manage users, or run/track ProcessPlan workflows').

Add common synonyms or phrasings users might say (e.g., 'ProcessPlan workflows', 'ProcessPlan processes', 'ProcessPlan templates') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of actions ('Manage Organizations, Users'), but 'Manage' is generic and the coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the more thorough 4 or vague 2.	3 / 5
Completeness	Both 'what' ('ProcessPlan integration. Manage Organizations, Users.') and 'when' ('Use when the user wants to interact with ProcessPlan data.') are present, but the 'when' clause is generic rather than concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	Relevant keywords ('ProcessPlan', 'interact with ProcessPlan data') appear, but there are no synonyms, variations, or file extensions, so it sits at 'some relevant keywords but missing common variations' rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	The named specific product (ProcessPlan) gives it a clear niche with low conflict risk, but the surrounding triggers are otherwise generic, keeping it just below the fully-distinct 5 anchor.	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/processplan/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.