Name: clerk
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

clerk

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

Quality

63%

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/clerk/SKILL.md

Quality

Content

65%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 and actionable with strong CLI examples and a clear connection/polling flow, but it pads an unnecessary intro, lacks validation before destructive actions, and inlines a reference-grade action table rather than splitting it out.

Suggestions

Add an explicit validation or confirmation checkpoint before running destructive actions (delete-user, delete-organization) and surface the action's expected effects.

Trim the introductory "what Clerk is" paragraph and the auth-plumbing filler since Claude already knows these concepts.

Move the "Popular actions" table into a references file (e.g. ACTIONS.md) and link to it from SKILL.md to reduce inlined bulk.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with copy-paste commands and tables, but the introductory paragraph explaining what Clerk is and filler like "so you can focus on the integration logic" could be trimmed.	4 / 5
Actionability	Concrete, executable bash commands cover install, auth, connection, search, and running actions, with a parameter-passing example and proxy flag table, though the action table carries "No description" placeholders leaving minor gaps.	4 / 5
Workflow Clarity	A reasonable sequence with a polling feedback loop exists, but destructive actions (delete-user, delete-organization) are invoked via `membrane action run` with no validation checkpoint, capping the score per the destructive-operations guidance.	3 / 5
Progressive Disclosure	Sections are present but the skill exceeds 50 lines with no bundle files, and the large inlined "Popular actions" table is content that could live in a separate reference; references are not signaled.	3 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly states what the skill does and when to use it in third person, but is terse and lacks richer trigger synonyms. It is competent but not exemplary.

Suggestions

Expand the trigger clause to include natural terms users say, e.g. "Use when the user mentions Clerk, user authentication, sign-in/sign-up, or managing users and organizations."

List a few more concrete capabilities (create/update/delete users and organizations) to lift specificity beyond two entity nouns.

Dimension	Reasoning	Score
Specificity	"Manage Users, Organizations" names the domain and two concrete entity actions, matching the score-3 anchor of 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both "what" ("Manage Users, Organizations") and "when" ("Use when the user wants to interact with Clerk data") are present, but the trigger phrase could be more explicit and specific.	4 / 5
Trigger Term Quality	Keywords like "Clerk", "Users", "Organizations", and "Clerk data" are relevant but miss common synonyms (auth, sign-in, authentication) users would naturally say.	3 / 5
Distinctiveness Conflict Risk	The Clerk user-management niche is mostly distinct with minimal conflict risk, though it could overlap slightly with generic auth/admin skills.	4 / 5
	Total	14 / 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/clerk/SKILL.md
Commit: f484c82

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