ideogram-enterprise-rbac
Configure Ideogram enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls for Ideogram. Trigger with phrases like "ideogram SSO", "ideogram RBAC", "ideogram enterprise", "ideogram roles", "ideogram permissions", "ideogram SAML".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-enterprise-rbac84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 an excellent skill description that follows best practices. It uses third person voice, lists specific capabilities, provides explicit 'Use when' guidance, and includes comprehensive trigger terms. The Ideogram product qualifier combined with enterprise administration domain creates clear distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure Ideogram enterprise SSO, role-based access control, and organization management.' These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (configure SSO, RBAC, organization management) AND when (implementing SSO integration, configuring role-based permissions, setting up organization-level controls) with explicit 'Use when' and 'Trigger with' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'ideogram SSO', 'ideogram RBAC', 'ideogram enterprise', 'ideogram roles', 'ideogram permissions', 'ideogram SAML' - these are terms users would naturally use when needing this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Ideogram' as a specific product qualifier combined with enterprise/SSO/RBAC domain. The explicit trigger phrases like 'ideogram SAML' and 'ideogram RBAC' create a clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable TypeScript code for Ideogram enterprise RBAC implementation with good coverage of roles, SSO, and audit logging. However, it's verbose for a skill file with all implementation details inline rather than referenced, and the workflow lacks validation checkpoints critical for enterprise SSO configuration where misconfigurations can lock users out.
Suggestions
Add validation checkpoints to the workflow: 'Test SSO with a single user before enabling enforce mode' and 'Verify role mappings work correctly before removing direct access'
Move detailed implementation code (full middleware, audit system) to separate reference files, keeping only quick-start examples in SKILL.md
Remove the Prerequisites section - Claude understands what enterprise SSO requires without being told
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements like the Prerequisites section (Claude knows what SAML/OIDC requires) and verbose interface definitions that could be trimmed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code throughout - role definitions, SAML config, OAuth setup, middleware implementation, and audit logging are all copy-paste ready with concrete examples. | 3 / 3 |
Workflow Clarity | Steps 1-4 provide a clear sequence, but lack validation checkpoints. For enterprise SSO setup (a potentially risky operation), there's no 'verify SSO works before enforcing' step or rollback guidance if configuration fails. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the skill is quite long (~180 lines) with all implementation details inline. The SAML config, OAuth setup, and audit trail could be split into separate reference files with just quick-start examples here. | 2 / 3 |
Total | 9 / 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 | |
- 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.