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".
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/clay-pack/skills/clay-enterprise-rbac/SKILL.mdQuality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, explicit 'Use when' guidance, and a comprehensive list of trigger phrases. The Clay-specific domain and administrative focus make it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring workspace roles, team access control, and credit budget allocation. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure roles, access control, credit budgets) and 'when' (explicit 'Use when' clause with specific scenarios plus a 'Trigger with phrases' section listing keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'clay SSO', 'clay RBAC', 'clay enterprise', 'clay roles', 'clay permissions', 'clay team access', 'clay workspace'. These cover both technical and natural user language variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific 'Clay' product context combined with workspace administration focus. The trigger terms are all prefixed with 'clay' and target a narrow niche (workspace permissions/roles), making conflicts with other skills very unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable framework for Clay RBAC management with a useful role matrix and audit checklist, but suffers from code examples that are more illustrative than executable — the TypeScript budget control code doesn't actually integrate with Clay's API and the YAML blocks are documentation rather than configuration. The workflow lacks validation checkpoints important for access control operations, and some content explains things Claude would already understand.
Suggestions
Replace the TypeScript budget control code with actual Clay API calls or Clay UI steps that enforce row limits, since the current code is a standalone logging utility that doesn't interact with Clay
Add validation checkpoints after role assignment and API key creation steps (e.g., 'Verify: confirm the member appears with correct role in Settings > Members')
Remove the prerequisites section and trim the 'why' explanations in the role assignment YAML — Claude can infer why SDRs need Member access
Convert the API key YAML from a descriptive documentation format into actionable steps for creating and naming keys in Clay's UI
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary content like the prerequisites section (Claude knows what admin privileges are) and the recommended role assignments YAML with 'why' fields that explain obvious things. The TypeScript budget control code is quite verbose for what is essentially a configuration pattern. However, the role matrix table and audit checklist are efficient. | 2 / 3 |
Actionability | The role matrix table and audit checklist are concrete and useful. However, the TypeScript code is more of a conceptual framework than executable guidance — it defines interfaces and a logging function but doesn't actually interact with Clay's API or enforce any budgets. The API key YAML is descriptive documentation rather than actionable configuration. The UI navigation ('Settings > Members > Invite') is helpful but minimal. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced from role definition through audit, which is good. However, there are no validation checkpoints between steps — for example, no verification that role assignments were applied correctly, no check that API keys are working after creation, and no feedback loop for the credit budget controls. For an access control workflow involving potentially destructive permission changes, validation gaps are notable. | 2 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear headers and a logical flow. However, the TypeScript code block and detailed YAML examples make the file quite long when they could potentially be in separate reference files. The single reference to 'clay-migration-deep-dive' is appropriate, but there are no bundle files to support progressive disclosure. The error handling table and audit checklist could be separate references. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.