# Set Up Firecrawl App Access

Teams need a clear path from Firecrawl signup to a working application integration. This skill guides credential setup, SDK choice, and smoke testing for Claude, Codex, and Claude Code workflows.

## Install

```bash
npx skillstore add firecrawl/firecrawl-build-onboarding
```

## Metadata

- Status: approved
- Slug: firecrawl-firecrawl-build-onboarding
- Version: 0.1.0
- Author version: 0.1.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: 5ba3ced05a127afe8c386dffbe2f97bdc28b4fe868b4f6f35678b701bedadb61
- Author: firecrawl
- GitHub username: firecrawl
- License: ISC
- Repository: https://github.com/firecrawl/skills/tree/main/skills/firecrawl-build-onboarding/
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/firecrawl-firecrawl-build-onboarding
- Manifest: https://skillstore.pages.dev/api/skills/firecrawl-firecrawl-build-onboarding/manifest

## Capabilities

- Guides browser authorization when the user does not already have a Firecrawl API key.
- Shows how to place hosted or self-hosted Firecrawl settings in environment configuration.
- Directs agents to SDK installation paths for JavaScript, Python, Rust, Java, Elixir, and REST.
- Helps choose between a fresh project setup and an existing project integration path.
- Recommends a smoke test after adding the first Firecrawl request.

## Use Cases

- Add Firecrawl to a New App: A developer can create credentials, install the right SDK, and add a first verified Firecrawl request.
- Standardize Team Setup: A technical lead can give agents a repeatable process for local, preview, and production credential setup.
- Prepare Self-Hosted Configuration: A platform engineer can add both the API key and custom Firecrawl API URL for internal deployments.

## Prompt Templates

### Start Firecrawl Setup

```
Use this skill to set up Firecrawl for this project. Ask me before changing environment files.
```

### Use Existing Key

```
I already have a Firecrawl API key. Add the correct environment variable guidance and choose the SDK for this stack.
```

### Integrate Into Existing Codebase

```
Inspect the repository configuration patterns, then plan the safest Firecrawl SDK integration and smoke test.
```

### Plan Production Rollout

```
Design a Firecrawl onboarding plan for development, preview, and production using secret managers where possible.
```

## Limitations

- Requires the user to complete browser authorization for new Firecrawl credentials.
- Does not implement endpoint-specific scraping, crawling, or search behavior by itself.
- Depends on external Firecrawl documentation and service availability.
- Handles API key setup, so users must protect local environment files and secret stores.

## Best Practices

- Ask for user confirmation before creating or modifying environment files.
- Use a platform secret manager for shared, preview, or production credentials.
- Run one smoke test after SDK installation to prove the key and endpoint work.

## Anti Patterns

- Do not commit \`.env\` files or Firecrawl API keys to source control.
- Do not run unpinned installer commands in regulated environments without review.
- Do not choose a broad Firecrawl endpoint before defining the product behavior.

## Security Audit

- Audited at: 2026-07-05T15:09:12.292\+00:00
- Summary: Most static findings are Markdown formatting, documentation links, placeholders, or expected Firecrawl onboarding references. Confirmed risks remain around credential handling, direct \`.env\` updates, and an unpinned \`npx @latest\` installer command that executes remote package code.

## Stats

- Views: 57
- Downloads: 6
- Favorites: 0
- Popularity score: 0