New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Firecrawl Multi Env Setup

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores.

MITAuto-check: notesData & Analytics

Install Firecrawl Multi Env Setup

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill firecrawl-multi-env-setup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace firecrawl-multi-env-setup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/firecrawl-multi-env-setup .claude/skills/firecrawl-multi-env-setup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
firecrawl-multi-env-setup
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
493 words
Files
2 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores.

  • Works in 7 steps: Inventory each environment's owner,… → Create distinct secret-manager entries… → Apply environment-specific domain… → …
  • Auditing multiple environments
  • SKILL.md covers Overview, Prerequisites, Current Contract and Authentication, plus 7 more sections
  • Needs FIRECRAWL_API_KEY

What it does

Firecrawl Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores. Use when creating or auditing multiple environments. Trigger with "Firecrawl environments", "Firecrawl staging", or "separate Firecrawl keys".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/official-docs.md`). Compatibility notes: Designed for Claude Code; Firecrawl Cloud work requires network access

It sits in Data & Analytics, covering Web scraping. It works with Firecrawl. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Auditing multiple environments
  • With Firecrawl environments
  • Firecrawl staging
  • Separate Firecrawl keys

Example prompts

  • “Firecrawl environments”
  • “Firecrawl staging”
  • “separate Firecrawl keys”
  • “/firecrawl-multi-env-setup”

Requirements

  • A credential in FIRECRAWL_API_KEY
  • Compatibility (from SKILL.md): Designed for Claude Code; Firecrawl Cloud work requires network access
  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Edit

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Inventory each environment's owner, team/account, key, secret path, egress, allowed domains, endpoints/formats, spend ceiling, queue…
  2. Create distinct secret-manager entries and workload identities. Validate that configuration names the environment and refuses missing or…
  3. Apply environment-specific domain policy, explicit crawl/batch limits, endpoint/format restrictions where available, and non-production…
  4. Keep production targets and captured fixtures out of developer machines and pull-request CI. Use synthetic fakes by default and a…
  5. Route telemetry and audit receipts with an environment label while redacting keys, URLs, custom headers, prompts, and bodies.
  6. Test cross-environment secret, target, store, webhook, and queue mistakes; assert they fail before a Firecrawl request or downstream write.
  7. Document promotion as configuration and evidence review, not copying a .env file; test independent rotation and rollback.

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Write
    • Edit

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • FIRECRAWL_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code; Firecrawl Cloud work requires network access

    From compatibility in the SKILL.md frontmatter.

Context cost

Firecrawl Multi Env Setup loads about 1.1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:47
    ation and evidence review, not copying a .env file; test independent rotation and rollback.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 493 words, ~1,116 tokens.

Download SKILL.mdSave it as .claude/skills/firecrawl-multi-env-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
firecrawl-multi-env-setup
description
Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores. Use when creating or auditing multiple environments. Trigger with "Firecrawl environments", "Firecrawl staging", or "separate Firecrawl keys".
allowed-tools
Read, Glob, Grep, Write, Edit
compatibility
Designed for Claude Code; Firecrawl Cloud work requires network access
argument-hint
<repository-path> <environment-set>
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, firecrawl, environments, security
model
inherit
effort
high

Firecrawl Environment Separation

Overview

Prevent a test from consuming production credits, crawling production targets, or writing captured content into the wrong store. Environment identity must be explicit and fail closed.

Prerequisites

  • The target repository or integration path and the requested operator outcome.
  • The source authorization, data classification, and environment policy.
  • Current Firecrawl documentation, credentials only when needed, and an owner for approvals.

Current Contract

Cloud keys are team-scoped credentials and team limits are shared across keys, so separate keys alone do not guarantee capacity isolation. Key restrictions, spend limits, IP restrictions, distinct teams/accounts where appropriate, and an application policy gateway provide different isolation layers. Self-hosted evaluation has a separate capability and security contract.

Authentication

For authenticated Cloud operations, inject FIRECRAWL_API_KEY from an approved secret manager. REST requests use Authorization: Bearer with the key. Never print, commit, transmit, or place a key in a URL. Keyless access is suitable only where the current documentation explicitly allows it and the workload accepts its limits; production workflows should make identity and team ownership explicit.

Instructions

  1. Inventory each environment's owner, team/account, key, secret path, egress, allowed domains, endpoints/formats, spend ceiling, queue capacity, retention, store, and alert destination.
  2. Create distinct secret-manager entries and workload identities. Validate that configuration names the environment and refuses missing or cross-environment values.
  3. Apply environment-specific domain policy, explicit crawl/batch limits, endpoint/format restrictions where available, and non-production credit ceilings.
  4. Keep production targets and captured fixtures out of developer machines and pull-request CI. Use synthetic fakes by default and a protected staging tenant for live tests.
  5. Route telemetry and audit receipts with an environment label while redacting keys, URLs, custom headers, prompts, and bodies.
  6. Test cross-environment secret, target, store, webhook, and queue mistakes; assert they fail before a Firecrawl request or downstream write.
  7. Document promotion as configuration and evidence review, not copying a .env file; test independent rotation and rollback.
Show full SKILL.md (179 more words)Show less

Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. Do not call Firecrawl, rotate keys, change account settings, scrape a target, or deploy merely because this skill was invoked.

Approval Boundaries

Require approval before creating a team/key, adding a production target to staging, sharing capacity, changing spend controls, or copying data or configuration across environments.

Output

Return an environment matrix, identities and secret references, target and endpoint policies, budget/capacity isolation, stores, tests, promotion path, and unresolved shared dependencies.

Error Handling

  • A shared team makes capacity isolation impossible: document it and add throttling or choose stronger isolation.
  • Environment cannot be identified at startup: fail closed.
  • A cross-environment write is detected: halt processing, preserve redacted evidence, and invoke data-incident handling.

Examples

  • "Set up Firecrawl staging" creates its own identity, policy, budget, telemetry, and store.
  • "Reuse the production key locally" is rejected even if the key is convenient.

Resources

Read official Firecrawl evidence before relying on an endpoint, SDK method, plan limit, price, retention option, or self-hosted release.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/.curated/firecrawl-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/official-docs.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Firecrawl Multi Env Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Firecrawl Multi Env Setup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Firecrawl Multi Env Setup this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: NotesMIT
Firecrawl Scrapefirecrawl/skills117—~1.8kAutomated safety check: PassISC
Firecrawl Agentfirecrawl/skills117—~1.2kAutomated safety check: PassISC
Firecrawl Company Directoriesfirecrawl/skills117—~557Automated safety check: PassISC
Firecrawl Competitive Intelfirecrawl/skills117—~604Automated safety check: PassISC
Firecrawlzapier/connectors176—~4.2kAutomated safety check: PassElastic-2.0

Similar skills

  • Firecrawl Scrape

    firecrawl/skills

    Read a known webpage or execute a discovered workflow or data-provider capability.

    117 GitHub stars~1.8k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Firecrawl Agent

    firecrawl/skills

    Autonomously navigate websites and extract structured data across pages.

    117 GitHub stars~1.2k tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Firecrawl Company Directories

    firecrawl/skills

    Extract structured company lists from directories with Firecrawl.

    117 GitHub stars~557 tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Firecrawl Competitive Intel

    firecrawl/skills

    Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl.

    117 GitHub stars~604 tokensUpdated yesterday
    Data & AnalyticsAuto-check passed

  • Firecrawl

    zapier/connectors

    Official

    Agent-callable Firecrawl tools — scrape a URL to clean Markdown, crawl a site, search the web, map site URLs, and extract structured data.

    176 GitHub stars~4.2k tokensUpdated 1 mo ago
    Data & AnalyticsAuto-check passed

  • SEO Firecrawl

    seranking/seo-skills

    Ad-hoc web scraping, site mapping, and full-site crawling via Firecrawl MCP.

    160 GitHub stars~2.3k tokensUpdated 3 mo ago
    Data & AnalyticsAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Firecrawl Multi Env Setup

What does Firecrawl Multi Env Setup do?

Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores. Firecrawl Multi Env Setup is an agent skill from jeremylongshore/tons-of-skills-marketplace. Separate Firecrawl development, staging, and production identities, targets, budgets, policies, telemetry, and data stores.

When should I use Firecrawl Multi Env Setup?

Firecrawl Multi Env Setup fits situations like: auditing multiple environments; with Firecrawl environments; firecrawl staging; separate Firecrawl keys.

How do I install Firecrawl Multi Env Setup in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill firecrawl-multi-env-setup -a claude-code`. Or copy the skill folder (skills/.curated/firecrawl-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/firecrawl-multi-env-setup in your project. Claude Code loads it when a task matches its description.

How do I install Firecrawl Multi Env Setup in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill firecrawl-multi-env-setup -a codex`. Or copy the skill folder (skills/.curated/firecrawl-multi-env-setup in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/firecrawl-multi-env-setup in your project. Codex loads it when a task matches its description.

Can I use Firecrawl Multi Env Setup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill firecrawl-multi-env-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/firecrawl-multi-env-setup, .gemini/skills/firecrawl-multi-env-setup, .github/skills/firecrawl-multi-env-setup and .opencode/skills/firecrawl-multi-env-setup in your project.

What does Firecrawl Multi Env Setup need to run?

Going by SKILL.md and its folder, Firecrawl Multi Env Setup needs credentials named FIRECRAWL_API_KEY. Our summary lists: A credential in FIRECRAWL_API_KEY. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Edit. Compatibility (from SKILL.md): Designed for Claude Code; Firecrawl Cloud work requires network access.

Does Firecrawl Multi Env Setup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Firecrawl Multi Env Setup safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Firecrawl Multi Env Setup use?

Firecrawl Multi Env Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Firecrawl Multi Env Setup use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 439 tokens, read only when the agent opens those files.

What are the alternatives to Firecrawl Multi Env Setup?

Skills that share tags, products or a category with Firecrawl Multi Env Setup: Firecrawl Scrape (firecrawl/skills, 117 stars), Firecrawl Agent (firecrawl/skills, 117 stars), Firecrawl Company Directories (firecrawl/skills, 117 stars) and Firecrawl Competitive Intel (firecrawl/skills, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Firecrawl Multi Env Setup?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.