fireflies-common-errors

Diagnose and fix Fireflies.ai GraphQL API errors by error code. Use when encountering Fireflies.ai errors, debugging failed requests, or troubleshooting authentication and rate limit issues. Trigger with phrases like "fireflies error", "fix fireflies", "fireflies not working", "debug fireflies", "fireflies 429".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The content is concise and highly actionable with executable examples and a useful diagnostic script. Its weakness is structure: it is a single self-contained file with implicit per-fix verification steps and no bundle references, capping workflow clarity and progressive disclosure at 2.

Suggestions

Add an explicit validate->fix->retry feedback loop for each error fix (e.g., 'after applying the fix, re-run the diagnostic script and confirm the error code is gone') to lift workflow clarity.

Split the full error-code catalog and diagnostic script into reference files (e.g., references/error-codes.md, scripts/diagnose.sh) and keep SKILL.md as an overview that links to them one level deep.

Confirm whether referenced bundle skills (fireflies-rate-limits, fireflies-debug-bundle) exist as actual files; if not, either provide them or drop the cross-skill references to avoid dangling pointers.

Dimension	Reasoning	Score
Conciseness	The body is a lean error-code quick reference with copy-paste curl/jq commands and tight tables; it assumes Claude's competence and avoids explaining GraphQL or Fireflies basics.	3 / 3
Actionability	Provides fully executable bash diagnostics, a TypeScript mutation example with bypass_size_check, an introspection query, and a deprecated-field replacement table — copy-paste ready and specific.	3 / 3
Workflow Clarity	The diagnose-by-error-code flow is present and a diagnostic script plus an 'Output' section mention verification, but explicit validate->fix->retry checkpoints are only implicit per fix rather than stated as feedback loops.	2 / 3
Progressive Disclosure	No bundle files exist and the ~180-line body is a single monolithic SKILL.md; it points to external/other-skill names rather than clearly signaled one-level-deep bundle files, and inline content (full catalog + diagnostic script) could be split into references.	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 strong: it specifies concrete actions, gives explicit 'Use when' trigger guidance, lists natural trigger phrases, and carves out a distinct niche. It uses third-person voice throughout with no over-claims.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Diagnose and fix Fireflies.ai GraphQL API errors by error code') tied to a specific mechanism; it lists specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly states what it does ('Diagnose and fix ... errors by error code') and when to use it ('Use when encountering Fireflies.ai errors, debugging failed requests, or troubleshooting authentication and rate limit issues').	3 / 3
Trigger Term Quality	Provides natural user phrases ('fireflies error', 'fix fireflies', 'fireflies not working', 'debug fireflies', 'fireflies 429') with good coverage including a specific status code.	3 / 3
Distinctiveness Conflict Risk	The 'Fireflies.ai GraphQL API' niche with code-specific triggers like 'fireflies 429' is clearly distinct and unlikely to conflict with other 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: 1628598

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.