Name: clerkio
Rating: 59.2 (1 reviews)
Author: membranedev

clerkio

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

Quality

68%

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

Quality

Content

71%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 commands and a clear connection-state workflow, but it is somewhat padded and keeps everything inline rather than splitting detailed reference material into bundle files. Trimming the intro and moving reference-heavy sections out would improve both conciseness and progressive disclosure.

Suggestions

Remove the marketing intro paragraph and the bare entity bullet list, or replace them with a one-line factual description of what Clerk.io does.

Move the proxy flag table and the clientAction state spec into a references/ file (e.g. PROXY.md or CONNECTION-STATES.md) and link to them from the body.

Delete or merge the 'Popular actions' section, since it duplicates the command already shown under 'Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with concrete commands, but the marketing-style intro paragraph ('helps online stores increase sales by personalizing the customer experience'), the bare entity bullet list, and the redundant 'Popular actions' section that repeats the action-list command add padding.	3 / 5
Actionability	Copy-paste ready commands cover the full common workflow — install, login (incl. headless), connection ensure, state polling, action list/run with JSON input, and proxy requests with a complete flag table.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-and-retry feedback loop; the dangling 'Step 2' reference and lack of a single linear checklist are minor gaps.	4 / 5
Progressive Disclosure	Sections are reasonably well-organized with headers, but all content is inlined in SKILL.md with no one-level-deep references to separate files for the proxy flag table, clientAction spec, or auth details that could live in references.	3 / 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 clearly identifies the Clerk.io niche and includes an explicit 'Use when' trigger, but its action list and trigger keywords are generic. Expanding both with concrete Clerk.io operations and natural synonyms would lift it toward the top anchors.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Clerk.io operations, e.g. 'sync products and orders, query search analytics, manage recommendations and email campaigns'.

Broaden trigger terms to natural synonyms users say, such as 'Clerk.io, ecommerce search, product recommendations, personalized storefronts'.

Tighten the 'Use when' clause to specific scenarios, e.g. 'Use when the user wants to sync, query, or automate Clerk.io ecommerce data'.

Dimension	Reasoning	Score
Specificity	Names the domain and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Clerk.io operations like sync products or query search analytics.	3 / 5
Completeness	Both 'what' (Clerk.io integration managing data/records/workflows) and 'when' ('Use when the user wants to interact with Clerk.io data') are present and explicit, though the 'when' clause is generic.	4 / 5
Trigger Term Quality	The natural trigger is essentially just 'Clerk.io' and 'data'; common variations or synonyms a user might say (e.g. product recommendations, search, ecommerce personalization) are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Clerk.io gives it a clear niche with distinct triggers and minimal conflict risk against 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/clerkio/SKILL.md
Commit: f484c82

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