Name: propelauth
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

propelauth

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

Quality

66%

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/propelauth/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 content is a genuinely actionable CLI guide with executable commands, a state-machine connection flow, and good sectioning. Its main weaknesses are a padded intro paragraph that over-explains PropelAuth and a dangling "Step 2" reference that slightly muddies the workflow.

Suggestions

Trim the opening paragraph to one line; drop the explanation of what PropelAuth is and why developers use it since Claude can infer that.

Fix the dangling "Step 2" reference — either add a numbered "Step 2" header or reword to a concrete section name (e.g. "skip to Searching for actions").

Consider moving the detailed clientAction sub-fields and the proxy-options table into a references file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what PropelAuth is and that developers use it to avoid building auth from scratch — concepts Claude already knows — and lines like "so you can focus on the integration logic rather than auth plumbing" are padding, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) plus a concrete proxy-options table, but placeholders like CONNECTION_ID, actionId, and QUERY leave minor gaps, fitting the mostly-executable anchor just below fully copy-paste ready.	4 / 5
Workflow Clarity	The connection flow is a clear state machine (ensure → READY skip ahead / BUILDING poll → CLIENT_ACTION_REQUIRED act then re-poll → CONFIGURATION_ERROR check error) with a feedback loop, but the dangling "skip to Step 2" reference with no matching Step 2 header leaves a minor gap, fitting the anchor for a clear sequence with most checkpoints present.	4 / 5
Progressive Disclosure	The body is a single well-sectioned file (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files present and no real need for external references; it is well-organized but exceeds 50 lines and inlines detail (e.g. the clientAction sub-structure) that could be split out, fitting the good-structure anchor with minor organization gaps.	4 / 5
	Total	15 / 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 is clearly targeted to a named product and includes both a what and a Use-when clause, giving it solid distinctiveness and completeness. It is held back by a generic "Manage" verb and limited trigger-term breadth.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "Create, update, and search Users and Organizations").

Broaden the trigger clause with natural phrasings users would say, e.g. "Use when the user wants to manage PropelAuth users, organizations, API keys, or roles."

Add file-format or entity synonyms (users, orgs, invitations, API keys) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (PropelAuth) and two entities ("Manage Users, Organizations") but the verb "Manage" is generic rather than a concrete action like extract/fill/merge, matching the anchor that names a domain with 1-2 actions but is not comprehensive.	3 / 5
Completeness	It answers both what ("PropelAuth integration. Manage Users, Organizations.") and when ("Use when the user wants to interact with PropelAuth data."), but the trigger clause is somewhat generic rather than packed with concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	The natural keyword "PropelAuth" appears along with "Users" and "Organizations", but coverage is thin — "Use when the user wants to interact with PropelAuth data" lacks common variations or synonyms, fitting the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"PropelAuth integration" names a specific product niche with distinct triggers and minimal overlap risk with other skills, matching the anchor for a clear niche with minimal conflict risk.	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/propelauth/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.