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

keycloak

Keycloak integration. Manage data, records, and automate workflows. Use when the user wants to interact with Keycloak 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/keycloak/SKILL.md

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 content is highly actionable, packed with executable Membrane CLI commands and a clear connect-then-act workflow with state-polling feedback loops. Its main weakness is an introductory paragraph that explains Keycloak concepts Claude already knows, plus slightly loose step numbering ('Step 2' is referenced but unlabeled).

Suggestions

Remove or trim the opening paragraph explaining what Keycloak is; Claude already knows this, so lead directly with the integration workflow.

Label the 'Step 2' section explicitly (e.g. add a '### Step 2: Search and run actions' header) so the 'skip to Step 2' references resolve.

Cut promotional phrasing like 'so you can focus on the integration logic rather than auth plumbing' to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command-based guidance, but the opening paragraph explaining what Keycloak is ('open-source identity and access management solution... handles user login, registration, and single sign-on') restates concepts Claude already knows, and some lines ('so you can focus on the integration logic rather than auth plumbing') read as promotional padding.	3 / 5
Actionability	The body provides copy-paste-ready, fully executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a flag table for proxy options and concrete JSON-input examples covering the common cases.	5 / 5
Workflow Clarity	There is a clear install → authenticate → connect → search → run sequence with explicit state-based feedback loops (polling BUILDING until READY, re-polling after CLIENT_ACTION_REQUIRED), but the 'skip to Step 2' reference points to a Step 2 that is never labeled as a header, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist and the skill is a single self-contained SKILL.md with well-organized section headers and no nested references; it slightly exceeds the simple-skill line threshold but is appropriately structured for a CLI integration, with only minor organization gaps.	4 / 5
	Total	16 / 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 names the Keycloak domain and includes an explicit 'Use when' trigger, but the capability actions are generic ('manage data, records, and automate workflows') rather than concrete Keycloak-specific operations. Trigger coverage relies almost entirely on the single term 'Keycloak' without synonyms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Keycloak operations, e.g. 'Manage realms, clients, users, groups, and roles, and automate authentication workflows.'

Expand the trigger clause with natural synonyms users would say, e.g. 'Use when the user wants to manage Keycloak authentication, SSO, realms, users, or roles.'

Dimension	Reasoning	Score
Specificity	The domain (Keycloak) is named, but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete Keycloak operations like managing realms, clients, users, or roles.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Keycloak data') are present, though the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	'Keycloak' and 'Keycloak data' are relevant natural terms a user would say, but common variations and synonyms (authentication, SSO, identity, realms, users, login) are missing.	3 / 5
Distinctiveness Conflict Risk	'Keycloak integration' names a specific product with a distinct trigger, giving minimal conflict risk, though the generic 'manage data, records, and automate workflows' phrasing could overlap with other integration 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/keycloak/SKILL.md
Commit: f484c82

Reviewed: 6 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.