manage-portal-members-and-prospects

Manage the lifecycle of API Experience Hub portal members and prospects. Use when an admin needs to approve or reject prospects (candidate users), list active members, inspect and update a member's user-group assignments, or disable a member. Covers the full join → approve → assign → disable flow.

Quality

84%

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

Quality

Content

76%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 with concrete operation specs and clear sequencing, but destructive member-management steps lack explicit validation checkpoints or feedback loops, capping workflow clarity. Minor input-description repetition could be tightened.

Suggestions

Add explicit validation after state-changing steps (e.g., re-fetch the member after disableCommunityUser to confirm access is revoked; verify group assignments took effect after addGroupMappingToUser) to lift workflow clarity past the destructive-operations cap.

Reduce repeated per-step input boilerplate by defining connectionId/portalId once and referencing them, trimming token cost.

Add a brief feedback loop note for approve/disable failures (error → inspect → retry) to support error recovery.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tight per-step blocks, but repeated boilerplate ('description: Connection ID', 'description: Portal ID') across every step and the What You've Built/Next Steps/Related Jobs sections add minor trimmable padding, fitting the 4-anchor above the midpoint.	4 / 5
Actionability	Each step provides a complete, copy-paste-ready yaml operation spec (operationId, inputs with bindings, outputs, and example payloads for user-provided inputs), covering the common cases per the 5-anchor.	5 / 5
Workflow Clarity	Nine steps are clearly sequenced with 'What happens next' transitions and a final checklist, but destructive/irreversible operations (disable member, reject prospect, approve) lack per-step validation checkpoints or feedback loops, capping this at 3 per the destructive-operations guidance.	3 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single file is well-organized into clear sections (Prerequisites, Steps, Checklist, Next Steps) with no nested references, fitting the 4-anchor for a self-contained workflow skill.	4 / 5
	Total	16 / 20 Passed

Description

92%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 is strong: it states concrete lifecycle actions, gives an explicit 'Use when' trigger, and carves out a distinct niche. Minor room to broaden natural-language synonyms beyond the AEH-specific vocabulary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'approve or reject prospects', 'list active members', 'inspect and update a member's user-group assignments', 'disable a member' — covering the full lifecycle comprehensively, matching the 5-anchor.	5 / 5
Completeness	Explicitly states what it does ('Manage the lifecycle...') and when to use it ('Use when an admin needs to approve or reject prospects...') with concrete trigger phrases, satisfying the 5-anchor for both what and when.	5 / 5
Trigger Term Quality	Includes natural admin-facing phrases like 'approve or reject prospects', 'list active members', 'disable a member'; good coverage but the domain jargon ('prospects', 'API Experience Hub') leaves some common synonyms unrepresented, fitting just below the 5-anchor.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (AEH portal member/prospect lifecycle) with distinct triggers and minimal overlap risk with other skills, matching the 5-anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mulesoft/mulesoft-dx
Path: skills/manage-portal-members-and-prospects/SKILL.md
Commit: 4cf0cf6

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.