fireflies-prod-checklist

Execute Fireflies.ai production deployment checklist with health checks and rollback. Use when deploying Fireflies.ai integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "fireflies production", "deploy fireflies", "fireflies go-live", "fireflies launch checklist".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

The body is highly actionable with executable code and a well-sequenced, validated deployment workflow, but it is somewhat verbose in its overview and monolithic in structure with no real bundle references to offload detail. Splitting the inline code and tables into reference files would improve progressive disclosure.

Suggestions

Trim the Overview paragraph since the Prerequisites and section headers already convey scope, removing redundant framing.

Move the full TypeScript health-check endpoint and alerting/error tables into a reference file (e.g. references/health-check.md) and link to it, keeping SKILL.md as an overview.

Make the Rollback section concrete (platform-specific revert commands and a post-rollback health verification loop) rather than a placeholder comment.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with checklists, executable code, and tables, but the Overview restates what the section headers already convey and some checklist framing is padded; it could be tightened without losing clarity.	2 / 3
Actionability	Provides fully executable TypeScript health-check code and bash blocks with 'set -euo pipefail', concrete curl verification commands, and specific alert/error tables — copy-paste ready guidance.	3 / 3
Workflow Clarity	Sequences Pre-flight → Deploy → Post-Deploy Verification → Rollback with explicit validation checkpoints (health checks run immediately after deploy, post-deploy webhook verification) plus a pre-deployment checklist for a risky production operation.	3 / 3
Progressive Disclosure	No bundle files exist, yet the SKILL.md is a ~200-line monolith with a full inline TypeScript block and multiple tables that could live in reference files; the 'Next Steps' pointer to 'fireflies-upgrade-migration' is not a real bundled file, so structure is present but content that should be separate is inline.	2 / 3
	Total	10 / 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 specific, complete, and distinctive: it names concrete actions, includes an explicit 'Use when' clause with natural trigger phrases, and occupies a clear niche unlikely to conflict with other skills. It is one of the stronger examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Execute Fireflies.ai production deployment checklist with health checks and rollback' — covering checklist execution, health checks, and rollback, matching the multi-action anchor rather than a single domain mention.	3 / 3
Completeness	Explicitly answers what ('Execute Fireflies.ai production deployment checklist with health checks and rollback') and when ('Use when deploying Fireflies.ai integrations to production, preparing for launch...') with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural phrases users would say — 'fireflies production', 'deploy fireflies', 'fireflies go-live', 'fireflies launch checklist' — giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to Fireflies.ai production deployment with distinct, product-specific triggers, making it unlikely to fire for unrelated skills.	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: 6e3a65f

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