Name: forgerock
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

forgerock

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

Quality

61%

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

Quality

Content

61%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 delivers executable Membrane CLI guidance with clear connection-state handling and good sectioning. Weaknesses are the introductory concept-explanation padding, inconsistent workflow numbering, and absent explicit validation/feedback loops for batch or destructive actions.

Suggestions

Remove or shrink the opening paragraph explaining what ForgeRock is; assume Claude's knowledge and lead with the actionable CLI workflow.

Fix the step numbering (the body references 'Step 2' but has no numbered Step 1) or relabel with consistent step markers.

Add an explicit validate/retry feedback loop for destructive or batch action runs (e.g. check the response state, retry on CLIENT_ACTION_REQUIRED, surface errors on CONFIGURATION_ERROR).

Dimension	Reasoning	Score
Conciseness	The body is mostly executable command guidance, but the opening 'ForgeRock is an identity and access management platform...' paragraph explains what ForgeRock is — a concept Claude already knows.	3 / 5
Actionability	Provides concrete, executable membrane CLI commands with flags and JSON examples, with only minor gaps (e.g. placeholders CONNECTION_ID/actionId are clearly marked).	4 / 5
Workflow Clarity	The connection lifecycle is sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED), but there are no explicit validate-then-fix feedback loops and the step numbering is inconsistent ('Step 2' referenced without a numbered 'Step 1').	3 / 5
Progressive Disclosure	Single-file skill is organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references; well-structured for its size, though some inline detail (the clientAction schema) could be trimmed.	4 / 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 names the ForgeRock domain, gives a 'Use when' trigger clause, and uses third-person voice. It is held back by generic verbs ('Manage data, records') and limited natural trigger term variety.

Suggestions

Replace generic verbs with concrete ForgeRock actions (e.g., 'create and manage users, groups, and identity objects') to lift specificity.

Expand trigger terms with synonyms and entry points a user would actually say (e.g., 'identity management, user provisioning, ForgeRock IAM').

Tighten the 'when' clause with specific trigger scenarios such as 'Use when the user needs to manage ForgeRock users, groups, or identity records.'

Dimension	Reasoning	Score
Specificity	Names the ForgeRock domain and a few concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive.	3 / 5
Completeness	States what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with ForgeRock data'), though the 'when' is fairly generic.	4 / 5
Trigger Term Quality	Includes the trigger phrase 'Use when the user wants to interact with ForgeRock data' but lacks synonyms or natural variations beyond the bare product name.	3 / 5
Distinctiveness Conflict Risk	The ForgeRock-specific framing makes it mostly distinct from other skills, with only minor overlap risk with generic data-management 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/forgerock/SKILL.md
Commit: f484c82

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