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".
89
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 clearly defines its scope around Firecrawl team access control with specific capabilities (per-key credit limits, domain restrictions, multiple API keys). It includes both a 'Use when' clause and explicit trigger phrases, making it highly actionable for skill selection. The description is concise, uses third person voice, and occupies a distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure team access control', 'per-key credit limits', 'domain restrictions', 'managing multiple API keys per team', 'implementing credit budgets per consumer', 'controlling which domains each team can scrape'. | 3 / 3 |
Completeness | Clearly answers 'what' (configure team access control with per-key credit limits and domain restrictions) and 'when' (explicit 'Use when...' clause covering managing API keys, credit budgets, domain control, plus a 'Trigger with phrases' section). | 3 / 3 |
Trigger Term Quality | Includes a dedicated trigger phrase list with natural terms like 'firecrawl RBAC', 'firecrawl teams', 'firecrawl enterprise', 'firecrawl access control', 'firecrawl permissions'. Also includes contextual terms like 'credit limits', 'domain restrictions', and 'API keys per team' that users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Firecrawl's team access control, RBAC, and credit management. The combination of 'Firecrawl' + 'access control' + 'credit limits' + 'domain restrictions' creates a very clear niche unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with well-sequenced steps and executable code for implementing Firecrawl team access control. Its main strength is the concrete, production-ready TypeScript implementation with built-in validation at each operation. The primary weakness is that the substantial inline code could be better organized with progressive disclosure, and Step 1's bash block is purely comments rather than executable commands.
Suggestions
Extract the TypeScript implementation (Steps 2-4) into a separate reference file and keep only a concise overview with key patterns in SKILL.md
Replace the comment-only bash block in Step 1 with actual actionable guidance or remove the bash fence since there are no executable commands
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary elements like the 'Prerequisites' section mentioning 'Understanding of credit-per-page billing' and the bash comments in Step 1 that are just descriptive rather than executable. The error handling table and overall structure are reasonably tight, but the content could be trimmed further. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code with concrete type definitions, working domain matching logic, budget enforcement, and complete scrape/crawl functions. The key rotation step includes a real curl command for verification. Code is copy-paste ready with realistic team configurations. | 3 / 3 |
Workflow Clarity | The five steps are clearly sequenced from key creation through domain policies, budget enforcement, policy-enforced scraping, and key rotation. Step 5 includes explicit validation (curl check before removing old key) and a 48-hour overlap period. Step 4 has built-in validation checks (domain allowlist, budget check) before executing operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections, but the inline code is quite lengthy (~150 lines of TypeScript) and could benefit from being split into a separate reference file. The 'Next Steps' reference to 'firecrawl-migration-deep-dive' is good, but no bundle files exist to support progressive disclosure. The error handling table is a nice compact reference. | 2 / 3 |
Total | 10 / 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
a04d1a2
- 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.