Name: stepzen
Rating: 60 (1 reviews)
Author: membranedev

stepzen

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

Quality

70%

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/stepzen/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 body is highly actionable with executable CLI commands and a clear state-driven connection workflow, though it opens with conceptual padding and has a couple of mislabeled step references.

Suggestions

Trim the intro paragraph explaining what StepZen/GraphQL is and the 'so you can focus on the integration logic' phrasing; assume Claude knows the domain.

Fix the dangling 'skip to Step 2' and '1b' references by relabeling the sections as explicit numbered steps (Step 1, Step 2) so the navigation is consistent.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient with command blocks and a flag table, but the opening paragraph explains what StepZen/GraphQL is and phrases like "so you can focus on the integration logic rather than auth plumbing" add unnecessary explanation Claude doesn't need, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests plus a concrete flag table, fully covering the common cases, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based validation and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but references to a nonexistent 'Step 2' and an orphaned '1b' label introduce minor gaps, matching 'clear sequence with most checkpoints; minor validation gaps'.	4 / 5
Progressive Disclosure	As a single well-organized file with clear section headers and no broken or nested references, it has good structure; the ~140-line body keeps everything inline with minor organization gaps rather than splitting to reference files, matching 'good structure; most content appropriately placed'.	4 / 5
	Total	16 / 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 covers both what and when and is clearly niched to StepZen, but its action verbs are generic and trigger keyword coverage is limited to the product name alone.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete StepZen-specific actions like "deploy GraphQL schemas, query endpoints, and manage data sources".

Expand the trigger clause to include natural phrases a user would say, e.g. "Use when the user wants to build or query a StepZen GraphQL API, deploy schemas, or connect data sources".

Dimension	Reasoning	Score
Specificity	The description names the StepZen domain and lists a few actions ("Manage data, records, and automate workflows"), but these verbs are generic rather than concrete operations, fitting the 'names domain and 1-2 actions but not comprehensive' anchor.	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with StepZen data"), but the 'when' is limited to a single trigger phrase and could be more specific, matching the 'both present, when could be more explicit' anchor.	4 / 5
Trigger Term Quality	The only natural keyword is "StepZen" / "StepZen data" in the trigger clause; relevant but missing common variations or synonyms, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product StepZen gives it a clear niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	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/stepzen/SKILL.md
Commit: f484c82

Reviewed: 4 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.