CtrlK
BlogDocsLog inGet started
Tessl Logo

firecrawl-security-basics

Apply Firecrawl security best practices for API key management and webhook verification. Use when securing API keys, implementing webhook signature validation, or auditing Firecrawl security configuration. Trigger with phrases like "firecrawl security", "firecrawl secrets", "secure firecrawl", "firecrawl API key security", "firecrawl webhook signature".

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable security guide with executable code and a logical five-step flow plus a checklist and error table. Minor conciseness padding, a couple of small correctness gaps in the webhook example, and absent validation checkpoints in non-rotation steps keep it just below top marks.

Suggestions

Trim restated-knowledge comments (e.g. "// Timing-safe comparison prevents timing attacks") and the "protecting them is critical" filler to improve conciseness.

Fix the webhook verification example: compare buffer lengths before timingSafeEqual to avoid a throw, and verify against the raw request body rather than JSON.stringify(req.body).

Add explicit validation checkpoints or feedback loops to Steps 1-3 (e.g. confirm the key loads, confirm .gitignore took effect) to match the rotation step's verify-before-proceed pattern.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete code blocks and minimal prose, but includes brief explanatory comments restating concepts Claude already knows (e.g., "// Timing-safe comparison prevents timing attacks") and slight padding ("protecting them is critical").

4 / 5

Actionability

Provides copy-paste-ready TypeScript and bash across all five steps (env validation, HMAC verification, key rotation curl, sanitization), with minor gaps such as using timingSafeEqual on possibly-unequal-length buffers and recomputing the body via JSON.stringify rather than raw bytes.

4 / 5

Workflow Clarity

Five steps are clearly sequenced and key rotation includes a verification checkpoint (curl | jq .success before removing the old key), but other steps lack explicit validation checkpoints or error-recovery feedback loops.

4 / 5

Progressive Disclosure

Well-organized into Overview, Prerequisites, Instructions, Checklist, Error Handling, and Resources sections with no bundle files needed; the cross-reference to firecrawl-prod-checklist is unsignaled as a path but overall navigation is clear.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

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 specific, complete, and distinctive, naming concrete security actions and providing explicit natural-language trigger phrases. It clearly answers both what the skill does and when Claude should use it.

DimensionReasoningScore

Specificity

"Apply Firecrawl security best practices for API key management and webhook verification" and "securing API keys, implementing webhook signature validation, or auditing Firecrawl security configuration" name the domain plus multiple concrete actions (key management, webhook verification, signature validation, auditing).

5 / 5

Completeness

Clearly answers both what (apply security best practices for API key management and webhook verification) and when ("Use when securing API keys, implementing webhook signature validation, or auditing Firecrawl security configuration") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit trigger phrases "firecrawl security", "firecrawl secrets", "secure firecrawl", "firecrawl API key security", "firecrawl webhook signature" provide comprehensive coverage of natural terms a user would say, including synonyms.

5 / 5

Distinctiveness Conflict Risk

"Firecrawl security" is a clear, narrow niche with distinct Firecrawl-specific triggers, giving minimal overlap risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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