Name: process-street
Rating: 62.4 (1 reviews)
Author: membranedev

process-street

Process Street integration. Manage Organizations, Integrations. Use when the user wants to interact with Process Street data.

Quality

74%

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/process-street/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.

A highly actionable, command-driven skill body with a strong connection-state validation loop and clean sectioning. Its main weakness is conciseness: a marketing-flavored intro and some fluffy connective prose add tokens without earning their place.

Suggestions

Cut the marketing intro to a one-line factual description of Process Street, removing 'businesses of all sizes', 'streamline processes', and the 'auth plumbing' aside.

Tighten the step labeling so 'Step 1', 'Step 2', and the '1b' branch are explicitly headed, making the connection workflow's sequence unambiguous.

De-duplicate the action-discovery command, which appears in both 'Searching for actions' and 'Popular actions', into a single clearly placed reference.

Dimension	Reasoning	Score
Conciseness	The bulk is lean CLI commands and a flag table, but the intro paragraph carries marketing-style padding ('used by businesses of all sizes to streamline processes, improve team collaboration, and ensure consistency') and a few connective phrases ('so you can focus on the integration logic rather than auth plumbing') that could be trimmed.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases end-to-end — install, login, connection ensure/get with --wait, action list, action run with --input, and request via proxy — each with real flags and a complete options table.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → poll-for-ready → search → run sequence with an explicit validation feedback loop (polling connection state through READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step labeling is loose ('1b', 'skip to Step 2' with no clearly labeled Step 1/Step 2 header).	4 / 5
Progressive Disclosure	No bundle files exist, so all guidance is self-contained and organized into clearly headed sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references; it is well-structured but slightly over 50 lines with minor redundancy (the action-list command appears in two sections).	4 / 5
	Total	16 / 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.

A clear, third-person description that names the niche and includes an explicit 'Use when' trigger, giving it solid completeness and low conflict risk. It is held back by a generic verb ('Manage') and a 'what' that undersells the full range of Process Street entities shown in the body.

Suggestions

Replace the generic verb 'Manage' with concrete actions (e.g. 'Create, search, and run Process Street workflows, templates, and tasks') to lift specificity.

Expand the 'what' clause to reflect the body's full scope (Workspaces, Folders, Templates, Template Runs, Tasks) rather than only 'Organizations, Integrations'.

Add a couple of natural trigger synonyms users might say, such as 'workflows', 'checklists', or 'SOPs', to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Process Street domain and two concrete entity targets ('Manage Organizations, Integrations'), but the verb 'Manage' is generic and the scope is far narrower than the body's actual capabilities (Workspaces, Templates, Runs, Tasks), so it does not reach comprehensive coverage.	3 / 5
Completeness	It states both a 'what' ('Manage Organizations, Integrations') and an explicit 'when' ('Use when the user wants to interact with Process Street data'), but the 'what' is thin and omits most actual capabilities, so it falls short of a fully concrete, comprehensive answer.	4 / 5
Trigger Term Quality	The product name 'Process Street' appears as a strong, naturally-spoken trigger along with the phrase 'interact with Process Street data'; coverage is good for a single named product, though a few natural variants (e.g. 'workflows', 'checklists', 'SOPs') are absent.	4 / 5
Distinctiveness Conflict Risk	The skill targets a specific named SaaS product ('Process Street') with distinct triggers and minimal overlap 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/process-street/SKILL.md
Commit: f484c82

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