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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The content is highly actionable with complete, executable examples and a clear step sequence including validation, but it is somewhat verbose and monolithic, keeping detail inline rather than offloading to reference files. Tightening and splitting long code blocks into referenced files would improve token efficiency and structure.

Suggestions

Move the larger code modules (config/fireflies.ts, the client, and the Zod validation) into reference files under references/ and link to them from SKILL.md, keeping only a concise Quick Start inline to improve conciseness and progressive disclosure.

Add an explicit fix-and-revalidate loop to the Step 4 workflow (e.g., 'if validation fails, correct the missing/malformed env var and re-run validateConfig() before continuing') to reach a full feedback-loop workflow.

Trim or tabularize the per-environment config repetition (e.g., extract the common FirefliesConfig shape and show only the per-env diffs) to reduce token cost while preserving actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not over-explain concepts Claude already knows, but it inlines five full code modules (~225 lines) where a multi-env skill of this size would benefit from moving detailed code into reference files; it is not level 3 because the token budget could be trimmed by splitting content out, and not level 1 because there is no conceptual padding.	2 / 3
Actionability	Provides complete, executable TypeScript, bash, and YAML examples (config module, client, GitHub Actions, GCP Secret Manager commands, Zod validation) that are copy-paste ready with specific details, matching the top anchor; it is not level 2 because the code is real and complete rather than pseudocode or missing key details.	3 / 3
Workflow Clarity	A clear five-step sequence exists with an explicit startup-validation checkpoint (Step 4, fail-fast) and an Error Handling table, but the fix-then-revalidate feedback loop is only implicit via the table rather than spelled out in the ordered workflow, so it sits at level 2 rather than level 3's explicit feedback loops.	2 / 3
Progressive Disclosure	Sections are well organized but everything lives in a single inline monolith with no bundle files (references/scripts/assets absent), and content that should be separate (multiple full code modules) is inline; it is not level 3 because the inline code is not split into one-level-deep references, and not level 1 because organization is present.	2 / 3
	Total	9 / 12 Passed

Description

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.

The description is strong: it states concrete capabilities, includes explicit trigger phrases, answers both 'what' and 'when', and occupies a clear niche unlikely to conflict with other skills. No changes needed.

Dimension	Reasoning	Score
Specificity	Names a concrete domain ('Configure Fireflies.ai across dev, staging, and production with isolated API keys') and multiple specific actions (configure, manage per-env secrets, implement env-specific configs), matching the top anchor of multiple concrete actions rather than the mid-level 'domain and some actions'.	3 / 3
Completeness	Explicitly answers both what (configure Fireflies across dev/staging/prod with isolated keys) and when (a clear 'Use when...' clause plus trigger phrases), meeting the top anchor exactly; it is not level 2 because the 'when' is explicit rather than implied.	3 / 3
Trigger Term Quality	Provides several natural trigger phrases a user would say ('fireflies environments', 'fireflies staging', 'fireflies dev prod', 'fireflies environment setup', 'fireflies config by env'), giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The niche is narrowly scoped to Fireflies multi-environment setup with distinct triggers, making it unlikely to fire for unrelated skills; it is not level 2 because the triggers are clearly tied to a specific product and use case.	3 / 3
	Total	12 / 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
Commit: 1628598

Reviewed: 2 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.