Name: authlete
Rating: 48 (1 reviews)
Author: membranedev

authlete

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

Quality

51%

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

Quality

Content

45%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 CLI workflow guidance is concrete and well-sequenced with useful state-checking checkpoints, but the document is dominated by a massive, largely irrelevant term list that wastes tokens and should be extracted into a reference file. Removing that list and fixing the inconsistent step numbering would substantially improve the skill.

Suggestions

Delete or extract the 300-line '## Authlete Overview' bullet list into a separate references file (e.g. references/terminology.md) and link to it; most of those terms (file extensions, audio tracker formats, UI widgets) are irrelevant to Authlete.

Fix the workflow numbering: replace '#### 1b. Wait for the connection to be ready' with a consistent 'Step 1 / Step 2' scheme and actually label the 'Step 2' section that other steps reference.

Show one fully-resolved end-to-end example with a real CONNECTION_ID and action invocation so the executable guidance is complete rather than placeholder-based.

Dimension	Reasoning	Score
Conciseness	The '## Authlete Overview' section is a ~300-line bullet list of largely irrelevant terms (file extensions like BMP/TIFF, audio tracker formats like S3M/MOD/XM/IT, UI concepts like Modal/Wizard) that have nothing to do with Authlete, matching the score-1 anchor for severely verbose, heavily padded content. It cannot be higher because the bulk of the body is token waste that competes with useful context.	1 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure "https://www.authlete.com/" --json', 'membrane action run <actionId> --connectionId=... --json') with documented flags, matching the score-4 anchor for mostly executable guidance. It falls short of 5 because parameter placeholders like CONNECTION_ID are never concretely exemplified end-to-end.	4 / 5
Workflow Clarity	There is a clear sequence (install → login → connection ensure → poll until READY → handle CLIENT_ACTION_REQUIRED → search/run actions) with state-checking checkpoints and a feedback loop (re-poll after the user completes the action), matching the score-4 anchor. It is below 5 because the section numbering is inconsistent ('#### 1b' with a referenced but unlabeled 'Step 2') and error-recovery for CONFIGURATION_ERROR is only briefly mentioned.	4 / 5
Progressive Disclosure	No bundle files exist and the entire 300-line Authlete Overview term list is inlined into SKILL.md when it clearly belongs in a separate reference file, matching the score-2 anchor for content that should be separate being inlined with minimal helpful structure. It is above 1 only because section headers do provide some navigability for the actionable parts.	2 / 5
	Total	11 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when...' trigger and ties the skill to a distinct brand, but its capability statement is generic. Tightening 'Manage data, records, and automate workflows' into concrete Authlete/OAuth actions would lift specificity and completeness.

Suggestions

Replace generic actions with concrete Authlete operations, e.g. 'Manage OAuth/OIDC clients, issue and introspect tokens, handle authorization and pushed authorization requests.'

Add natural trigger synonyms users actually say, such as OAuth 2.0, OpenID Connect, tokens, or client registration, to improve trigger-term coverage.

Make the 'Use when' clause more specific than 'interact with Authlete data' — e.g. 'Use when the user needs to manage Authlete clients, tokens, scopes, or authorization flows.'

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Authlete domain but the actions are minimal and generic rather than concrete OAuth/OIDC operations; this matches the score-2 anchor ('Names the domain but actions are minimal or generic'). It does not reach 3 because no genuinely concrete Authlete actions (e.g. issue tokens, introspect, register clients) are listed.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Authlete data') are present, matching the score-4 anchor. It is capped below 5 because the 'what' is generic and the trigger phrase lacks concrete, specific triggers like OAuth flows or token management.	4 / 5
Trigger Term Quality	'Authlete' and 'interact with Authlete data' give some relevant natural keywords, but common variations or synonyms a user might say (OAuth, OIDC, tokens, clients, authorization) are missing, matching the score-3 anchor for partial keyword coverage. It is above 2 because at least one natural brand term users would say is present.	3 / 5
Distinctiveness Conflict Risk	The specific brand 'Authlete' carves a clear niche with minimal conflict risk against unrelated skills, matching the score-4 anchor for mostly-distinct triggers. It does not reach 5 because the generic 'Manage data, records, and automate workflows' wording could overlap with other data-management skills.	4 / 5
	Total	13 / 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/authlete/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.