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

screensteps

ScreenSteps integration. Manage data, records, and automate workflows. Use when the user wants to interact with ScreenSteps 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/screensteps/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 Membrane CLI commands and a clear connection state-machine, but carries some background prose and filler that inflate tokens. Tightening the intro and removing vague directives would improve conciseness.

Suggestions

Remove or compress the opening background paragraph ('ScreenSteps is a knowledge base software...') and the filler line 'When to use which actions: Use action names and parameters as needed.' since Claude already knows this.

Label 'Step 2' explicitly or remove the 'skip to Step 2' cross-references so the connection workflow numbering is internally consistent.

Consolidate the 'Searching for actions' and 'Popular actions' sections, which currently repeat the action-list command with slightly different invocations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-focused content, but includes background Claude already knows ('ScreenSteps is a knowledge base software...') and filler like 'When to use which actions: Use action names and parameters as needed.' that could be trimmed.	3 / 5
Actionability	Provides copy-paste ready, fully executable commands (membrane login, connection ensure, action list/run, request) with flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	A clear sequenced flow (install -> auth -> connect -> search -> run) with explicit state checkpoints and polling feedback for BUILDING/CLIENT_ACTION_REQUIRED, but 'skip to Step 2' references an unlabeled step and the numbering ('1b') is slightly inconsistent.	4 / 5
Progressive Disclosure	Single-file skill with well-organized sections (Overview, Working with ScreenSteps, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) and clear navigation; no bundle files are needed so minor organization gaps keep it just below a 5.	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 clearly identifies the ScreenSteps niche with an explicit trigger clause, but its capability list is generic ('Manage data, records, and automate workflows') rather than naming concrete operations. Tightening the action list to specific tasks would lift specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete ScreenSteps operations such as 'search articles, manage spaces, list users, and automate workflows'.

Add natural trigger synonyms and entities users actually say, e.g. 'knowledge base', 'articles', 'manuals', or 'documentation'.

Keep the explicit 'Use when...' clause but tie it to concrete user intents like 'creating or searching step-by-step guides and tutorials'.

Dimension	Reasoning	Score
Specificity	Names the ScreenSteps domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, matching the anchor that lists 1-2 non-comprehensive actions.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when...') clause are present, but the 'what' is generic so it does not reach the fully concrete level 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with ScreenSteps data' surfaces the key term 'ScreenSteps', but lacks common variations or synonyms beyond 'data', fitting the 'some relevant keywords' anchor.	3 / 5
Distinctiveness Conflict Risk	ScreenSteps is a specific named application with a distinct trigger ('interact with ScreenSteps data'), giving a clear niche and minimal conflict risk with other skills.	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/screensteps/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.