fireflies-multi-env-setup

Configure Fireflies.ai across dev, staging, and production with isolated API keys. Use when setting up multi-environment deployments, managing per-env secrets, or implementing environment-specific Fireflies configurations. Trigger with phrases like "fireflies environments", "fireflies staging", "fireflies dev prod", "fireflies environment setup", "fireflies config by env".

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

Highly actionable, executable content with a clear sequenced workflow and a startup validation checkpoint. The main weaknesses are verbosity from inlining complete implementations and the absence of progressive disclosure via bundle files.

Suggestions

Move the full config module, client, and Zod validator into scripts/ or references/ files and keep SKILL.md as a concise overview with one-level-deep links, reducing inline token cost.

Tighten the inlined client code (e.g., omit the debug-logging path or summarize it) so the body shows only what is essential to the multi-environment strategy.

Add a brief per-environment verification step (e.g., a curl/health check against each env's webhook) so the workflow ends with an explicit confirmation rather than only a startup schema check.

Dimension	Reasoning	Score
Conciseness	Prose is tight and free of concept-explanation padding, but the ~230-line body inlines a full per-environment config object, a complete HTTP client, and a Zod validator that could be trimmed or externalized. Mostly efficient but could be tightened.	2 / 3
Actionability	Fully executable TypeScript, GitHub Actions YAML, and gcloud/bash commands that are copy-paste ready, with concrete env-var names and validation schema.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and Step 4 provides an explicit startup-validation checkpoint ('Validate on startup -- fail fast') with an error-handling table for recovery guidance.	3 / 3
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are empty), so all large code blocks live inline in a monolithic SKILL.md. Sections are well-organized, but substantial implementations that could be split into reference files are inline. Not a 3 because the skill is well over 50 lines and would benefit from externalized detail; not a 1 because structure and navigation are present.	2 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit 'what' and 'when' guidance, natural trigger phrases, and a clear niche. The only weakness is that the listed capabilities overlap rather than enumerating multiple distinct concrete actions.

Suggestions

Distinguish the concrete actions more sharply (e.g., 'generate per-env config, rotate API keys, register per-env webhooks') instead of restating 'configure'/'set up'/'implement' as near-synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and a few overlapping actions ('Configure Fireflies.ai across dev, staging, and production with isolated API keys', 'managing per-env secrets', 'implementing environment-specific Fireflies configurations'), but these are variations of one setup action rather than multiple distinct concrete actions. Not a 3 because it lacks a list of separate specific actions like extract/fill/merge; not a 1 because it does name concrete capabilities.	2 / 3
Completeness	Explicitly answers both what ('Configure Fireflies.ai across dev, staging, and production with isolated API keys') and when ('Use when setting up multi-environment deployments, managing per-env secrets, or implementing environment-specific Fireflies configurations') plus explicit trigger phrases.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say: 'fireflies environments', 'fireflies staging', 'fireflies dev prod', 'fireflies environment setup', 'fireflies config by env'. Good coverage of natural terms rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Clear niche (Fireflies.ai multi-environment setup) with distinct Fireflies-specific triggers; unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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
Path: plugins/saas-packs/fireflies-pack/skills/fireflies-multi-env-setup/SKILL.md
Commit: 4c47e33

Reviewed: 3 days 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.