CtrlK
BlogDocsLog inGet started
Tessl Logo

onelogin

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/onelogin/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 skill is highly actionable with executable commands and a clear connection-state workflow, weakened mainly by an unnecessary introductory concept explanation and a flat entity list that consume tokens without proportional value. Tightening those would improve token efficiency.

Suggestions

Trim or remove the introductory paragraph defining OneLogin/SSO/MFA, since Claude already knows this, keeping only the official docs link.

Collapse the bare 30-item entity list into a compact inline reference or move it to a separate file, noting only the primary entities (User, App, Group, Role) in the overview.

Label the destination of "skip to Step 2" explicitly (e.g. add a "## Step 2: Search and run actions" heading) so the workflow sequence is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly lean CLI commands, but the opening paragraph explaining what OneLogin is (identity management, SSO, MFA) and the flat 30-item entity list are unnecessary explanation Claude largely already knows and could be tightened.

3 / 5

Actionability

It provides copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) with concrete JSON input examples and a flag table, fully covering the common cases.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but the "skip to Step 2" reference points to an unlabeled target, leaving a minor gap.

4 / 5

Progressive Disclosure

The body is well-organized into clear sections with no bundle files to reference, though being over 50 lines with the full entity list and proxy details inline means it is not as split out as a 5 would require.

4 / 5

Total

16

/

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 covers what and when with a distinct OneLogin trigger, but its capability list is generic and its trigger vocabulary is narrow. Tightening the action verbs and adding natural synonyms would lift it.

Suggestions

Replace generic verbs ("Manage data, records") with concrete OneLogin actions such as "manage users, roles, apps, and groups; automate provisioning workflows".

Expand the trigger clause with natural phrasings users would say, e.g. "Use when the user mentions OneLogin, SSO, or MFA, or wants to manage OneLogin users, apps, or groups."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the OneLogin domain plus a couple of actions, but the actions are generic ("manage data") rather than concrete, so it is not comprehensive enough for a 4.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with OneLogin data"), but the when clause could be more specific with concrete trigger phrases, so it stops short of 5.

4 / 5

Trigger Term Quality

"OneLogin" and "interact with OneLogin data" provide a relevant keyword, but there are no synonyms or file-extension variants a user might naturally say, leaving common variations missing.

3 / 5

Distinctiveness Conflict Risk

OneLogin is a distinct identity-provider niche with a clear trigger term, though it has minor overlap risk with other SSO/identity-management skills rather than being wholly unique.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.