clay-enterprise-rbac

Configure Clay workspace roles, team access control, and credit budget allocation. Use when managing team access to Clay tables, setting per-user credit budgets, or configuring workspace-level permissions for Clay. Trigger with phrases like "clay SSO", "clay RBAC", "clay enterprise", "clay roles", "clay permissions", "clay team access", "clay workspace".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete code, configs, and tables, and is well structured into clear steps. Its main weaknesses are verbosity from repetitive worked examples, the absence of explicit validation feedback loops for destructive admin operations, and no use of bundle files to split detail out of SKILL.md.

Suggestions

Tighten the Step 3 and Step 4 code blocks to one representative example plus a brief note that the pattern repeats, cutting repetitive API-key and table-budget entries.

Add an explicit validation checkpoint to the access-audit workflow (e.g., "After revoking keys/removing members, re-pull the member and API-key lists and confirm the change took effect; fix and re-check if not") to satisfy the destructive-operations feedback-loop expectation.

Move the full role matrix, API-key registry, and quarterly audit checklist into reference files under references/ and link to them from SKILL.md so the overview stays lean and detail is one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of general-concept padding, but the full TypeScript block repeats three table-budget objects and the API-key block lists four entries where one or two examples would convey the pattern, so it could be tightened.	2 / 3
Actionability	Concrete TypeScript interface and audit function, YAML role/API-key configs, a specific UI path ("Settings > Members > Invite"), a capability matrix, and an error-handling table provide copy-paste-ready guidance.	3 / 3
Workflow Clarity	Five sequenced steps plus a quarterly audit checklist and error table give a clear sequence, but there is no explicit validate→fix→retry checkpoint for destructive operations (member removal, key revocation), capping this dimension at 2 per the rubric guideline.	2 / 3
Progressive Disclosure	Sections are well organized, but no bundle files exist and all content (full code blocks, checklist, error table) is inline in a >50-line body, so content that could be split into references is not progressively disclosed.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete capabilities, explicit "Use when" guidance, and a rich set of branded trigger phrases. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	"Configure Clay workspace roles, team access control, and credit budget allocation" lists multiple concrete actions rather than vague language, matching the level-3 anchor.	3 / 3
Completeness	It states both what ("Configure Clay workspace roles, team access control, and credit budget allocation") and when ("Use when managing team access to Clay tables, setting per-user credit budgets, or configuring workspace-level permissions"), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Explicit trigger phrases ("clay SSO", "clay RBAC", "clay enterprise", "clay roles", "clay permissions", "clay team access", "clay workspace") give good coverage of natural terms a user would say.	3 / 3
Distinctiveness Conflict Risk	The Clay enterprise RBAC niche with branded "clay ..." triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

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