Name: workos
Rating: 52 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

workos

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

Quality

58%

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/workos/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 body is well-structured with concrete, executable Membrane CLI commands and a clear connect-to-run workflow that includes polling-based validation. Its main weakness is mild verbosity explaining WorkOS and Membrane concepts Claude largely already understands.

Suggestions

Trim conceptual padding: remove or shorten 'WorkOS is a platform that helps SaaS companies...' and 'so you can focus on the integration logic rather than auth plumbing' to assume Claude's competence.

Tighten the 'Popular actions' section so it does not duplicate the discovery guidance already given in 'Searching for actions'.

Consider moving the proxy flag reference table and the clientAction state detail into a separate reference file, keeping SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands throughout, but includes unnecessary explanation Claude doesn't need (e.g. 'WorkOS is a platform that helps SaaS companies...' and 'so you can focus on the integration logic rather than auth plumbing'); fits 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level 4.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action run, request) with real flags and JSON examples; only minor gaps like the 'Popular actions' section duplicating discovery guidance keep it from a fully comprehensive 5.	4 / 5
Workflow Clarity	Clear sequence (install -> auth -> connect -> search -> run) with explicit validation checkpoints and a feedback loop in the connection flow (poll --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR); minor gaps (loose 'Step 2' references, no explicit Step 1 label) keep it just below the exemplary level 5.	4 / 5
Progressive Disclosure	Well-organized into clear sections with headers and no bundle files to misroute; the single-file structure is appropriate, but at ~140 lines some reference material (proxy flag table, action schemas) could be split out, placing it at good-but-not-exemplary structure.	4 / 5
	Total	15 / 20 Passed

Description

48%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 names the domain and includes a 'Use when' trigger, but its capabilities are generic ('manage data, records, automate workflows') and the trigger guidance lacks concrete, varied phrases. It is distinct as a WorkOS-specific skill yet light on actionable specifics.

Suggestions

Replace generic verbs with concrete WorkOS actions, e.g. 'Manage users, organizations, SSO connections, directory sync, and audit logs in WorkOS'.

Expand the trigger clause with natural phrases users actually say, e.g. 'Use when the user wants to manage WorkOS organizations, users, SSO, or directory sync, or mentions WorkOS records/data'.

Add common synonyms or object names (organizations, connections, events, SSO profiles) so the description surfaces for varied user phrasings.

Dimension	Reasoning	Score
Specificity	Names the WorkOS domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete; closer to the score-2 anchor 'Names the domain but actions are minimal or generic' than the score-3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Has a clear 'what' (manage data, records, automate workflows) and a present 'when' clause ('Use when the user wants to interact with WorkOS data'), but the 'when' is generic and only weakly specific, fitting 'clear what but when only weakly implied/specific' rather than the explicit-when level 4.	3 / 5
Trigger Term Quality	Includes the specific term 'WorkOS' and the trigger phrase 'interact with WorkOS data', but misses common variations or synonyms; matches 'Some relevant keywords but missing common variations or synonyms' and is not high enough for 4 due to thin keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The WorkOS niche and 'interact with WorkOS data' trigger make it mostly distinct with only minor overlap risk against other integration skills; not a level-5 clear niche but clearly above the somewhat-specific level 3.	4 / 5
	Total	12 / 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/workos/SKILL.md
Commit: f484c82

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