firecrawl-enterprise-rbac

Configure Firecrawl team access control with per-key credit limits and domain restrictions. Use when managing multiple API keys per team, implementing credit budgets per consumer, or controlling which domains each team can scrape. Trigger with phrases like "firecrawl RBAC", "firecrawl teams", "firecrawl enterprise", "firecrawl access control", "firecrawl permissions".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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 complete, executable code and a well-sequenced workflow including validation. Its main weakness is progressive disclosure: a large single-file skill that keeps substantial implementation inline rather than splitting it into reference files.

Suggestions

Move the gateway proxy (Step 2) and TeamBudget (Step 3) TypeScript implementations into a references/ file (e.g. references/gateway.ts), keeping SKILL.md as a concise overview with a clearly signaled one-level-deep link.

Trim the Overview paragraph to drop the explanatory sentence about credit-based pricing that restates knowledge Claude already has.

Add a short validation/verification checkpoint after Step 1 (key creation) — e.g. confirm each new key returns 200 from the Firecrawl API before wiring it into TEAM_POLICIES.

Dimension	Reasoning	Score
Conciseness	Content is mostly code-forward and efficient, but the Overview paragraph restates context Claude likely already knows ('credit-based pricing means access control is primarily about limiting credit consumption') and the large inline TypeScript blocks could be tightened or moved to a reference.	2 / 3
Actionability	Provides fully executable TypeScript (FirecrawlApp client, TeamBudget class, teamScrape/teamCrawl) and a copy-paste curl verification command, matching the 'copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with explicit validation checkpoints (e.g. 'Verify new key works' via curl success check, delete old key only after 48-hour overlap) and an Error Handling table providing feedback loops for recovery.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single monolithic file over 50 lines with all code inline and no bundle reference files to offload the gateway/budget implementations; the only pointer ('firecrawl-migration-deep-dive') is to an external skill rather than a one-level-deep reference.	2 / 3
	Total	10 / 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.

The description is concise, third-person, and clearly states both capability and trigger conditions with natural keyword coverage. It is among the strongest example descriptions in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'per-key credit limits and domain restrictions', 'managing multiple API keys per team', and 'implementing credit budgets per consumer', matching the highest anchor.	3 / 3
Completeness	Explicitly answers both what ('Configure Firecrawl team access control...') and when ('Use when managing multiple API keys per team...') with an explicit trigger clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — 'firecrawl RBAC', 'firecrawl teams', 'firecrawl enterprise', 'firecrawl access control', 'firecrawl permissions' — giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The Firecrawl enterprise RBAC niche with product-specific triggers ('firecrawl RBAC', 'firecrawl enterprise') 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: 50ab626

Reviewed: about 18 hours 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.