documenso-enterprise-rbac

Configure Documenso enterprise role-based access control and team management. Use when implementing team permissions, configuring organizational roles, or setting up enterprise access controls. Trigger with phrases like "documenso RBAC", "documenso teams", "documenso permissions", "documenso enterprise", "documenso roles".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%Weight 40%Scale 1-3

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 real executable Documenso SDK code and useful reference tables, but is weighed down by verbose generic RBAC/audit/multi-tenant patterns, missing validation feedback loops around destructive operations, and broken reference signaling (an orphaned bundle file plus a dangling pointer to a non-existent file).

Suggestions

Link the existing references/implementation-guide.md from the body and either create or remove the dangling 'documenso-migration-deep-dive' reference so navigation is not broken.

Tighten or move the generic application-level RBAC, audit-logging, and multi-tenant code into the reference file, keeping only Documenso-specific guidance inline to improve conciseness.

Add explicit validation checkpoints (e.g., verify team-scoped API key and confirm role permissions before destructive calls like document delete/send) to raise workflow clarity for risky operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with Documenso-specific code, but includes lengthy generic patterns Claude already knows (a full RBAC permission map + middleware, an audit-logging wrapper, a multi-tenant service class) and a marketing-style time-sensitive claim ('early adopter pricing') that could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript using the real SDK (new Documenso({apiKey}), documents.deleteV0/sendV0/getV0) plus concrete SSO config URLs and specific error-cause/solution tables, matching the top anchor.	3 / 3
Workflow Clarity	Steps 1-5 are listed but read as feature areas rather than a strictly sequenced workflow, and destructive operations (document delete/send) lack explicit validate-then-proceed feedback loops, capping this at 2 per the destructive-operation guideline.	2 / 3
Progressive Disclosure	Sections are organized, but the existing references/implementation-guide.md is never linked from the body while Next Steps points to a non-existent 'documenso-migration-deep-dive', and content that could live in the reference file is inline instead — matching 'references present but not clearly signaled; content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 that clearly states the capability, gives explicit 'Use when' trigger guidance, and lists natural trigger phrases scoped to a distinct Documenso-specific niche. Voice is imperative (matching the good examples) with no first/second-person phrasing to penalize.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure Documenso enterprise role-based access control and team management', 'implementing team permissions, configuring organizational roles', 'setting up enterprise access controls' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both 'what' ('Configure Documenso enterprise role-based access control and team management') and 'when' ('Use when implementing team permissions...') plus explicit trigger phrases, matching the top anchor.	3 / 3
Trigger Term Quality	Provides five natural trigger phrases a user would actually say ('documenso RBAC', 'documenso teams', 'documenso permissions', 'documenso enterprise', 'documenso roles'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (Documenso enterprise RBAC) with all triggers prefixed by 'documenso', making conflict with other skills unlikely.	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
Path: plugins/saas-packs/documenso-pack/skills/documenso-enterprise-rbac/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.