ideogram-enterprise-rbac

Implement team-based access control and credit management for Ideogram. Use when managing multiple teams with separate budgets, enforcing content policies, or implementing API key isolation for enterprise Ideogram usage. Trigger with phrases like "ideogram RBAC", "ideogram enterprise", "ideogram teams", "ideogram permissions", "ideogram multi-tenant".

Quality

96%

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

92%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.

A well-built, executable code skill with lean prose, complete TypeScript examples, and a clearly sequenced workflow with validation guards. Its main weakness is progressive disclosure: everything is inline with no reference files splitting out the team configs, policy patterns, or proxy logic.

Suggestions

Move the large TEAM_CONFIGS, BLOCKED_TERMS, and cost-per-image tables into a references/ file (e.g. references/team-configs.md) and signal it from SKILL.md so the overview stays lean.

Extract the full teamGenerate proxy and budget-enforcement logic into a scripts/ or references/ file, keeping SKILL.md as an architecture overview with a Quick start snippet.

Add a short 'Validation' note (e.g. test that content/budget rejections surface correctly and that rotation is verified in staging) to make the existing guard checks explicit as a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean: the single Overview sentence conveys non-obvious domain context (Ideogram's single key with no roles/scopes) rather than basic concepts Claude already knows, and the rest is tight executable code with no padding.	3 / 3
Actionability	Each step ships complete, executable TypeScript — real team configs, regex-based content checks, budget tracking, and a fetch call to api.ideogram.ai — that is copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	The six steps are clearly sequenced, teamGenerate runs explicit guard checks (content/style/model/budget) before generating, the key-rotation step includes 'verify' in staging and 'Monitor for 48 hours', and the Error Handling table provides cause/solution recovery.	3 / 3
Progressive Disclosure	No bundle files exist and ~260 lines of code/config live inline in SKILL.md; the only external pointer is the unrelated 'ideogram-migration-deep-dive', so content that could be split into reference files is instead monolithic, matching the 'structure present but content that should be separate is inline' anchor.	2 / 3
	Total	11 / 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, third-person description that names concrete capabilities, includes explicit 'Use when' triggers and natural keyword phrases, and carves out a distinctive enterprise RBAC niche. No first/second-person voice or vague fluff is present.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'team-based access control and credit management', 'separate budgets', 'enforcing content policies', 'API key isolation' — matching the top anchor for naming several specific actions.	3 / 3
Completeness	It states both what the skill does ('Implement team-based access control and credit management for Ideogram') and an explicit 'Use when…' clause, clearly answering what and when.	3 / 3
Trigger Term Quality	It provides natural trigger phrases a user would say ('ideogram RBAC', 'ideogram enterprise', 'ideogram teams', 'ideogram permissions', 'ideogram multi-tenant'), giving good coverage rather than jargon-only or generic terms.	3 / 3
Distinctiveness Conflict Risk	The Ideogram-enterprise RBAC niche with Ideogram-specific trigger phrases makes it 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
Path: plugins/saas-packs/ideogram-pack/skills/ideogram-enterprise-rbac/SKILL.md
Commit: 4c47e33

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